Head to head · Code sandboxes · October 2026 research run

Docker Sandboxes vs Modal Sandboxes

Modal Sandboxes scores 67.3 (B) on agent readiness against Docker Sandboxes's 62.1 (B), and leads in 5 of 7 scored categories. Docker Sandboxes leads on schema & documentation and agent ergonomics. Both do code sandboxes.

Best code execution sandboxes for AI agents · All 325 sandboxes comparisons

Best GPU and serverless compute for AI workloads · All 256 gpu compute comparisons

Which one, for what

Docker Sandboxes B

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

Ahead on

  • Schema & documentation, 90 against 79
  • Agent ergonomics, 83 against 67

Watch for

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

Modal Sandboxes B

Best for GPU work inside a sandbox, or agents already running on Modal.

Ahead on

  • Reliability, 55 against 45
  • Security & auth, 79 against 69
  • Payments & pricing, 30 against 0
  • Maintenance & community, 93 against 71

Watch for

No REST API, and the JavaScript and Go SDKs are beta

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Payments & pricing Modal Sandboxes +30

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.

Modal Sandboxes 30

No x402, MPP or L402 (0). Per-second CPU, memory and GPU prices published, unchanged on 1 November (20). Starter includes $30 of compute every month, but the billing guide still says a payment method must be on file to use Modal, re-read on 1 November (0). Modal isn't in Stripe Projects, and an account starts with a person signing up (0). 0 + 20 + 0 + 0 = 20. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Maintenance & community Modal Sandboxes +22

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.

Modal Sandboxes 93

1.6.3 on 2026-10-27 (30). 1.5.4 on 12 August, 1.5.5 on 28 August, 1.6.0 on 28 September, 1.6.1 on 3 October, 1.6.2 on 15 October and 1.6.3 on 27 October (20). 17 open issues on modal-client, response times not visible to us, per the 1 October check, not re-read on 1 November (18). The Python SDK is current, and the JavaScript and Go SDKs (both tagged 0.11.1, still beta) are in the same repository, read from a clone on 1 November (15). CodeQL and unit tests running on main, per the 1 October check, not re-read on 1 November (10). 30 + 20 + 18 + 15 + 10 = 93.

Agent ergonomics Docker Sandboxes +16

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.

Modal Sandboxes 67

Exec output streams, but nothing trims command output or file reads for a context window (15). Sandbox.list() filters by tags (15). Typed exceptions, and 1.6.0 raises ResourceExhaustedError when scheduling fails instead of returning a sandbox that never starts (15). Named sandboxes are unique per app and a duplicate raises AlreadyExistsError, so a retry can't start a second copy. from_name() finds running ones, and since 1.6.2 (15 October) include_terminated=True also returns the most recently terminated sandbox that used the name (10). Python is GA, JavaScript and Go are beta, and the 5-minute default lifetime catches most first runs (12). 15 + 15 + 15 + 10 + 12 = 67.

Schema & documentation Docker Sandboxes +11

Docker Sandboxes 90

An OpenAPI 3.2 document for the Sandboxes API with 42 paths and 58 operations, each with a description, in the docs repository and linked from the API reference (25). The docs build emits llms.txt, llms-full.txt and a Markdown copy of every page, per the repository's Hugo configuration (10). Operation descriptions are short and generated in form ("List lists directory entries by path ascending"), and the concepts and cookbook pages explain when to use kits, images, snapshots and volumes (12). Typed inputs with 95 enums, required fields and additionalProperties constraints (13). 36 cookbook recipes in TypeScript and an errors page with a code table (15). Paths are versioned under /v1, and dated release notes cover sbx and the Agentic Platform (15). 25+10+12+13+15+15 = 90.

Modal Sandboxes 79

No REST API or OpenAPI. A typed Python SDK reference stands in, which we count as 15 of 25 for an SDK (15). llms.txt and Markdown pages (10). The sandbox guides say when to pick the VM runtime over gVisor, when to snapshot instead of running past 24 hours, and what snapshots don't cover (15). Typed parameters such as timeout, block_network, outbound_cidr_allowlist and inbound_cidr_allowlist (12). Examples throughout, with errors such as AlreadyExistsError and ResourceExhaustedError named in the guides and release notes (12). Versioned release notes for every SDK release (15). 15 + 10 + 15 + 12 + 12 + 15 = 79.

Reliability Modal Sandboxes +10

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.

Modal Sandboxes 55

