Sandboxes
Run agents safely,local to cloud.
Run Claude Code, Codex, and many other agents at full speed in MicroVM environments. Local or cloud. One CLI.
Get started in seconds.
Install sbx locally. Then start an agent with sbx run claude or sbx run codex.
macOS install command: brew trust docker/tap && brew install docker/tap/sbx
One command. MicroVM‑based isolation everywhere.
When a job outgrows your machine, run the same sandbox on Docker-managed infrastructure and carry it back when done.
Burst up
Heavy builds on cloud hardware, not your battery
Keep working
Detach and close the laptop, the agent keeps going
Same isolation
Same microVM boundary on both sides, no downgrade
Carry it over
sbx move recreates a sandbox’s filesystem on the other side, the work comes with it
No, these aren’t containers.
Its own kernel
A hardware boundary. A runaway agent hits a boundary, not your machine.
No Docker-in-Docker compromise
Containers alone force elevated privileges the moment an agent builds images. A private engine per microVM does not.
A VMM we built ourselves
Docker’s own virtual machine monitor, tuned for sandboxes that start in seconds and leave nothing behind.
A hardware boundary.
No Docker-in-Docker compromise
A VMM we built ourselves
Everyone else makes you choose.
Real isolation in someone else’s cloud, or your machine with weaker walls. Docker Sandboxes is the only one that runs the same microVM model in both places and moves a sandbox between them.
| Capability | |||||
|---|---|---|---|---|---|
| Isolation on your machine | MicroVM, own kernel | None, cloud only | None, cloud only | None, cloud only | Shared-kernel container for dev parity |
| Runs in the cloud | Yes, same microVM model | Yes | Yes | Yes | Yes |
| Move a sandbox between them | One command, sbx move | No | No | No | No |
| Self-hosting means | Your laptop, today | Your AWS or GCP, via Terraform and Nomad | Your cloud, control plane stays on Daytona’s | Modal-managed infrastructure | Cloudflare’s infrastructure |
| Docker inside the sandbox | Private engine per sandbox | – | – | – | – |
You don’t trust agents with security. You build walls around them. Docker has been ahead of the curve on exactly this, and Docker Sandboxes is what that looks like at the infrastructure level.
Pay only for what you use
| Size | vCPUs | GB | Per hour |
|---|---|---|---|
| Micro | 1 | 2 GB | $0.07 |
| Small | 2 | 4 GB | $0.14 |
| Medium | 4 | 8 GB | $0.28 |
| Large | 8 | 16 GB | $0.56 |
| XL | 16 | 32 GB | $1.12 |
Start locally on Docker Sandboxes for free. Cloud compute is metered by the second. Bring your own key for model inference.
Sandbox Kits
The same sandbox,
every time.
One YAML file gives an agent its tools, credentials, network rules, and config. The agent boots ready, the same way, every time.
Mixin Kits
Layer additional capabilities onto Claude Code or Codex.
Agent Kits
Define a full agent: its image, its entrypoint, the network it can reach.
Credentials never enter the VM
The real secret stays on your host.
Give a sandbox exactly
the tools it needs.
Enable an MCP server for one sandbox and only that sandbox. The agent gets the tools. Nothing else does.
Curated catalog ships with the CLI.
Scope servers per sandbox: one project gets GitHub, the rest get nothing.
Server credentials live in the sbx secret store.
Works with whichever agent runs inside.
Install Docker Sandboxes in seconds.
Need more control over your sandboxes?
Your developers get isolated environments to run agents freely and safely. When your team needs to go further, Docker AI Governance adds network access policies, filesystem controls and org-wide MCP governance: defined once, enforced everywhere.
Talk to us about:
- Network access policies for sandbox environments
- Filesystem access controls and restrictions
- Admin-level configuration for your team
Talk to an expert
Thank you for your interest. The Docker Team will be in touch.
Common questions
What is a sandbox for coding agents?
A disposable, isolated environment where an agent works unattended, with a real dev environment and scoped access to your files, network, and secrets. Your host stays untouched.
How is this different from a container?
Each sandbox is a microVM with its own kernel and its own private Docker Engine, so there is a hardware boundary between the agent and your machine and no path back to the host.
Which agents are supported?
Claude Code, Codex, Gemini, Kiro, Cursor, GitHub Copilot, Warp, NanoClaw and more. Launch any of them with sbx run
Is YOLO mode actually safe here?
Yes. The sandbox is the safety, not the prompt, so agents run unattended with --dangerously-skip-permissions as the default.
Do I need Docker Desktop?
No. sbx installs as its own CLI on macOS, Windows, and Linux.
What are Sandbox Kits?
One YAML file that gives an agent its tools, credentials, network rules, and config, so it boots ready the same way every time.
Can agents use MCP servers inside a sandbox?
Yes. Enable an MCP server for one sandbox and only that sandbox. Server credentials live in the sbx secret store.
What are Cloud Sandboxes?
The same microVM sandbox on Docker-managed infrastructure, metered by the second. Move a sandbox between laptop and cloud with sbx move.
What if I need org-wide controls?
Docker AI Governance adds network access policies, filesystem controls, and org-wide MCP governance, defined once and enforced everywhere.




