a full computer in<10ms

Composable computers for Devs and Agents

Full, hardware-isolated Linux computers you compose once, spin up as many as you need, and never pay for idle time.

Docs

Set up once. Build on it forever

  • create
  • fork
  • snapshot
  • checkpoint
  • pause / resume
  • hibernate

Machines that remember

Running processes, open files, and shell state all survive between sessions.

Your tools are already signed in

Integrations & automations in every machine

Trusted by engineers at

  • Meta
  • orq.ai
  • HelloFreshHelloFresh
  • Clawnify
  • Google
  • LangWatch
  • Saga
  • ByteDance
  • Filed
  • Prosus
  • Applyfin
  • TeslaTesla
  • AppTweak
  • MoyaiMoyai
  • Booking.com
  • HiDesk
  • FREE NOW
  • Familiar LabsFamiliar Labs

Engineers at Meta, Google, Tesla, ByteDance, HelloFresh, Prosus, Booking.com, Techleap, FREE NOW, orq.ai, neno, Duna, Saga, Sparqle, Moyai, Netium, Applyfin, Familiar Labs, LangWatch, Medexxa, HiDesk, Clawnify, Installer.com, Prospyr, AppTweak, Filed build on boxd.

Fork a machine, mid-run

Copy a running machine in under 200ms, with everything live:

  • running processes
  • databases
  • files, memory and disk

Stop rebuilding the same environment. Share one across your team.

Save a machine with your app, data and tools already running. Every new machine starts from it, not from scratch.

Built for flexibility and control

boxd hands you the whole platform to configure, not a black box. Add checkpoints to your VMs and take snapshots to restore from, and give your organisation its own private domains, variables and secrets.

Configure your favorite integrations inside your private VMs and automate whatever you want.

One machine for every agent, branch and developer

Dev boxes, agents and PR previews all run on the same machine. Every one of them gets these tools.

Machines

Persistent Linux VMs with 2 vCPU, 8 GB of RAM and 100 GB of disk by default. SSH in and it's yours.

Forks

Copy a running machine, disk and all, in under 200ms. The copy is a real machine, not a container on top of yours.

Snapshots

Freeze a machine and bring it back later in the state you left it, down to the running processes.

Checkpoints

Roll a machine back to exactly where it was. Memory and disk, restored in place — a save point on the machine you already have, not a new one.

Integrations

Connect GitHub, Linear or Slack once and every machine in the org has it. The MCP server installs straight into Claude Code, Codex or opencode.

Domains

Every machine gets an HTTPS subdomain. Point your own domain at it when you're ready.

Environment vars

Share secrets across machines, scoped to your org rather than pasted per box.

API keys

Drive all of it from the CLI, the API, or your CI job.

Self-hosted

Run the whole platform on your own hardware.

Contact us
FAQ

Things people ask first

Commonly asked questions →

Yes. Give a machine an egress allowlist and it can only connect to the hosts you name. Forks inherit the allowlist, so copies of a locked-down machine stay locked down. Create a machine with `--isolated` and boxd leaves out the in-machine CLI, your integrations and your agent logins. To keep machines off the public internet, put your organization behind Tailscale.

The machine keeps running, so builds and agent runs carry on and your files and processes are there when you come back. After 4 hours with no traffic a machine hibernates and pays for disk only, then wakes with its processes intact. Every new account starts with €30 of free credits, and the full rate card is on the pricing page.

Yes. Machines come in 1 vCPU / 4 GiB, 2 vCPU / 8 GiB (the default) and 4 vCPU / 16 GiB, and you can pick any of them yourself. For 8 vCPU / 32 GiB or larger, email contact@boxd.sh. Resize an existing machine with `boxd machine resize <name> --vcpu 4 --memory 16G`, which restarts it.

On bare-metal servers in Germany, so your machines and their data stay in the EU. A US region is coming. If you need machines in your own datacenter, cloud or country, you can self-host boxd.

Every idea gets its own machine

Install the CLI, sign in once, and the first one is yours. Fork it the moment you need another.

Docs