Dev setup for solo developers
Solo developers on one machine use Rig to replace terminal archaeology: project groups boot Vite, API, database, and workers in health order; merged logs show which process died overnight; port reclaim fixes EADDRINUSE without lsof hunting. The local MCP hub lets Cursor or Claude read live health, stream logs, diagnose crashes, and restart a dead sidecar — scoped tools, not a raw shell. Everything works offline; cloud is optional for Continuity or a second machine. Rig does not host code or replace Docker — it is the native process manager for local development when you ship alone and cannot afford mystery crashes before standup. One board names every service so six anonymous panes become a recoverable morning routine with health order, colour-tagged logs, and one-click restart for the process that actually died overnight.
- Health-ordered morning boot for full project groups
- Merged logs and port reclaim without terminal archaeology
- Local MCP for Cursor/Claude — scoped, not a raw shell
- Offline-first; Cloud optional for Continuity or a second machine
Do I need Rig Cloud as a solo developer?
No. The desktop app runs fully offline for process control, logs, ports, and MCP. Cloud is optional for Live Links, Continuity backups, or a second machine.
How is Rig different from iTerm or Terminal tabs?
Rig names every service, merges logs with colour tags, tracks ports, recovers crashes, and exposes MCP so your editor sees the runtime — not six anonymous panes.