devboxen runs your development environments on your own servers instead of on your laptop. Each environment is an isolated container with its own Docker, so a project's complete Docker Compose stack and a coding agent like Claude Code can work there around the clock, without access to your laptop, your SSH keys or your other projects. You use them from a terminal or from any browser, also on your phone, and everything keeps running when you disconnect.
Status: early. Everything described here is in daily use; devboxen init, the guided
setup, is new.
It fits if:
- you develop projects that run as a Docker Compose stack, even in development;
- you let coding agents work on them and want that away from your own machine;
- you have, or can rent, a Linux server (any Ubuntu 24.04 VPS), and optionally an AWS account for a bigger machine that only runs when you need it;
- you are one person or a small team.
It does not fit if you need user management, roles and an admin UI for a larger organization. Use Coder for that.
- Isolated boxes. Each box is a container with its own Docker daemon (via
Sysbox).
docker compose upworks as on a workstation and at the same speed. A box cannot reach the host, other boxes or the server's SSH. You can have several boxes per server, for example one per project. - Or a virtual machine per box. On a server with hardware virtualization, each box runs in its own VM by default, with its own kernel (docs/vm.md).
- Sessions that keep running. Every terminal and every Claude Code session runs in tmux inside the box. Close the laptop, lose the connection, continue from another device.
- Claude Code included. One login for all boxes on a server. Claude can use a real Chrome browser in the box, and you can watch what it does.
- Browser access. VS Code, the terminal sessions and a Chrome that runs inside the box,
so your app's
localhostaddress works. Usable on a phone. - GitHub without SSH keys. git and gh use fine-grained tokens, one per account or organization. No key and no SSH agent ever enters a box.
- On-demand cloud server. An optional OpenTofu module for an AWS EC2 instance that you start when you need it and that stops itself every night.
| Directory | Contents |
|---|---|
box/ |
The box image: Ubuntu, Docker, Chrome, VS Code server, terminal, Claude Code, Codex CLI, mise (docs) |
host/ |
Commands and settings for each server: devbox, devbox-admin, firewall |
cmd/devboxen-web/, web/ |
The browser interface (docs) |
ansible/ |
Server setup and deployment |
tofu/aws-host/ |
OpenTofu module for an on-demand AWS server |
cmd/devboxen/ |
The devboxen command line tool |
docs/ |
Settings, boxes, VM boxes, browser interface, AWS hosts, security |
You need:
- a server with Ubuntu 24.04 (x86_64) that you can log in to as root with your SSH key;
- a domain name that points to it, for the browser interface;
- on your computer: Go,
sshand Ansible.
go install github.com/dx-tooling/devboxen/cmd/devboxen@latest
mkdir my-devboxen && cd my-devboxen && git init # a private repository for your setup
devboxen initdevboxen init asks for the server and the domain, makes a key pair for your secrets and
the password for the browser interface, sets the server up (about 10 minutes) and creates
the first box. If it stops halfway, run it again: it continues where it stopped. Then:
devboxen shell # a shell in the box (or: devboxen claude)
devboxen tui # everything as a menuThe browser interface is at https://<your domain>. Commit the directory, except
secrets/identity.txt, and keep a copy of that file somewhere safe: without it, the secrets
cannot be decrypted.
More hosts, a server you have or a new AWS instance that runs only when you need it:
devboxen host add (docs/aws.md for AWS). devboxen help lists all
commands; the settings are described in docs/config.md.