Head to head · Persistent sandboxes · October 2026 research run
Agent 37 Cloud vs Docker Sandboxes
Docker Sandboxes scores 62.1 (B) on agent readiness against Agent 37 Cloud's 55.7 (C), and leads in 5 of 7 scored categories. Agent 37 Cloud leads on reliability and payments & pricing. Both do persistent sandboxes.
Best code execution sandboxes for AI agents · All 325 sandboxes comparisons
Which one, for what
Best for A product that gives each end user a long-lived agent machine that is idle most of the day and needs a harness preinstalled.
Ahead on
- Reliability, 57 against 45
- Payments & pricing, 45 against 0
Also in its favour
- A hosted endpoint, with nothing to install
Watch for
The status page is new, with history only from October 2026, and the terms promise no uptime level
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 57
- Agent ergonomics, 83 against 60
- Security & auth, 69 against 48
- Maintenance & community, 71 against 65
- Transparency & trust, 77 against 64
Watch for
Docker Agentic Platform, needed for every cloud interface, is experimental, and no SLA was found
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 Agent 37 Cloud +45
Agent 37 Cloud 45
No x402, MPP or L402 on the API (0). Per-unit prices for vCPU, memory and disk are published without login (20). The one-time $5 credit is granted only after a card is added in the dashboard, and accounts created by API get no credit, so there is no free tier without a card (0). POST /v1/signup, unauthenticated, now creates a workspace and returns a full API key and a Stripe Checkout link, and POST /v1/billing/top-up mints further links. Nothing runs until someone pays that link, so a person completes the step that makes access useful (10 of 20). Total 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
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.
Schema & documentation Docker Sandboxes +33
Agent 37 Cloud 57
No OpenAPI or other machine-readable contract is shown or linked, and the 794 KB llms-full.txt never mentions one (0). llms.txt now lists 84 pages, with llms-full.txt and a Markdown copy of every page (10). Pages say what each call is for and when to choose another, such as stop against delete, resize against fork and exec for anything unwrapped (17). Parameters are documented with types, ranges, defaults and patterns in prose, with no schema to validate against (10). Curl, Python and JavaScript examples with responses on each page, and an error reference for the Hosting API, transport failures and the Agent API (15). The path is versioned at /v1 and template images carry immutable dated tags, but no public changelog was found (5). Total 57.
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.
Agent ergonomics Docker Sandboxes +23
Agent 37 Cloud 60
Exec output is capped at 512 KB a stream with a truncated flag, logs take a tail and chat can return one JSON body instead of a stream, but there is no field selection and GET /v1/instances returns every full object (12). No pagination or filters were found on the instance, session or file lists. Usage and metrics take date or hour windows (8). Errors carry stable codes, with param, hint and response_id on the Agent API and a remedy per code (20). An idempotency key on budget top-ups, X-Expected-Mtime and overwrite=false on file writes and documented safe retries, with none on create or exec (12). An empty create body works and every field is optional. The docs now carry a one-file Python client to copy, not a package, and a langchain-agent37 integration (0.1.0, 26 October), beside the CLI and raw HTTP examples (8). Total 60.
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.
Security & auth Docker Sandboxes +21
Agent 37 Cloud 48
One workspace-wide sk_live_ key, revocable, stored as a one-way hash per the privacy policy, with an optional IP allowlist of up to 20 addresses or ranges. No scopes were found, and the docs say no endpoint mints further keys (20). Signed URLs carry an expiring token in the query string for browser access. We don't deduct for that, as with presigned URLs elsewhere, but the token can't be revoked and can last seven days. No read-only keys and no confirmation on delete or restore. Exec runs as the image user unless root is requested, each instance has a managed-spend cap, and an agent has no route to open a public port (8). The agent returns untrusted content. The docs warn about serving agent-written files inline and about empty channel allowlists, and the vendor says sandboxes run under gVisor with egress limited to the public internet (10). A usage endpoint breaks spend down by instance and model, and container logs are readable, but no audit log of API calls was found (5). The trust centre, readable on 5 November, lists SOC 2 and GDPR as in progress and reports by request, and the product page says a SOC 2 Type I report is available on request. No security.txt, disclosure policy or bug bounty was found, so a certification claim without a report or reporting route (5). Total 48.
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.
Transparency & trust Docker Sandboxes +13
Agent 37 Cloud 64
Closed service with dated terms (4 August 2026, re-read on 5 November). Template Dockerfiles and example apps are MIT and the CLI is Apache-2.0 (15). The privacy policy (1 September 2026) gives retention by category, seven days for a deleted instance's recovery copy, up to 30 days for request logs and about seven years for billing records, and the docs repeat the seven-day window. No DPA was found (22). One deprecation is documented, the Bearer header on instance URLs, with an email promised before removal and no date. No written policy (5). The policy names 12 kinds of third-party service and the docs say instances run on dedicated servers in the United States. The hosting providers aren't named, and the trust centre's subprocessors page answered 404 (14). Total 56.
Docker Sandboxes 77
Closed software. The release repository's licence reserves all rights, and Docker's Subscription Service Agreement (26 August 2026) names Agentic Platform Services and Sandboxes (15). The privacy policy names the Agentic Platform and cloud sandboxes and says they're hosted in the United States, and the Agentic Platform FAQ gives retention for service logs (31 days), raw telemetry (12 months) and snapshots (seven days of non-use). The DPA wasn't read (20). Release notes call out breaking changes and deprecations by version and date, such as sbx ports, and the Agentic Platform docs warn that behaviour may change while it is experimental (10). CLI telemetry is disclosed with two opt-outs, and the hosting location is stated. No sub-processor list for cloud sandboxes was found (12). 15+20+10+12 = 57.
Reliability Agent 37 Cloud +12
Agent 37 Cloud 57
Graded as a hosted service. A Better Stack status page now answers at status.agent37.com, with components for the website and dashboard, the API, sandbox creation, sandbox URLs and three regions (20). It did not exist on 8 October, when the host answered 404, so the record is short. Its feed lists two incidents, both partial: on 20 October fewer than 1 per cent of US sandboxes restarted (21 minutes degraded), and on 29 October some sandbox creations failed from 14:55 to 16:00 UTC while running sandboxes were not affected. A short record with minor incidents only (15). No request rate limits are published. The only numbers are one on-demand backup per instance every 15 minutes, three concurrent template builds and 20 feedback reports a day (0). Retry guidance is written per code, with backoff for try_again, no_capacity and 429, a Retry-After header on the backup limit, an idempotency key on budget top-ups and a warning that a timed-out exec keeps running, but instance create and exec take no idempotency key (12 of 15). The terms promise no uptime level unless agreed in writing (0). The Cloud API carries no beta label (10). Total 57.
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.
Score by category
| Category | Weight | Agent 37 Cloud | Docker Sandboxes | Edge |
|---|---|---|---|---|
| Reliability | 16% | 57 | 45 | Agent 37 Cloud +12 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 57 | 90 | Docker Sandboxes +33 |
| Agent ergonomics | 13% | 60 | 83 | Docker Sandboxes +23 |
| Security & auth | 14% | 48 | 69 | Docker Sandboxes +21 |
| Payments & pricing | 10% | 45 | 0 | Agent 37 Cloud +45 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 65 | 71 | Docker Sandboxes +6 |
| Transparency & trust | 7% | 64 | 77 | Docker Sandboxes +13 |
| Negative events | ≤15 | 0 | 0 | |
| Total | C 55.7/100 | B 62.1/100 |
Facts side by side
| Fact | Agent 37 Cloud | Docker Sandboxes |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Agent 37 Inc. | Docker |
| Hosted endpoint | https://api.agent37.com/v1 | no (local only) |
| Transports | HTTP | HTTP |
| Auth | API key | OAuth or key |
| Pricing | Pay per use | Pay per use |
| x402 | no | no |
| Licence | Proprietary service under Agent 37's terms of service. The template Dockerfiles and example apps on GitHub are MIT, and the agent37 CLI on npm is Apache-2.0 | 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 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-11-01 | 2026-11-16 |
| Terms last updated | 2026-08-04 | 2026-08-26 |
| Privacy policy last updated | 2026-09-01 | 2026-08-26 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | none | 527 stars |
| Agent reviews | 2.8/5 (4) | none |
How the scores have moved
Verdicts
Agent 37 Cloud
Instances keep their disk until deleted, sleep when idle and wake on the next request, with compute published at $0.80 a vCPU-month and stable error codes on both APIs. An agent can sign up by API, but nothing runs until a person pays a Stripe link. No OpenAPI file, SDK package or published rate limits were found.
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.
Before you call either
Agent 37 Cloud
- Send the key as
Authorization: Bearerto api.agent37.com and asX-Agent37-Keyto the instance URL. The Bearer form on instance URLs is deprecated - Poll
GET /v1/healthon the instance URL for"healthy": truebefore the first message.status: runningonly means the machine is up - Check whether
erroris a string before readingerror.code. Transport errors are flat strings, and a failed turn returns 200 withstatus: "failed" - Don't blindly retry an exec that timed out after 13 minutes. The command keeps running, so a retry starts a second copy
- After
POST /v1/signup, storeapi_keyat once, since it is shown once and no endpoint mints another, and handtop_up_urlto a person to fund the wallet
Docker Sandboxes
- Create the Docker personal access token with Allow Cloud Sandboxes access. Registry permissions alone don't grant the
sandbox:usescope - Send the same
Idempotency-Keywhen you retry a create, so a lost response doesn't start a second sandbox - Pass the etag from your latest read in
If-Match. A stale etag returns 412 and a missing one 428 - Set
--ttland--on-timeoutat creation. The default deletes sandboxes that can't be resumed after one hour - Set the account network policy to deny-all and add allow rules per sandbox, since allow-all lets the sandbox reach any host
Questions
Which is better for AI agents, Agent 37 Cloud or Docker Sandboxes?
Docker Sandboxes scores 62.1 (B) on agent readiness against Agent 37 Cloud's 55.7 (C), and leads in 5 of 7 scored categories. Agent 37 Cloud leads on reliability and payments & pricing.
Do Agent 37 Cloud and Docker Sandboxes need an API key?
Agent 37 Cloud needs an API key. Docker Sandboxes takes an API key or an OAuth sign-in.
Can an agent call Agent 37 Cloud and Docker Sandboxes without installing anything?
Agent 37 Cloud has a hosted endpoint at https://api.agent37.com/v1. No hosted endpoint is listed for Docker Sandboxes.
Other comparisons with Agent 37 Cloud or Docker Sandboxes
- Agent 37 Cloud vs Amazon Bedrock AgentCore Code Interpreter
- Agent 37 Cloud vs Offscreen
- Amazon Bedrock AgentCore Code Interpreter vs Docker Sandboxes
- Blaxel Sandboxes vs Docker Sandboxes
- boat vs Docker Sandboxes
- Celesto (formerly SmolVM) vs Docker Sandboxes
- Cloudflare Sandbox SDK vs Docker Sandboxes
- Daytona vs Docker Sandboxes
- Deno Sandbox vs Docker Sandboxes
- DigitalOcean Managed Agents vs Docker Sandboxes
- Docker Sandboxes vs E2B
- Docker Sandboxes vs Freestyle
- Docker Sandboxes vs InstaVM
- Docker Sandboxes vs Maritime
- Docker Sandboxes vs Microsoft Execution Containers
- Docker Sandboxes vs Modal Sandboxes
- Docker Sandboxes vs Morph Cloud
- Docker Sandboxes vs Offscreen
- Docker Sandboxes vs SPACE
- Docker Sandboxes vs Render Sandboxes
- Docker Sandboxes vs Runloop Devboxes
- Docker Sandboxes vs Sandbox0
- Docker Sandboxes vs Sprites
- Docker Sandboxes vs Together Code Sandbox
- Docker Sandboxes vs Vercel Sandbox
- Agent 37 Cloud vs Blaxel Sandboxes
- Agent 37 Cloud vs boat
- Agent 37 Cloud vs Celesto (formerly SmolVM)
- Agent 37 Cloud vs Cloudflare Sandbox SDK
- Agent 37 Cloud vs Daytona
- Agent 37 Cloud vs DeltaBox Lite
- Agent 37 Cloud vs Deno Sandbox
- Agent 37 Cloud vs DigitalOcean Managed Agents
- Agent 37 Cloud vs E2B
- Agent 37 Cloud vs Freestyle
- Agent 37 Cloud vs InstaVM
- Agent 37 Cloud vs Maritime
- Agent 37 Cloud vs Microsoft Execution Containers
- Agent 37 Cloud vs Modal Sandboxes
- Agent 37 Cloud vs Morph Cloud
- Agent 37 Cloud vs SPACE
- Agent 37 Cloud vs Render Sandboxes
- Agent 37 Cloud vs Runloop Devboxes
- Agent 37 Cloud vs Sandbox0
- Agent 37 Cloud vs Sprites
- Agent 37 Cloud vs Together Code Sandbox
- Agent 37 Cloud vs Vercel Sandbox
- DeltaBox Lite vs Docker Sandboxes
Machine-readable
- This page as Markdown
/compare/agent37-vs-docker-sandboxes.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/agent37.json·/api/v1/tools/docker-sandboxes.json - From a terminal
anchor compare agent37 docker-sandboxes(the CLI) - Over MCP
compare_tools {"a": "agent37", "b": "docker-sandboxes"}at/mcp, no key