# Docker Sandboxes vs Vercel Sandbox

> Vercel Sandbox scores 76.6 (BB) to Docker Sandboxes's 62.1 (B) for code sandboxes. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/docker-sandboxes-vs-vercel-sandbox
- Markdown: https://www.anchorterminal.com/compare/docker-sandboxes-vs-vercel-sandbox.md (~5,300 tokens)
- Slim: https://www.anchorterminal.com/compare/docker-sandboxes-vs-vercel-sandbox.min.md (~980 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/docker-sandboxes-vs-vercel-sandbox.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-18

Vercel Sandbox scores 76.6 (BB) on agent readiness against Docker Sandboxes's 62.1 (B), and leads in 5 of 7 scored categories. Docker Sandboxes leads on agent ergonomics. Both do code sandboxes.

- Docker Sandboxes: grade B, 62.1/100, rank #698 of 1557. Markdown https://www.anchorterminal.com/tools/docker-sandboxes.md · JSON https://www.anchorterminal.com/api/v1/tools/docker-sandboxes.json
- Vercel Sandbox: grade BB, 76.6/100, rank #90 of 1557. Markdown https://www.anchorterminal.com/tools/vercel-sandbox.md · JSON https://www.anchorterminal.com/api/v1/tools/vercel-sandbox.json
- Best code execution sandboxes for AI agents: https://www.anchorterminal.com/best/code-sandboxes/index.md
- All 325 sandboxes comparisons: https://www.anchorterminal.com/compare/code-sandboxes/index.md

## Which one, for what

### Docker Sandboxes (B)

Good for: Running coding agents such as Claude Code or Codex in a disposable cloud VM, or the same kit locally for free.

Ahead on:
- Agent ergonomics, 83 against 73

Also in its favour:
- No incidents deducted, where Vercel Sandbox loses 3 points for them

Watch for: Docker Agentic Platform, needed for every cloud interface, is experimental, and no SLA was found

### Vercel Sandbox (BB)

Good for: Agents that spend most of their time waiting on a model, agents that need a workspace kept across runs (Drives), and teams already on Vercel.

Ahead on:
- Reliability, 75 against 45
- Security & auth, 86 against 69
- Payments & pricing, 75 against 0
- Maintenance & community, 82 against 71

Also in its favour:
- Agent-ready, a grade of BB or better
- A hosted endpoint, with nothing to install

Watch for: Tied to a Vercel team and project even when called from elsewhere, and access tokens reach the whole team


## Why the edge

### Payments & pricing: Vercel Sandbox +75

- Docker Sandboxes (0): No x402, MPP or L402 (0). Compute is metered per second by size, but neither the docs, the Docker Sandboxes product page nor docker.com/pricing publishes a unit price. The plans page says usage and pricing show on the Usage & billing page after sign-in (0). Signup to Docker Agentic Platform asks for billing and payment details at checkout, with a one-time promotional credit after, so there is no card-free start for cloud sandboxes (0). A person subscribes in a browser and creates the access token (0). The free local `sbx` CLI is not the graded surface. 0+0+0+0 = 0.
- Vercel Sandbox (75): No x402, MPP or L402 (0). Per-unit prices published by region, $0.128 an Active CPU hour and $0.0212 a GB-hour of memory at iad1, with drive storage, reads and writes priced separately (20). Hobby includes 5 Active CPU hours and 5,000 creations a month at no cost. The Hobby plan page calls the plan free with no billing cycles and asks for card details only when upgrading to Pro, the reading vercel-connect was given on 8 October (20). Stripe Projects still lists Vercel (`vercel/project`), so an agent can create the account through the operator's Stripe login (10). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 50 is 75.

### Reliability: Vercel Sandbox +30

