PortBay vs ServBay
PortBay is an open-source (AGPL-3.0), container-free local dev manager for macOS covering Node, PHP, and static sites. ServBay is a closed-source, container-free all-in-one bundle that ships many PHP versions, Node, Python, databases, and multiple web servers in a single downloadable app. If you want one install that bundles every runtime and service imaginable, ServBay covers a wide surface. If you want something open, lighter, and opinionated about using your system's existing tools, PortBay is the better fit.
At a glance
| PortBay | ServBay | |
|---|---|---|
| License | AGPL-3.0 (open source) | Closed source |
| Price | Free · optional Pro | Free tier / paid tiers |
| Containers | None (native) | None (native) |
| Runtimes | Node, PHP, static | PHP (multiple versions), Node, Python, more |
Local HTTPS + .test | Built in (mkcert) | Built in |
| Managed DNS | Bundled dnsmasq | Built in |
| Reverse proxy | Caddy (automatic) | Caddy / Nginx (selectable) |
| Footprint | Small (native) | Medium–large (bundled runtimes) |
| Platform | macOS (Apple Silicon) | macOS |
| Automation | CLI + MCP | GUI-first |
What they share
Both tools are container-free and provide real .test HTTPS hostnames without writing Nginx configs by hand. Both bundle their own DNS handling. Both aim for a "just click and go" experience for local development, and both support PHP and Node projects on macOS without Docker.
Where PortBay is different
PortBay is open source under AGPL-3.0. The codebase is public, auditable, and accepts contributions. ServBay is proprietary.
PortBay is intentionally lean. Rather than bundling every version of every runtime, it manages projects against runtimes you already have installed — or installs what you need. The result is a smaller disk footprint and less ambient background resource use.
PortBay's declarative JSON registry means your project configuration is a file you can check into version control and share across machines. The full CLI and an MCP server let you script every operation, including from AI agents.
Pro access is a one-time contribution (donation or merged PR) rather than a tiered subscription.
Where ServBay is stronger
ServBay bundles an unusually wide set of runtimes and services out of the box — multiple simultaneous PHP versions, Python, several database engines, and selectable web servers — all managed through its GUI. If you need to switch between PHP 7.4 and PHP 8.3 for different projects with no manual setup, ServBay handles that with a few clicks and no prior configuration.
ServBay's GUI is comprehensive and works well for developers who prefer visual management over terminal commands. The all-in-one model also means fewer "where does this binary live" questions on a fresh machine.
Choose ServBay when
- You need multiple PHP versions active simultaneously and want that managed for you through a GUI.
- You want a single installer that brings runtimes, databases, and web servers without touching Homebrew or the system path.
- Open-source licensing is not a requirement.
- You prefer a rich GUI over CLI-first workflows.
Choose PortBay when
- Open source matters — you want to inspect the code or contribute.
- You want a lighter tool that works with your existing runtime installs rather than replacing them with a bundled copy.
- You mix Node, PHP, and static projects and want a single consistent interface across all of them.
- CLI and MCP automation are important for your workflow or team.
- A perpetual Pro license (contribution-based, no subscription) fits better than tiered pricing.
Bottom line
ServBay is a capable all-in-one bundle for macOS PHP developers who want maximum GUI convenience and parallel PHP versions. PortBay is the right pick when open source, a lighter footprint, and CLI-first automation matter more than bundled-everything. Get started with PortBay to see the difference.
See all comparisons — developers also compare PortBay with Laravel Herd and MAMP.