Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

Coasts

coasts.dev

  • Free plan
  • macOS
  • Linux
  • Self-hosted
7.6 Club score Visit coasts.dev

What Coasts is

Coasts runs separate local development environments for the same project on one machine, letting teams work across Git worktrees with distinct ports, networks, and services. It supports Docker Compose projects and non-containerized local setups, with options for sharing services, volumes, and other resources or isolating instance data. Each running environment receives dynamic ports, while the checked-out environment uses the project's canonical ports. Coasts works with agentic coding workflows without special harness-side configuration; its documentation lists Codex, Claude Code, Cursor, Conductor, T3 Code, and Shep. Remote environments can run on SSH-reachable machines and combine with local ones. The project is free, MIT-licensed, and described as offline-first, with no hosted service dependency or AI upsells. Coasts runs on macOS and Linux and requires Docker, Git, Node.js, and socat. On Linux, canonical ports below 1024 may need host configuration before checkout can bind them.

Who it suits

Coasts suits developers who need separate environments for Git worktrees, including those using supported agentic coding harnesses. It can also suit teams combining local work with SSH-based remote runtimes.

Good to know, and what to watch

  • Runs isolated environments for one project.
  • Supports Docker Compose and non-containerized setups.
  • Offers configurable sharing and per-instance data isolation.
  • Supports local and SSH-based remote environments.
  • Free, MIT-licensed, and offline-first.
  • Requires Docker, Git, Node.js, and socat.
  • Available for macOS and Linux only.
  • Linux ports below 1024 may need host configuration.

Custom team services

—

Coasts

Free

Free plan

The verdict

Coasts is a free local option for separating development runtimes while retaining configurable sharing. Check its system requirements and Linux port caveat before setting it up.

What the maker publishes

Harness compatibility
The docs list support guidance for Codex, Claude Code, Cursor, Conductor, T3 Code, and Shep. source
Harnesses
The documentation lists Codex, Claude Code, Cursor, Conductor, T3 Code and Shep as supported harnesses. source
License
The project is MIT-licensed and described as free and open source. source
License and cost
The project describes itself as free, local and MIT-licensed, with no AI upsells. source
Linux limitation
On Linux, canonical ports below 1024 may require host configuration before checkout can bind them. source
Maker
The site copyright identifies Stanton Street Inc. source
Offline use
The project describes itself as offline-first with no hosted service dependency. source
Parallel runtimes
Each Coast has its own ports, network, and services, with configurable resource sharing. source
Platform limitation
Canonical ports below 1024 on Linux require additional host configuration. source
Port mapping
Each running Coast receives dynamic ports, while only the checked-out Coast uses the project's canonical ports. source
Purpose
Coasts runs multiple isolated local development environments for the same project on one machine. source
Purpose
Coasts runs multiple isolated local development environments for the same project on one machine. source
Remote hardware
Remote Coasts run services on remote machines through SSH and can be combined with local Coasts in a hybrid setup. source
Remote runtimes
Remote Coasts can run on machines reachable over SSH, allowing local and remote runtimes in a hybrid setup. source
Requirements
Coasts requires macOS or Linux, Docker, Git, Node.js and socat; Linux uses Docker Engine with the Compose plugin. source
Requirements
The documented requirements are macOS or Linux, Docker, Git, Node.js, and socat. source
Runtime support
Coasts supports Docker Compose stacks and non-containerized local development setups. source
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. source
Security and hosting
The project says it is offline-first with no hosted service dependency. source
Stack support
Coasts supports Docker Compose projects and non-containerized local development setups. source
Support
The site links to a Discord community and a contact page. source
Team support
The maker offers setup, onboarding, and ongoing infrastructure help for teams through its contact page. source
Volume strategies
Coasts provides shared services, shared volumes, and per-instance data isolation strategies for services such as databases and caches. source
Workflows
Coasts works with agentic coding workflows that use Git worktrees and says no special harness-side configuration is required. source

Checked against the maker's pages on 10 Oct 2026.