Coasts
Coasts runs separate local development environments for the same project on a single machine.
What Coasts is
Coasts runs separate local development environments for the same project on a single machine. Each environment can have its own ports, network, and services, with configurable sharing of resources such as volumes or services. Running environments receive dynamic ports; the checked-out environment uses the project's canonical ports. It supports Docker Compose projects and local development setups without containers, and works with Git worktree-based agentic coding workflows without special harness-side configuration. Its documentation lists Codex, Claude Code, Cursor, Conductor, T3 Code, and Shep as supported harnesses. Coasts can also run services on SSH-reachable remote machines alongside local environments. The project describes itself as free, open source under the MIT license, and offline-first, with no hosted service dependency. It runs on macOS and Linux and requires Docker, Git, Node.js, and socat. On Linux, using canonical ports below 1024 may require host configuration.
Good
- Free, local, and MIT-licensed.
- Supports Docker Compose and non-containerized setups.
- Works with several documented coding harnesses.
- Can combine local and SSH-based remote runtimes.
Watch out
- Requires Docker, Git, Node.js, and socat.
- Runs on macOS and Linux only.
- Linux canonical ports below 1024 may need host configuration.
Who it suits
Coasts suits developers who want isolated environments for parallel work on one project, especially those using Git worktrees or agentic coding tools. It also fits teams that need local and SSH-based remote runtimes.
Verdict
Coasts brings isolated project environments, configurable resource sharing, and remote SSH runtimes together for macOS and Linux development. Check its system requirements and Linux port configuration needs before adopting it.
Plans and prices
From Coasts's own pricing page, checked 10 Oct 2001.
| Plan | Price | What it gives you |
|---|---|---|
| Coasts | Free | Free, local, open source; no usage limits stated |
| Custom team services | Priced on request | Custom local configurations · cloud deployments · infrastructure support |
The facts
Each one read from Coasts's own pages, with the date it was checked.
What it does
- Harness compatibility
- The docs list support guidance for Codex, Claude Code, Cursor, Conductor, T3 Code, and Shep.checked 10 Oct 2001
- Harnesses
- The documentation lists Codex, Claude Code, Cursor, Conductor, T3 Code and Shep as supported harnesses.checked 9 Oct 2001
- License
- The project is MIT-licensed and described as free and open source.checked 10 Oct 2001
- Offline use
- The project describes itself as offline-first with no hosted service dependency.checked 10 Oct 2001
- Parallel runtimes
- Each Coast has its own ports, network, and services, with configurable resource sharing.checked 10 Oct 2001
- Purpose
- Coasts runs multiple isolated local development environments for the same project on one machine.checked 10 Oct 2001
- Remote hardware
- Remote Coasts run services on remote machines through SSH and can be combined with local Coasts in a hybrid setup.checked 10 Oct 2001
- Remote runtimes
- Remote Coasts can run on machines reachable over SSH, allowing local and remote runtimes in a hybrid setup.checked 9 Oct 2001
- Requirements
- The documented requirements are macOS or Linux, Docker, Git, Node.js, and socat.checked 10 Oct 2001
- Runtime support
- Coasts supports Docker Compose stacks and non-containerized local development setups.checked 10 Oct 2001
- Secrets
- Coasts can extract secrets from the host environment and inject them into Coast containers so credentials do not need to be hardcoded in a Coastfile.checked 10 Oct 2001
- Security and hosting
- The project says it is offline-first with no hosted service dependency.checked 9 Oct 2001
- Stack support
- Coasts supports Docker Compose projects and non-containerized local development setups.checked 9 Oct 2001
- Support
- The site links to a Discord community and a contact page.checked 9 Oct 2001
- Volume strategies
- Coasts provides shared services, shared volumes, and per-instance data isolation strategies for services such as databases and caches.checked 10 Oct 2001
- Workflows
- Coasts works with agentic coding workflows that use Git worktrees and says no special harness-side configuration is required.checked 9 Oct 2001
- Worktree runtimes
- Each environment can have its own ports, network and services, with options to share resources across environments.checked 9 Oct 2001
- Worktree workflow
- Coasts works with agentic coding workflows that use Git worktrees and requires no special harness-side configuration.checked 10 Oct 2001
Money
- License and cost
- The project describes itself as free, local and MIT-licensed, with no AI upsells.checked 9 Oct 2001
Where it runs
- Linux limitation
- On Linux, canonical ports below 1024 may require host configuration before checkout can bind them.checked 10 Oct 2001
- Platform limitation
- Canonical ports below 1024 on Linux require additional host configuration.checked 9 Oct 2001
- Port mapping
- Each running Coast receives dynamic ports, while only the checked-out Coast uses the project's canonical ports.checked 10 Oct 2001
The company
- Maker
- The site copyright identifies Stanton Street Inc.checked 9 Oct 2001
- Team support
- The maker offers setup, onboarding, and ongoing infrastructure help for teams through its contact page.checked 10 Oct 2001
Alternatives to Coasts
- 1
Garden
Free planOpen sourceWebAPILinuxmacOS8.3From $50 a month - 2
DevPod
Free planOpen sourceLinuxmacOSSelf-hostedWindows7.4Free plan - 3
Docker Desktop
Free planWebLinuxmacOSWindows7.3From $9 a month - 4
OrbStack
Free planAPImacOS7.2From $8 a month - 5
Kool
Free planWebLinuxmacOSWindows7.1From $5 a month - 6
Rancher Desktop
Free planAPILinuxmacOSWindows6.7Free plan