Depot Sandboxes vs Docker Cloud Sandboxes
Choose Depot Sandboxes for teams on Depot CI who want agent sandboxes and hosted coding-agent sessions billed from the same minute pool; choose Docker Cloud Sandboxes for developers already using Docker Sandboxes locally who want the same policies and Kits when a run must outlive the laptop. Depot Sandboxes uses MicroVM on bare metal isolation; Docker Cloud Sandboxes uses MicroVM, own kernel isolation.
Key differences between Depot Sandboxes and Docker Cloud Sandboxes
- Isolation: Depot Sandboxes uses MicroVM on bare metal; Docker Cloud Sandboxes uses MicroVM, own kernel.
- Pause and resume: Docker Cloud Sandboxes documents pause and resume; Depot Sandboxes does not.
- Session length: 2 h default timeout (Depot Sandboxes) versus 1 h default TTL (Docker Cloud Sandboxes).
- SDKs and interfaces: Only Docker Cloud Sandboxes lists REST API.
What they have in common
- Both are hosted platforms.
- Both use microVM isolation.
- Neither is open source.
- Both support snapshots.
- Both list TypeScript and CLI.
Depot Sandboxes vs Docker Cloud Sandboxes at a glance
| Attribute | Depot Sandboxes | Docker Cloud Sandboxes |
|---|---|---|
| What it is | MicroVM sandboxes on the bare-metal compute behind Depot CI, with a TypeScript SDK, Tailscale networking and a Managed Agents service that hosts Claude Code, Codex, Devin and Amp sessions. | The cloud counterpart to Docker's local agent sandboxes: the same sbx CLI and Kits running microVMs on Docker-managed compute, metered per second under the experimental Docker Agentic Platform. |
| Type | Hosted platform | Hosted platform |
| Isolation | MicroVM per sandbox on bare-metal hosts ("Real microVMs, not containers") with a full Linux syscall interface, Docker and nested VMs; hypervisor not named | MicroVM with a separate kernel per sandbox and its own Docker Engine, "the same microVM isolation and policies as local sandboxes"; hypervisor not named |
| Open source | No | No |
| Self-host / BYOC | Not documented / Yes | No / Not documented |
| SDKs | JavaScript/TypeScript, CLI | CLI, JavaScript/TypeScript, REST API |
| Cold start (vendor claim) | Blog: "fast boot from a pre-cached base image"; no figure | Press release: boots in the "low hundreds of milliseconds" with secrets, policy and agent configuration preconfigured (vendor claim) |
| Max session | Runs until stopped or the configured timeout expires; the SDK launch post gives a default timeout of two hours with extensions; no maximum stated; a stopped sandbox cannot be restarted | Expires after 1 hour by default; the timeout action can stop a resumable sandbox or delete it, and the press release says agents can run unattended for hours; no maximum stated |
| Persistence | Snapshots save the home and /workspace directories (not processes or memory) and seed new sandboxes; Managed Agents snapshot the workspace automatically between runs, excluding node_modules, .venv and target; stopped sandboxes cannot be resumed; persistent disk was listed as planned | Sandboxes that can be resumed are stopped rather than deleted at expiry; sbx move copies a filesystem snapshot between cloud and local (processes and memory are not transferred); the API manages images, snapshots and volumes; files are deleted on rm |
| Snapshots / pause | Yes / No | Yes / Yes |
| GPU | Not mentioned | No - cloud sandboxes have no host hardware access (GPU, USB, display are local-only) |
| Networking | Sandboxes can join your organisation's Tailscale tailnet to reach private services; Depot Cache credentials are injected by default; run secrets are scoped to up to 16 hosts each; no egress allow-list documented | Deny-by-default policy at account and sandbox level, opened per host with --allow-network (e.g. github.com:443); credentials are injected by a proxy so raw values never enter the VM; ports are exposed through public HTTPS URLs; L7 method/path filtering is not supported in the cloud; the security page (written for local sandboxes) says sandboxes cannot communicate directly over the network |
| Pricing | Developer $20/month with 2,000 included minutes, Startup $200/month with 20,000, Business custom (dedicated infrastructure, deployment in your own AWS account); minutes are shared across Depot CI, Sandboxes and Managed Agents and measured at 2 vCPU, so the default 4 vCPU sandbox uses 2 minutes per minute; overage $0.00005 per vCPU-second, billed per second with no minimum; storage 25 GB / 250 GB included then $0.20/GB-month | Pay-as-you-go compute metered in seconds by runtime and CPU/memory configuration under a Docker Agentic Platform subscription with no recurring fee; rates are not published; 1-16 vCPUs per the press release; model-provider inference billed separately |
| Free tier | 7-day trial on Developer and Startup plans; a permanent free tier is not listed | None stated for cloud; the sbx CLI and local sandboxes are free |
| Compliance | Not documented | Not documented |
| Regions | Not documented | Not documented |
| Company headquarters | Not documented | Palo Alto, California, United States |
| Good fit for | Teams on Depot CI who want agent sandboxes and hosted coding-agent sessions billed from the same minute pool | Developers already using Docker Sandboxes locally who want the same policies and Kits when a run must outlive the laptop |
Verified November 14, 2026 from each provider’s documentation. Cold-start figures are vendor claims, not our measurements.
Which should you choose?
Reasons to choose Depot Sandboxes
- You use Depot CI and want sandbox and agent minutes from the same pool with shared caches
- You want hosted Claude Code, Codex, Devin or Amp sessions that survive closing your laptop
- You need sandboxes on your Tailscale tailnet to reach private services
- You want Arm as well as x86 microVMs
Reasons to choose Docker Cloud Sandboxes
- You already use Docker Sandboxes locally and want identical policies and Kits in the cloud
- You need agent runs to continue after your laptop shuts down
- You want credential injection and deny-by-default networking enforced outside the VM
Trade-offs to check first
- Depot Sandboxes: Snapshots save files only, not processes or memory; a stopped sandbox cannot be restarted
- Depot Sandboxes: TypeScript-only SDK, and it was private beta at announcement
- Docker Cloud Sandboxes: Compute rates, regions and compliance are not published
- Docker Cloud Sandboxes: The Docker Agentic Platform subscription is labelled experimental
Both are worth piloting with your own image and region. See the full Depot Sandboxes profile and Docker Cloud Sandboxes profile, or the complete comparison.
More comparisons
Frequently asked questions
Is Depot Sandboxes or Docker Cloud Sandboxes better for AI agents?
What is the difference between Depot Sandboxes and Docker Cloud Sandboxes?
Which is open source, Depot Sandboxes or Docker Cloud Sandboxes?
How do Depot Sandboxes and Docker Cloud Sandboxes isolate code?
How does Depot Sandboxes pricing compare with Docker Cloud Sandboxes?
Do Depot Sandboxes and Docker Cloud Sandboxes support GPUs?
Can you self-host Depot Sandboxes or Docker Cloud Sandboxes?
How long can sessions run on Depot Sandboxes and Docker Cloud Sandboxes?
Do Depot Sandboxes and Docker Cloud Sandboxes support snapshots or pause and resume?
Sources
- depot.dev/docs/sandboxes/overview
- depot.dev/docs/agents/overview
- depot.dev/pricing
- depot.dev/changelog/2026-06-18-sandbox-sdk-beta.md
- docker.com/press-release/cloud-sandboxes-extending-secure-ai-agent-isolation-beyond-the-laptop/
- docs.docker.com/ai/sandboxes/
- docs.docker.com/ai/sandboxes/cloud/
- docs.docker.com/ai/sandboxes/cloud/local-vs-cloud/
Check before you rely on it. Products change quickly, and this page reflects public documentation as of November 14, 2026. Confirm anything that matters in the provider’s own documentation.
Cite this page
Agent Sandboxes. (2026). Depot Sandboxes vs Docker Cloud Sandboxes. agentsandboxes.org. Last reviewed November 14, 2026. https://agentsandboxes.org/compare/depot-sandboxes-vs-docker-cloud-sandboxes/