Agent Sandboxesagentsandboxes.org
Sandbox profile · Hosted platform

Depot Sandboxes

Answer in brief

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. A sensible add-on for Depot CI customers, less compelling as a standalone sandbox given the file-only snapshots and limited SDK coverage.

By the Agent Sandboxes editors · Updated

Overview

Depot, the container-build and CI acceleration company, exposes the compute behind Depot CI as sandboxes: microVMs on bare-metal hosts with NVMe storage, on x86-64 or ARM64, with Docker and nested virtualisation. Two surfaces exist. The Sandbox SDK (@depot/sandbox, Node.js, announced as a private beta on 18 June 2026) creates sandboxes, streams commands and exposes a node:fs/promises-style filesystem. Managed Agents hosts sessions from Amp, Claude Code, Claude Managed Agents, Devin and OpenAI in Depot sandboxes of 2-16 vCPUs, replacing the earlier depot claude remote agent product, with automatic workspace snapshots, Tailscale access to private services and a depot-mcp bridge.

Snapshots capture files only and stopped sandboxes cannot restart, so this is an ephemeral-run model rather than a persistent computer. Pricing is per second against a monthly minute pool shared with CI, which suits existing Depot customers more than standalone use; the Business tier offers deployment in your own AWS account. The hypervisor, regions and compliance are not documented on the sandbox pages, and the SDK's current status beyond the June private-beta note is not stated.

Notable

  • Sandbox SDK announced in private beta on 18 June 2026; Managed Agents replaced the earlier Claude Code remote agent product
  • Sizes from 2 to 64 vCPUs on Intel or Arm; Managed Agents at 2, 4, 8 or 16 vCPUs
  • Business plan offers dedicated infrastructure deployed in your own AWS account

Depot Sandboxes specifications

AttributeDetails
IsolationMicroVM per sandbox on bare-metal hosts ("Real microVMs, not containers") with a full Linux syscall interface, Docker and nested VMs; hypervisor not named
DeploymentHosted platform · BYOC available
Open sourceNo
SDKs and interfacesJavaScript/TypeScript, CLI
Cold start (vendor claim)Blog: "fast boot from a pre-cached base image"; no figure
Max session lengthRuns 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
PersistenceSnapshots 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
GPUNot mentioned
NetworkingSandboxes 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
PricingDeveloper $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
Free tier7-day trial on Developer and Startup plans; no permanent free tier
ComplianceNot documented
RegionsNot documented

Facts from Depot Sandboxes’s public documentation, verified November 9, 2026. Performance numbers are vendor claims.

Strengths and trade-offs

Strengths

  • 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

Trade-offs

  • Snapshots save files only; no memory snapshots, pause or restart of stopped sandboxes
  • TypeScript-only SDK, and it was private beta at announcement
  • Hypervisor, regions and compliance not documented
  • No free tier beyond a 7-day trial

Good fit for: Teams on Depot CI who want agent sandboxes and hosted coding-agent sessions billed from the same minute pool.

How Depot Sandboxes compares

SandboxIsolationOpen sourceSelf-host / BYOCCold start (vendor)Max sessionSnapshots / pauseGPUSDKs
Depot SandboxesMicroVM on bare metalNoNo / YesNot documented2 h default timeoutYes / NoNot documentedJavaScript/TypeScript, CLI
NamespaceKVM virtual machineNoNo / NoNot documentedDeadline-based; Devbox 3-24 hYes / YesNot documentedJavaScript/TypeScript, Go, CLI, MCP server, gRPC/Connect API
Railway SandboxesLinux VMNoNo / NoNot documentedNo cap (idle 30 min default)Yes / NoNot documentedJavaScript/TypeScript, CLI, GraphQL API
Docker Cloud SandboxesMicroVM, own kernelNoNo / No~100s of ms (claim)1 h default TTLYes / YesNoCLI, JavaScript/TypeScript, REST API
E2BFirecracker microVMYesYes / YesNot documented1 h / 24 h (Pro)Yes / YesNoPython, JavaScript/TypeScript
BlaxelMicroVMNoNo / Yes<25 ms resumeUnlimited (standby)Yes / YesNot documentedTypeScript, Python, Go
Modal SandboxesgVisor or VMNoNo / Not documented<1 sUp to 24 hYes / YesYesPython, JavaScript/TypeScript, Go

See all Depot Sandboxes alternatives →

Frequently asked questions

What is Depot Sandboxes?
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. A sensible add-on for Depot CI customers, less compelling as a standalone sandbox given the file-only snapshots and limited SDK coverage.
How does Depot Sandboxes isolate code?
Depot Sandboxes documents its isolation as: MicroVM per sandbox on bare-metal hosts ("Real microVMs, not containers") with a full Linux syscall interface, Docker and nested VMs; hypervisor not named.
Is Depot Sandboxes open source?
No, Depot Sandboxes is not open source. It does offer a bring-your-own-cloud deployment.
How much does Depot Sandboxes cost?
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 Check the official pricing page for current rates.
What are the alternatives to Depot Sandboxes?
Common alternatives include Namespace, Railway Sandboxes, Docker Cloud Sandboxes, E2B, Blaxel, Modal Sandboxes. See Depot Sandboxes alternatives for a full comparison.

Sources

  1. depot.dev/docs/sandboxes/overview
  2. depot.dev/docs/agents/overview
  3. depot.dev/pricing
  4. depot.dev/changelog/2026-06-18-sandbox-sdk-beta.md
  5. depot.dev/blog/now-available-the-depot-sandbox-sdk

Cite this page

Agent Sandboxes. (2026). Depot Sandboxes. agentsandboxes.org. Last reviewed November 9, 2026. https://agentsandboxes.org/sandboxes/depot-sandboxes/

Found an error or a missing sandbox? Submit a correction — every entry links to the sources it relies on.