Sandboxes

Run agents safely,local to cloud.

  • Claude Code
  • OpenAI Codex
  • GitHub Copilot
  • Kiro
  • Cursor
  • Gemini

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.

Read the docs for local setup

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

Capabilities

No, these aren’t containers.

A hardware boundary.

No Docker-in-Docker compromise

A VMM we built ourselves

Why Docker Sandboxes

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.

Comparison table
Capability Docker E2B Daytona Modal Cloudflare
Isolation on your machineMicroVM, own kernelNone, cloud onlyNone, cloud onlyNone, cloud onlyShared-kernel container for dev parity
Runs in the cloudYes, same microVM modelYesYesYesYes
Move a sandbox between themOne command, sbx moveNoNoNoNo
Self-hosting meansYour laptop, todayYour AWS or GCP, via Terraform and NomadYour cloud, control plane stays on Daytona’sModal-managed infrastructureCloudflare’s infrastructure
Docker inside the sandboxPrivate 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.
Gavriel Cohen, Creator of NanoClaw
Pricing

Pay only for what you use

Pricing rate table
SizevCPUsGBPer hour
Micro12 GB$0.07
Small24 GB$0.14
Medium48 GB$0.28
Large816 GB$0.56
XL1632 GB$1.12

Start locally on Docker Sandboxes for free. Cloud compute is metered by the second. Bring your own key for model inference.

Kits and MCP

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.

sbx run claude --kit github.com/acme/kits/backend.yaml

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.

sbx mcp ls sbx mcp enable github-official --sandbox my-project

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.

brew trust docker/tap && brew install docker/tap/sbx

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

Fields marked * are required.

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.

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.

Claude Code, Codex, Gemini, Kiro, Cursor, GitHub Copilot, Warp, NanoClaw and more. Launch any of them with sbx run .

Yes. The sandbox is the safety, not the prompt, so agents run unattended with --dangerously-skip-permissions as the default.

No. sbx installs as its own CLI on macOS, Windows, and Linux.

One YAML file that gives an agent its tools, credentials, network rules, and config, so it boots ready the same way every time.

Yes. Enable an MCP server for one sandbox and only that sandbox. Server credentials live in the sbx secret store.

The same microVM sandbox on Docker-managed infrastructure, metered by the second. Move a sandbox between laptop and cloud with sbx move.

Docker AI Governance adds network access policies, filesystem controls, and org-wide MCP governance, defined once and enforced everywhere.