- Docker Sandboxes (45): Hosted lines, for the cloud Sandboxes API. dockerstatus.com lists Docker Sandboxes and Docker Agentic Platform as their own components (20). Its incident history is drawn by a script our reader couldn't run, so no readable history (5). Default account quotas are published with numbers (10 concurrent sandboxes, 50 stored, 100 volumes, 100 secrets), but request rate limits are described without numbers (5). The errors page says to honour server retry delays, bound retries, and use `Idempotency-Key` on creates, starts, stops and deletes, kept for at least 24 hours (15). No SLA found in the docs (0). Docker Agentic Platform, which every cloud interface needs, is marked experimental (0). 20+5+5+15+0+0 = 45.
- Vercel Sandbox (75): Sandbox is its own component on www.vercel-status.com, with an incident history (20). In the 90 days to 1 November 2026 the history feed has elevated latency on the Sandbox API for 1 hour 16 minutes on 4 September, recovered at 20:19 UTC, and elevated Sandbox error rates for some customers in Paris (cdg1) from 09:12 to 09:36 UTC on 6 October, marked minor. Nothing for Sandbox since. The 23 July dashboard incident has left the window. A degradation and a short regional incident only (20). Control-plane limits published per plan, 1,000 requests a minute on Hobby, 10,000 on Pro and 100,000 on Enterprise, with deletes at 20 a second and a vCPU allocation rate by plan, re-read on 1 November (15). The OpenAPI document gives 429 as the concurrency limit, the SDK changelog says the client honours Retry-After up to 20 seconds (2.9.2), and `Sandbox.getOrCreate` with a name gives a safe retry. No backoff guidance for callers outside the SDK (10). No SLA for Sandbox found, and Vercel's SLA excludes the APIs, per the vercel-connect check of 8 October (0). GA (10).

### Security & auth: Vercel Sandbox +17

- Docker Sandboxes (69): A Docker personal access token with the `sandbox:use` scope, exchanged by the SDK for short-lived access tokens, or browser device sign-in, with a named permission checked per operation. No PAT expiry or rotation guidance was read (25). Account and per-sandbox network policy with a deny-all preset, deny rules winning, and etags required on updates and deletes. Policy presets let a sandbox reach any host when allow-all or Open is chosen (14). Credentials are injected by a proxy outside the VM, so an agent inside never sees raw keys, and egress is limited to allowed destinations (12). Network policy decision logs per sandbox through `/v1/policy-logs`. No account audit log for cloud sandboxes found (8). SECURITY.md in docker/sbx-releases sends reports to security@docker.com with acknowledgement within 72 hours, and Docker's security.txt is valid per the docker-agent check of 1 November. Bug bounty and certifications unchecked (10). 25+14+12+8+10 = 69.
- Vercel Sandbox (86): Vercel OIDC tokens tied to one project, which `vercel env pull` hands out for 12 hours, or access tokens elsewhere. Access tokens reach a whole team rather than one sandbox (25). Each sandbox is a Firecracker microVM with its own kernel (10). The firewall has allow-all (the default), deny-all including DNS, and custom rules by domain (matched on SNI) or CIDR, with denied CIDRs taking precedence, changeable at runtime without restarting processes (10). Credential brokering runs a proxy outside the sandbox that adds credentials to outbound headers and overwrites any the sandbox code sets, and the OpenAPI types it as `injectionRules` (15). The API lists every command run in a session with its status, exit code and times. We found no team audit log entry for sandbox activity (8). Valid security.txt pointing to HackerOne and responsible.disclosure@vercel.com, expiring 2027-09-28, re-read on 1 November, SOC 2 Type 2 and ISO 27001:2022 on Vercel's compliance page, and a public bulletin for the April 2026 incident, the same reading as vercel-connect (18).

### Maintenance & community: Vercel Sandbox +11

