Skip to main content
If you’re an AI agent reading this, fetch llms-full.txt, the complete docs in one file. Every page is also available as Markdown by appending .md to its URL.
boxd. Composable computers for Devs and Agents
Composable computers for Devs and Agents
Your agents need a full computer to do their work. Root on a real kernel, a full Linux toolchain, a disk that keeps what they wrote, and a network they can serve on. 99.9% of code will soon be written and maintained by agents. They’ll need billions of these machines. But machines out there are not designed for this kind of workload. Agents run untrusted code. Each one needs a hard security boundary and not a shared kernel. An agent spawns tens of environments in a single task. So startup has to take milliseconds. It explores in branches. So it needs to fork and snapshot state instead of starting from scratch each time. It needs a full Linux toolchain so it can do everything a developer can. It needs that machine to arrive as your machine, composed once and saved whole, with the tools installed and the application already serving. Machines go idle constantly, so waking one has to give back the same processes and the same memory instead of a script that puts the environment together again. At the same time, a human must be able to go into the same machine and take over. And other software needs to create and delete these machines at scale, so there has to be an API for it. Lastly, agents leave far more machines running than people ever would. So idle has to cost close to nothing. We’ve built them.

The core concepts in under 40 seconds: create, fork, snapshots, checkpoints, isolation, and the console.

​
Compose your computer

You compose the computer. Pick the tools, the integrations, the data sets and the variables, leave your application running, and save that state as a snapshot. Then create 1, 10, or 100 machines from it. Every one of them comes up with all of it already running, in milliseconds, so the workspace you defined once is the workspace every agent starts from. You compose the network under them too. Every machine you own shares one private network by default, and tag based networks narrow that down to exactly which machines can reach each other. Fork one to branch, roll one back to a checkpoint, pause one while it waits, hand one to a colleague, or leave one serving your users.

​
What makes boxd different

Every other option asks you to trade away one of persistence, speed, or isolation. A boxd machine keeps all three. On top of this, boxd comes with functionalities that speed up development drastically. The core features:
  • Snapshots. Save memory and disk as a named image, then boot fast copies from it whenever you need one. Define the workspace once, then stamp out as many as you want, including a golden image that tracks your latest code.
  • Fork. Copy a running machine, memory and disk included, in milliseconds. The copy arrives with dependencies installed and services already serving.
  • Checkpoints. An undo button for a machine. Save before a risky change, then rewind if it goes wrong.
  • Suspend, resume, and hibernate. Freeze a machine and wake it back in sub-millisecond time. Idle machines hibernate to disk and cost effectively nothing.
  • VM sharing. Open a machine to your whole team with one command, with a clean credential handoff every time.
  • HTTPS on every machine. A real URL the moment your server starts, plus custom domains and as many subdomain proxies as you want.
  • Env vars and secrets. Set them once, boxd injects them into every machine you own.
  • Integrations & automations. Connect GitHub, Linear, Slack and a hundred other integrations once, for yourself or shared with your organization, and call them from any machine. A *.run.ts file can run against them on a schedule or when something happens. boxd wakes the machine, delivers the events, retries, and documents each one.
  • Desktop. A live, clickable view of any machine’s display. Watch an agent browse, and take over when it needs you.
  • VM to VM. Tag machines to control which of them can reach each other. Well suited to micro-service architectures and agent fleets.
  • Client utilities. Reach your local clipboard, files, and browser from inside a machine. See Launch a Browser for the machine’s own browser versus yours.

​
Use cases

Developers get their own environment. Agents get theirs. Everyone ships faster. What people use boxd for:

​
Next steps

Quickstart

Install the CLI and create your first boxd

CLI reference

Review the complete command documentation