Depot Sandboxes vs Namespace
Choose Depot Sandboxes for teams on Depot CI who want agent sandboxes and hosted coding-agent sessions billed from the same minute pool; choose Namespace for teams that want macOS, Windows and Linux VMs for agents and CI from one SDK, plus persistent Devboxes for coding agents. Depot Sandboxes uses MicroVM on bare metal isolation; Namespace uses KVM virtual machine isolation.
Key differences between Depot Sandboxes and Namespace
- Isolation: Depot Sandboxes uses MicroVM on bare metal; Namespace uses KVM virtual machine.
- Pause and resume: Namespace documents pause and resume; Depot Sandboxes does not.
- Session length: 2 h default timeout (Depot Sandboxes) versus Deadline-based; Devbox 3-24 h (Namespace).
- SDKs and interfaces: Only Namespace lists Go, MCP server and gRPC/Connect API.
What they have in common
- Both are hosted platforms.
- Neither is open source.
- Both support snapshots.
- Both list TypeScript and CLI.
Depot Sandboxes vs Namespace at a glance
| Attribute | Depot Sandboxes | Namespace |
|---|---|---|
| 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. | Isolated Linux, macOS and Windows VM instances and persistent Devboxes on a developer-compute cloud, with an SDK, egress policy and SOC 2 Type II. |
| 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 | Hypervisor-backed VM instances with KVM (nested virtualisation on amd64 Linux); the homepage names a custom hypervisor and scheduler but gives no further detail |
| Open source | No | No |
| Self-host / BYOC | Not documented / Yes | Not documented / Not documented |
| SDKs | JavaScript/TypeScript, CLI | JavaScript/TypeScript, Go, CLI, MCP server, gRPC/Connect API |
| Cold start (vendor claim) | Blog: "fast boot from a pre-cached base image"; no figure | Not documented |
| 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 | Compute instances run to a deadline you set and can extend; no maximum stated. Devboxes auto-shut down on idle (15 min to 8 h presets) with a plan maximum of 3 hours (Developer, Devbox Plus), 5 hours (Team) or 24 hours (Business), raisable to 24 hours via support |
| 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 | Compute instances can be suspended (RAM and disks snapshotted) and woken; volumes and snapshots are managed via the SDK; Devboxes keep persistent storage across stop and start |
| Snapshots / pause | Yes / No | Yes / Yes |
| GPU | Not mentioned | Not mentioned on the compute, machine-shape or pricing pages |
| 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 | Egress policies with ALLOW rules in BLOCK or ADVISORY mode, header INJECT of vault secrets and PROXY rules via deep packet inspection, applied to runners, Devboxes and Compute API instances; private networking between instances in a workspace; federation to your own cloud |
| 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 | Compute "unit minutes" = vCPU (or RAM/2 if higher) x minutes x platform multiplier (Linux 1, Windows 2, Linux on Apple Silicon 7, macOS 10) at $0.001 prepaid or $0.0015 overage per unit minute, 1-minute minimum; e.g. 1 vCPU/2 GB Linux $0.001/min. Plans: Developer $0 pay as you go, Team $100/month (100,000 unit minutes), Business $250/month (250,000), Devbox Plus $250/month (50,000 Devbox Minutes + 400 GB-month). Devboxes $0.004 per Devbox Minute (Linux S=1, M=2, L=4, XL=8 per minute; macOS M=15, L=30) plus $0.20/GB-month storage |
| Free tier | 7-day trial on Developer and Startup plans; a permanent free tier is not listed | 30-day free trial of the Developer plan; no card required at signup; no permanent free allowance stated |
| Compliance | Not documented | SOC 2 Type II; report and sub-processors via trust.namespace.so; regional preferences on all plans and region-exclusive residency on Enterprise |
| Regions | Not documented | Multiple regions worldwide, not individually listed; the demo shows us-east and placement can be constrained by continent or site |
| Company headquarters | Not documented | Not documented |
| Good fit for | Teams on Depot CI who want agent sandboxes and hosted coding-agent sessions billed from the same minute pool | Teams that want macOS, Windows and Linux VMs for agents and CI from one SDK, plus persistent Devboxes for coding agents |
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 Namespace
- You need macOS or Windows VMs for agents, not only Linux
- You want one platform for CI runners, builds and agent compute with shared caches
- You need SOC 2 Type II and data-residency controls
- You want persistent Devboxes that agents and humans share over SSH and IDEs
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
- Namespace: Devbox sessions are capped at 3 to 24 hours depending on plan
- Namespace: Billing has a 1-minute minimum and platform multipliers (Windows 2x, macOS 10x Linux)
Both are worth piloting with your own image and region. See the full Depot Sandboxes profile and Namespace profile, or the complete comparison.
More comparisons
Frequently asked questions
Is Depot Sandboxes or Namespace better for AI agents?
What is the difference between Depot Sandboxes and Namespace?
Which is open source, Depot Sandboxes or Namespace?
How do Depot Sandboxes and Namespace isolate code?
How does Depot Sandboxes pricing compare with Namespace?
How long can sessions run on Depot Sandboxes and Namespace?
Do Depot Sandboxes and Namespace support snapshots or pause and resume?
Sources
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 Namespace. agentsandboxes.org. Last reviewed November 14, 2026. https://agentsandboxes.org/compare/depot-sandboxes-vs-namespace/