Dev Environments
A dev environment per engineer. Forked from one template.
A new hire commits on day one, with no setup drift across the team.
One template
New hire to first commit in a day.
You configure the stack once. Every engineer forks the same image, including Docker, your services, your secrets, and any seeded databases. Their machines are byte-identical.
Preview per PR
A live URL for every PR, opened by every teammate.
Each pull request gets its own forked machine with the full stack running, including the database. The URL goes into the PR and tears down on merge. No preview-env YAML, no staging queue.
Persistent & self-hosted
It keeps running after you close your laptop. You can also host it yourself.
Long builds, seeded databases, and uploaded fixtures survive between sessions. Machines sleep at €0/hr when idle and resume in 8ms. The same binary runs on your own KVM host without Postgres or Kubernetes, and your code stays inside your network.
boxd vs. the cloud dev environments you already know
| boxd | Codespaces | Gitpod | coder.com | |
|---|---|---|---|---|
| Persistent state | Yes | Volume | Partial | Yes |
| Fork from any state | Yes | No | No | No |
| Ops to self-host | 1 binary | — | K8s + DB | K8s + DB |
| Isolation | KVM | Container | Container | VM/Container |
| Interface | SSH | VS Code Web | VS Code Web | Web + SSH |
Related use cases
Stop spending engineer-months on environment setup.
Talk to us about your team's stack, or boot a machine yourself with one SSH command.
read the docs · see pricing · ssh boxd.sh