Resources · compare

Rig next to the tools you already run

Already using Herd, Valet, Local, ServBay, DBngin, Docker, PM2, a Procfile runner or a stack of terminal tabs? These pages explain, in plain words, what each tool is for and what Rig adds beside it, including where the other tool wins. Most of these are not either/or: plenty of studios run both.

vs/compare/laravel-herd

Laravel Herd

Herd is a polished PHP and Laravel runtime for Mac and Windows. Rig is the process manager for everything around that site: Vite, queues, Node APIs and your AI tools.

Laravel and PHP developers on Mac or Windows who already use Herd, or are choosing a setup now.Read the comparison
vs/compare/laravel-valet

Laravel Valet

Valet parks *.test sites on your Mac. Rig detects those sites and runs the rest of the stack; it does not replace Valet’s nginx and DNS job.

Mac developers already on Valet who need more than a parked site.Read the comparison
vs/compare/local-wp

Local WP

Local by WP Engine is a deep WordPress studio. Rig runs every process in your projects, including one-click WordPress on php -S with isolated MySQL and local HTTPS.

Agencies and freelancers choosing how to run WordPress locally, who may also run Node, queues or AI tools.Read the comparison
vs/compare/servbay

ServBay

ServBay bundles language runtimes, web servers and databases into one local environment. Rig runs and watches the processes in your own projects.

Developers on Mac or Windows comparing all-in-one local environments with a process manager.Read the comparison
vs/compare/dbngin

DBngin

DBngin runs local database servers natively, several versions side by side. Rig runs your app’s processes and can start managed Postgres and Redis for a project.

Developers choosing how to run local databases next to their dev servers.Read the comparison
vs/compare/docker-desktop

Docker Desktop

Docker isolates runtimes in containers. Rig runs and watches the processes already on your computer, and can start Compose stacks beside them.

Teams choosing between a container-first and a native local setup.Read the comparison
vs/compare/pm2

PM2

PM2 is a command-line process manager that keeps Node.js apps alive on servers. Rig is a desktop app for the dev processes on your own computer.

Node.js and full-stack developers deciding whether PM2 belongs on a laptop as well as a server.Read the comparison
vs/compare/overmind-foreman

Overmind and Foreman

Overmind and Foreman read a Procfile and start every line in your terminal. Rig reads the same file and runs it from a desktop app with logs, ports and MCP.

Developers who already keep a Procfile, or a Procfile.dev, and start it from the terminal.Read the comparison
vs/compare/terminal-tabs

Terminal tabs

Six tabs and a Procfile is a workflow, not a tool. Rig gives the same processes names, state, merged logs and memory.

Developers who start the same stack in iTerm, Terminal or Windows Terminal every morning.Read the comparison
vs/compare/devserver-mcp

DevServer MCP

DevServer MCP is a small open-source MCP server that lets an AI agent start dev servers and read their logs. Rig is a desktop app with a local MCP hub for the same job and more.

Developers looking for an MCP server that lets Claude Code, Cursor or Codex manage local dev servers.Read the comparison
vs/compare/mesh

a typical private network

Most private networks are a tunnel you configure. Mesh is the private network inside Rig: wake, screen, names and rules in sentences, on the Macs and Windows PCs you already use.

People with two or more computers who want them to reach each other without a separate network app.Read the comparison
How we write these

Every page names what the other tool is genuinely better at, and says plainly when you should keep using it. No feature table stacked to make us win.

Missing one?

Ask in the forum and we'll write it. Tilt, OrbStack, DDEV and Lando come up most.

Works with

Available for any MCP client — including