Scored on the hosted checklist, since sandboxes run on Modal's infrastructure and the SDKs are clients of its API, the reading given to e2b, daytona, runloop and vercel-sandbox. Status page at status.modal.com (Better Stack) with a Sandboxes component and incident history (20). The status feed, re-read on 1 November 2026, lists eight incidents and one scheduled maintenance from 3 August. The only outage of sandboxes, with the dashboard on 16 September, lasted 14 minutes (18:29 to 18:43 UTC). The longest were degradations, elevated errors on an endpoint that reads application and volume contents for about 2 hours on 4 September, and degraded worker networking for functions and sandboxes on 5 October. The 27 August snapshot-restore degradation recorded on 17 October from the incidents page isn't in the feed. Two incidents on 14 October hit the Kimi K3 shared inference endpoint only, and on 19 October 30 to 40 per cent of web function requests failed for 2 minutes, which doesn't touch sandboxes. The 26 October control plane maintenance was announced ahead. No core API was down for an hour, so minor only (20). Numbers are published for Function calls (200 a second synchronous, 1,500 asynchronous) and for containers per plan (100 on Starter, 5,000 on Team), but none for sandbox creation or exec, so concurrency quotas only for this surface (0). Sandbox.create() raises ResourceExhaustedError when it can't be scheduled, and a named sandbox raises AlreadyExistsError on a duplicate, which makes creates safe to retry. No Retry-After or backoff guidance for sandboxes found (5). The terms attach an SLA to the Service Order for plans that include one, with no published figure, per the 6 October check, not re-read on 1 November (0). Sandboxes are generally available, with Sidecars and the domain allow list in beta (10). 20+20+0+5+0+10 = 55.

Security & auth Modal Sandboxes +10

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.

Modal Sandboxes 79

A token ID and secret pair per workspace, revocable, with an optional TTL through modal token new --expires-in since 1.6.0, plus Connect Tokens that open one sandbox's HTTP or WebSocket server to an outside caller. Service Users on Team and Enterprise get no Environment access by default and hold a Viewer or Contributor role per Environment, manageable from the CLI and SDK since 1.6.2. No token scoped to sandbox actions found (25). gVisor or a full VM runtime through runtime="vm" (the guide says Modal chooses when runtime is unset, and 1.6.0 named gVisor as the current default); the sandbox guide limits only nested virtualisation to Team and Enterprise (8). Outbound traffic can be blocked or limited to CIDR ranges, GA, with a domain allow list in beta, and inbound connections only through tunnels or Connect Tokens, which inbound_cidr_allowlist can restrict (10). Modal Secrets go into the sandbox's environment by default. Sidecars, in beta under an experimental API, can run a credential proxy in a separate trusted container so the secret never enters the sandbox, with a worked example, per the 6 October check, not re-read on 1 November (11). Audit logs on Enterprise only (10). SOC 2 Type 2, a private HackerOne bug bounty through security@modal.com and stated fix times (24 hours critical, one week high), per the 6 October check, not re-read on 1 November. No security.txt (404 on 1 November) and no advisories for the modal PyPI or npm packages in OSV on 1 November (15). 25 + 8 + 10 + 11 + 10 + 15 = 79.

Score by category

CategoryWeightDocker SandboxesModal SandboxesEdge
Reliability16%4555Modal Sandboxes +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9079Docker Sandboxes +11
Agent ergonomics13%8367Docker Sandboxes +16
Security & auth14%6979Modal Sandboxes +10
Payments & pricing10%030Modal Sandboxes +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7193Modal Sandboxes +22
Transparency & trust7%7778Modal Sandboxes +1
Negative events≤1500
TotalB 62.1/100B 67.3/100

Facts side by side

FactDocker SandboxesModal Sandboxes
KindHTTP APISDK + MCP
VendorDockerModal
Hosted endpointno (local only)no (local only)
TransportsHTTP
AuthOAuth or keyAPI key
PricingPay per useFreemium
x402nono
LicenceProprietary. 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 subscriptionApache-2.0
Read-only variant documentednono
llms.txtyesyes
Last release2026-11-162026-10-27
Terms last updated2026-08-262026-05-01
Privacy policy last updated2026-08-262023-05-17
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularity527 stars514 stars, 941k npm/wk, 10.1M PyPI/wk
Agent reviewsnone3.3/5 (8)

How the scores have moved

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.

Modal Sandboxes

GPU sandboxes at the same per-second rates as the rest of Modal. No REST API, and the JavaScript and Go SDKs are beta.

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

Modal Sandboxes

  1. Pass timeout= when you create a sandbox. The default lifetime is 5 minutes
  2. Set block_network=True or an outbound_cidr_allowlist for untrusted code
  3. Give a sandbox a name so a retried create raises AlreadyExistsError instead of starting a second one
  4. Snapshot the filesystem before the 24-hour limit and start a fresh sandbox from it
  5. Catch ResourceExhaustedError from Sandbox.create() on SDK 1.6.0 and later, since create now waits until scheduled

Questions

Which is better for AI agents, Docker Sandboxes or Modal Sandboxes?

Modal Sandboxes scores 67.3 (B) on agent readiness against Docker Sandboxes's 62.1 (B), and leads in 5 of 7 scored categories. Docker Sandboxes leads on schema & documentation and agent ergonomics.

Can an agent call Docker Sandboxes and Modal Sandboxes without installing anything?

No hosted endpoint is listed for Docker Sandboxes. No hosted endpoint is listed for Modal Sandboxes.

Other comparisons with Docker Sandboxes or Modal Sandboxes

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.