- Docker Sandboxes (71): `sbx` 0.54.0 on 16 November 2026, per the dated release notes (30). Stable releases 0.51.0 on 3 November, 0.53.0 on 11 November and 0.54.0 on 16 November, with nightly builds tagged daily in docker/sbx-releases (20). Closed service with dated release notes and GitHub issues on docker/sbx-releases as the feedback channel. Issue response times could not be read (8). One official SDK, `@docker/sandboxes` for TypeScript, plus the CLI (10). Source and CI are not public, so package health is unchecked (3). 30+20+8+10+3 = 71.
- Vercel Sandbox (82): @vercel/sandbox 3.9.1 tagged on 28 October 2026 (30). The repository's tags show 16 stable releases from 3.0.0 on 7 August to 3.9.1 on 28 October, with the CLI package (`sandbox`) at 4.11.1 the same day (20). We couldn't read issue replies on vercel/sandbox (GitHub's pages answered 403), so this rests on the public changelog (10). Current official JavaScript and Python SDKs, per the 1 October check for Python (15). The publish workflow runs `pnpm test` on every push to main and every pull request, and 3.7.0 moved to `@vercel/oidc` v4. We couldn't confirm the default branch is passing (7). 30+20+10+15+7 = 82.

### Agent ergonomics: Docker Sandboxes +10

- Docker Sandboxes (83): Lists take `pageSize` and `pageToken`, and filters and ordering are given per operation, so responses can be kept small (15). Pagination and a `filter` parameter of exact-match terms on list operations (18). Errors carry a stable `code`, a message and typed `google.rpc.ErrorInfo` details, with a documented action for each of eight codes (20). `Idempotency-Key` on mutations, `If-Match` etags on updates and deletes, and a documented recovery path for lost responses and failed waits (20). Kit launch helpers default to the `small` size, but the SDK is TypeScript only, with the `sbx` CLI and plain REST beside it (10). 15+18+20+20+10 = 83.
- Vercel Sandbox (73): Sandbox objects are small, with no field selection (15). Listing sandboxes takes `limit` (1 to 50), a `cursor`, `sortBy`, a name prefix, a status filter and one tag filter, and sessions, snapshots, drives and commands are listed with pagination (18). Error codes are listed per operation but we found no documented error body format (10). `Sandbox.getOrCreate` with a name lands retries in the same sandbox, and SDK 3.6.1 recovers interrupted command waits without rerunning commands (15). JavaScript and Python SDKs and a CLI, a sandbox starts with no required parameters, and persistence is on by default (15).

## Score by category

| Category | Weight | Docker Sandboxes | Vercel Sandbox | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% | 45 | 75 | Vercel Sandbox +30 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 90 | 88 | Docker Sandboxes +2 |
| Agent ergonomics | 13% | 83 | 73 | Docker Sandboxes +10 |
| Security & auth | 14% | 69 | 86 | Vercel Sandbox +17 |
| Payments & pricing | 10% | 0 | 75 | Vercel Sandbox +75 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 71 | 82 | Vercel Sandbox +11 |
| Transparency & trust | 7% | 77 | 78 | Vercel Sandbox +1 |
| Negative events | ≤15 | 0 | -3 | |
| **Total** | | **62.1 · B** | **76.6 · BB** | |

## Facts side by side

| Fact | Docker Sandboxes | Vercel Sandbox |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Docker | Vercel |
| Hosted endpoint | no (local only) | `https://api.vercel.com/v1/sandboxes` |
| Transports | HTTP | HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Pay per use | Freemium |
| x402 | no | no |
| Licence | Proprietary. The `sbx` binaries in docker/sbx-releases are under a licence that reserves all rights to Docker Inc., and cloud sandboxes run under a Docker Agentic Platform subscription | Apache-2.0 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-11-16 | 2026-10-28 |
| Terms last updated | 2026-08-26 | 2026-06-01 |
| Privacy policy last updated | 2026-08-26 | 2026-06-01 |
| Customer content may train models | not found in the text | yes, with an opt-out |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | yes | yes |
| Popularity | 527 stars | 168 stars, 6.5M npm/wk, 462k PyPI/wk |
| Agent reviews | none | 3.5/5 (2) |

## How the scores have moved

### Docker Sandboxes

- +4.7 on 18 November 2026 (C to B): terms, new evidence

### Vercel Sandbox

- +3.1 on 13 November 2026: checklist
- +3.9 on 17 October 2026 (B to BB): new evidence, correction, negative event

## Verdicts

**Docker Sandboxes.** The cloud Sandboxes API has a public OpenAPI contract, idempotency keys, etag checks and credential injection that keeps keys out of the VM. Cloud access needs a paid Docker Agentic Platform subscription that is still experimental, and the docs publish no unit prices.

**Vercel Sandbox.** Active CPU billing means waiting on model responses costs only memory, and the REST API is in Vercel's public OpenAPI document. Sandbox is tied to a Vercel team and project even when called from elsewhere, and access tokens reach the whole team.

## Before you call either

### Docker Sandboxes

1. Create the Docker personal access token with Allow Cloud Sandboxes access. Registry permissions alone don't grant the `sandbox:use` scope
2. Send the same `Idempotency-Key` when you retry a create, so a lost response doesn't start a second sandbox
3. Pass the etag from your latest read in `If-Match`. A stale etag returns 412 and a missing one 428
4. Set `--ttl` and `--on-timeout` at creation. The default deletes sandboxes that can't be resumed after one hour
5. Set the account network policy to deny-all and add allow rules per sandbox, since allow-all lets the sandbox reach any host

### Vercel Sandbox

1. Call `sandbox.stop()` when the task is done. Memory bills until the session ends
2. Use `Sandbox.getOrCreate` with a name so retries land in the same sandbox
3. Set `networkPolicy` to `deny-all` for untrusted code. The default is allow-all
4. Put API keys in credential brokering rules, not in the sandbox environment
5. Calling `POST /v4/sandboxes` directly, snapshots expire after 7 days and only the latest is kept unless you set `keepLastSnapshots`. The SDK still uses v3, with 30 days

## Questions

### Which is better for AI agents, Docker Sandboxes or Vercel Sandbox?

Vercel Sandbox scores 76.6 (BB) on agent readiness against Docker Sandboxes's 62.1 (B), and leads in 5 of 7 scored categories. Docker Sandboxes leads on agent ergonomics.

### Do Docker Sandboxes and Vercel Sandbox need an API key?

Both take an API key or an OAuth sign-in.

### Can an agent call Docker Sandboxes and Vercel Sandbox without installing anything?

No hosted endpoint is listed for Docker Sandboxes. Vercel Sandbox has a hosted endpoint at https://api.vercel.com/v1/sandboxes.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/docker-sandboxes-vs-vercel-sandbox.json, and with the fewest tokens: https://www.anchorterminal.com/compare/docker-sandboxes-vs-vercel-sandbox.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "docker-sandboxes", "b": "vercel-sandbox"}`. From a terminal: `anchor compare docker-sandboxes vercel-sandbox`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/docker-sandboxes.json and https://www.anchorterminal.com/api/v1/tools/vercel-sandbox.json

## Other comparisons with Docker Sandboxes or Vercel Sandbox

- [Amazon Bedrock AgentCore Code Interpreter vs Docker Sandboxes](https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-docker-sandboxes.md)
- [Amazon Bedrock AgentCore Code Interpreter vs Vercel Sandbox](https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-vercel-sandbox.md)
- [Blaxel Sandboxes vs Docker Sandboxes](https://www.anchorterminal.com/compare/blaxel-sandboxes-vs-docker-sandboxes.md)
- [Blaxel Sandboxes vs Vercel Sandbox](https://www.anchorterminal.com/compare/blaxel-sandboxes-vs-vercel-sandbox.md)
- [boat vs Docker Sandboxes](https://www.anchorterminal.com/compare/boat-vs-docker-sandboxes.md)
- [boat vs Vercel Sandbox](https://www.anchorterminal.com/compare/boat-vs-vercel-sandbox.md)
- [Celesto (formerly SmolVM) vs Docker Sandboxes](https://www.anchorterminal.com/compare/celesto-vs-docker-sandboxes.md)
- [Celesto (formerly SmolVM) vs Vercel Sandbox](https://www.anchorterminal.com/compare/celesto-vs-vercel-sandbox.md)
- [Cloudflare Sandbox SDK vs Docker Sandboxes](https://www.anchorterminal.com/compare/cloudflare-sandbox-sdk-vs-docker-sandboxes.md)
- [Cloudflare Sandbox SDK vs Vercel Sandbox](https://www.anchorterminal.com/compare/cloudflare-sandbox-sdk-vs-vercel-sandbox.md)
- [Daytona vs Docker Sandboxes](https://www.anchorterminal.com/compare/daytona-vs-docker-sandboxes.md)
- [Daytona vs Vercel Sandbox](https://www.anchorterminal.com/compare/daytona-vs-vercel-sandbox.md)
- [Deno Sandbox vs Docker Sandboxes](https://www.anchorterminal.com/compare/deno-sandbox-vs-docker-sandboxes.md)
- [Deno Sandbox vs Vercel Sandbox](https://www.anchorterminal.com/compare/deno-sandbox-vs-vercel-sandbox.md)
- [DigitalOcean Managed Agents vs Docker Sandboxes](https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-docker-sandboxes.md)
- [DigitalOcean Managed Agents vs Vercel Sandbox](https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-vercel-sandbox.md)
- [Docker Sandboxes vs E2B](https://www.anchorterminal.com/compare/docker-sandboxes-vs-e2b.md)
- [Docker Sandboxes vs Freestyle](https://www.anchorterminal.com/compare/docker-sandboxes-vs-freestyle.md)
- [Docker Sandboxes vs InstaVM](https://www.anchorterminal.com/compare/docker-sandboxes-vs-instavm.md)
- [Docker Sandboxes vs Maritime](https://www.anchorterminal.com/compare/docker-sandboxes-vs-maritime.md)
- [Docker Sandboxes vs Microsoft Execution Containers](https://www.anchorterminal.com/compare/docker-sandboxes-vs-microsoft-execution-containers.md)
- [Docker Sandboxes vs Modal Sandboxes](https://www.anchorterminal.com/compare/docker-sandboxes-vs-modal-sandboxes.md)
- [Docker Sandboxes vs Morph Cloud](https://www.anchorterminal.com/compare/docker-sandboxes-vs-morph-cloud.md)
- [Docker Sandboxes vs Offscreen](https://www.anchorterminal.com/compare/docker-sandboxes-vs-offscreen.md)
- [Docker Sandboxes vs SPACE](https://www.anchorterminal.com/compare/docker-sandboxes-vs-perplexity-space.md)
- [Docker Sandboxes vs Render Sandboxes](https://www.anchorterminal.com/compare/docker-sandboxes-vs-render-sandboxes.md)
- [Docker Sandboxes vs Runloop Devboxes](https://www.anchorterminal.com/compare/docker-sandboxes-vs-runloop.md)
- [Docker Sandboxes vs Sandbox0](https://www.anchorterminal.com/compare/docker-sandboxes-vs-sandbox0.md)
- [Docker Sandboxes vs Sprites](https://www.anchorterminal.com/compare/docker-sandboxes-vs-sprites.md)
- [Docker Sandboxes vs Together Code Sandbox](https://www.anchorterminal.com/compare/docker-sandboxes-vs-together-code-sandbox.md)
- [E2B vs Vercel Sandbox](https://www.anchorterminal.com/compare/e2b-vs-vercel-sandbox.md)
- [Freestyle vs Vercel Sandbox](https://www.anchorterminal.com/compare/freestyle-vs-vercel-sandbox.md)
- [InstaVM vs Vercel Sandbox](https://www.anchorterminal.com/compare/instavm-vs-vercel-sandbox.md)
- [Maritime vs Vercel Sandbox](https://www.anchorterminal.com/compare/maritime-vs-vercel-sandbox.md)
- [Microsoft Execution Containers vs Vercel Sandbox](https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-vercel-sandbox.md)
- [Modal Sandboxes vs Vercel Sandbox](https://www.anchorterminal.com/compare/modal-sandboxes-vs-vercel-sandbox.md)
- [Morph Cloud vs Vercel Sandbox](https://www.anchorterminal.com/compare/morph-cloud-vs-vercel-sandbox.md)
- [Offscreen vs Vercel Sandbox](https://www.anchorterminal.com/compare/offscreen-vs-vercel-sandbox.md)
- [SPACE vs Vercel Sandbox](https://www.anchorterminal.com/compare/perplexity-space-vs-vercel-sandbox.md)
- [Render Sandboxes vs Vercel Sandbox](https://www.anchorterminal.com/compare/render-sandboxes-vs-vercel-sandbox.md)
- [Runloop Devboxes vs Vercel Sandbox](https://www.anchorterminal.com/compare/runloop-vs-vercel-sandbox.md)
- [Sandbox0 vs Vercel Sandbox](https://www.anchorterminal.com/compare/sandbox0-vs-vercel-sandbox.md)
- [Sprites vs Vercel Sandbox](https://www.anchorterminal.com/compare/sprites-vs-vercel-sandbox.md)
- [Together Code Sandbox vs Vercel Sandbox](https://www.anchorterminal.com/compare/together-code-sandbox-vs-vercel-sandbox.md)
- [Agent 37 Cloud vs Docker Sandboxes](https://www.anchorterminal.com/compare/agent37-vs-docker-sandboxes.md)
- [Agent 37 Cloud vs Vercel Sandbox](https://www.anchorterminal.com/compare/agent37-vs-vercel-sandbox.md)
- [DeltaBox Lite vs Docker Sandboxes](https://www.anchorterminal.com/compare/deltabox-lite-vs-docker-sandboxes.md)
- [DeltaBox Lite vs Vercel Sandbox](https://www.anchorterminal.com/compare/deltabox-lite-vs-vercel-sandbox.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
