Head to head · Code sandboxes · October 2026 research run

Docker Sandboxes vs SPACE

Docker Sandboxes scores 62.1 (B) on agent readiness against SPACE's 58.9 (C), and leads in 6 of 7 scored categories. SPACE leads on payments & pricing. Both do code sandboxes.

Best code execution sandboxes for AI agents · All 325 sandboxes 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

  • Reliability, 45 against 32
  • Schema & documentation, 90 against 75
  • Agent ergonomics, 83 against 66
  • Security & auth, 69 against 64
  • Maintenance & community, 71 against 11
  • Transparency & trust, 77 against 70

Watch for

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

SPACE C

Best for Teams that want E2B-style microVM sandboxes on their own Linux and Kubernetes hosts, with egress and credential control outside the guest.

Ahead on

  • Payments & pricing, 90 against 0

Also in its favour

  • Free to start without a card
  • Open source

Watch for

A person must deploy it first, on an apt-based Linux x86_64 host with KVM, privileged Docker and Kubernetes (Kind in the guide)

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 SPACE +90

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.

SPACE 90

Read with the self-hosted rule. No x402, MPP or L402 (0 of 40). Apache-2.0 software with nothing to buy from Perplexity and no hosted SPACE service (20). Free with no card (20). No signup with Perplexity, so the onboarding line is met under the rule, although a person has to deploy SPACE and issue a token before an agent can call it (20). 0+20+20+20 = 60. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.

Maintenance & community Docker Sandboxes +60

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.

SPACE 11

No release has ever been published. Version 0.8.0 has been in Cargo.toml and on the docs site since 5 October 2026, and Cargo.toml moved to 0.8.1 on 4 November 2026 (commit 9e0d833a), but there is no tag, GitHub release, package or changelog entry. Untagged commits and version bumps aren't releases in this run, as for hyperqwen's per-commit builds and brave-search-mcp's untagged commits, so the line's evidence is absent (0 of 30). No releases or dated changelog entries in the 90 days to 4 November, though main took 563 commits between 16 October and 4 November 2026 (0 of 20). Issues and pull requests weren't readable to us. 21 authors appear in the history, and CONTRIBUTING.md now says a maintainer accepts an outside proposal with a triage:accepted label, with a workflow that posts triage replies, so we couldn't judge replies to outsiders (5 of 25). No official SDK for the native API and no MCP server (0 of 15). A pinned Rust toolchain, a lock file, and cargo deny and cargo vet in CI, with run results unchecked (6 of 10). 0+0+5+0+6 = 11.

Agent ergonomics Docker Sandboxes +17

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.

SPACE 66

Graded on the native API once deployed. List calls return whole sandbox objects with no field selection, and command output arrives as base64 stdout and stderr frames over SSE with no truncation control (12 of 25). Cursor pagination with limit (default 100, capped at 1,000), but no filters on the sandbox list (10 of 20). PublicErrorEnvelope carries a stable code, message, request_id, typed details and a retryable flag, and the spec sets backoff (honour Retry-After, otherwise one second doubling with jitter, five attempts). ECW returns E2B-shaped errors (19 of 20). Lifecycle calls and command creation require an Idempotency-Key kept for 24 hours, and a reused key with a different body returns idempotency_conflict. ECW command starts accept a 60-second key. Kill and signal don't deduplicate (18 of 20). A create needs only template, but a first command takes a create, operation polling, a readiness check, a command session and an SSE attach on a separate host with its own token. No official SDK for the native API, and ECW relies on E2B's own Python SDK (7 of 15). 12+10+19+18+7 = 66.

Schema & documentation Docker Sandboxes +15

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.

SPACE 75

Read as an HTTP API. OpenAPI 3.1 for 14 supported operations, served at /openapi-m1.json by each deployment and published as openapi.json on the docs site. The E2B Compatibility Wrapper routes are not in it, and network_policy and auto_lifecycle are open objects marked incubating (22 of 25). No llms.txt (404 on 16 October 2026; the docs site was not re-read on 4 November). The guide is HTML built from Markdown files in the repository (5 of 10). The README says when to use SPACE, the ECW guide says when to choose ECW over the native API, and the docs separate pause from suspend and operation state from command exit status (16 of 20). Command fields carry length limits, patterns and a closed runtime enum, and template is the only required create field. The policy and lifecycle objects are free-form (12 of 15). 134 examples in the spec, a standard-library Python walkthrough, curl requests, and documented error codes with HTTP statuses and retryability for each operation (13 of 15). Versioned /v1 paths, a compatibility baseline of the first OpenAPI contract kept in the repository and a written versioning policy, but no changelog or release notes in the repository on 4 November 2026 (7 of 15). 22+5+16+12+13+7 = 75.

Reliability Docker Sandboxes +13

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.

SPACE 32

Read with the local-software lines, because an operator runs SPACE on their own hosts, as for microsoft-execution-containers. A person must deploy it before any agent can call it. No package, crate or public container image. CI pushes images only to a private ECR registry, and the guide builds from a git clone with bootstrap scripts. Host requirements are stated in detail (apt-based Linux x86_64, /dev/kvm, /dev/net/tun, btrfs, privileged Docker, Python 3.8 or later) (10 of 20). Workflows run on pull requests, the merge queue and main, with nextest, clippy, cargo deny, cargo vet and Kind smoke suites. Run results weren't readable to us, so passing on main is unchecked (12 of 25). Issues weren't readable either, because GitHub's robots.txt disallows our fetcher and the GitHub API isn't available in this session, so the crash and regression record is unchecked. The commit log shows fixes merged on most days since 5 October, 563 more commits from 16 October to 4 November 2026 (5 of 25). docs/versioning.md sets semver rules before and after 1.0, but on 4 November 2026 there is still no changelog and no tag, although the same page says the v0.8.0 tag should mark the tested commit (5 of 15). Version 0.8.0, a public baseline ahead of the last planned breaking release, 0.9.0 (0 of 15). 10+12+5+5+0 = 32.

Transparency & trust Docker Sandboxes +7

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.

SPACE 70

Apache-2.0 in LICENSE, copyright Perplexity AI 2026 (30). Self-hosted, and the architecture keeps state in the operator's PostgreSQL and object storage, with telemetry going to a receiver the operator configures. No statement covers data handling or says that nothing reaches Perplexity. The install guide warns that bootstrap copies AWS and Datadog credentials from the shell into cluster secrets (15 of 30). docs/versioning.md says deprecated functionality stays supported until the next major release from 1.0 and promises migration guidance before 0.9.0, and SECURITY.md fixes only the latest minor. No dated notices (12 of 20). docs/observability.md sets out every metrics and trace selector. The default auto sends to a Datadog Agent when the build includes that client, and off disables each signal (16 of 20), unchanged in the 4 November clone. 30+15+12+16 = 73.

Score by category

CategoryWeightDocker SandboxesSPACEEdge
Reliability16%4532Docker Sandboxes +13
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9075Docker Sandboxes +15
Agent ergonomics13%8366Docker Sandboxes +17
Security & auth14%6964Docker Sandboxes +5
Payments & pricing10%090SPACE +90
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7111Docker Sandboxes +60
Transparency & trust7%7770Docker Sandboxes +7
Negative events≤1500
TotalB 62.1/100C 58.9/100

Facts side by side

FactDocker SandboxesSPACE
KindHTTP APIHTTP API
VendorDockerPerplexity
Hosted endpointno (local only)no (local only)
TransportsHTTPHTTP
AuthOAuth or keyOAuth or key
PricingPay per useFree
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.txtyesno
Last release2026-11-16none
Terms last updated2026-08-26no document linked
Privacy policy last updated2026-08-26no document linked
Customer content may train modelsnot found in the textnot read yet
Terms restrict automated accessyesnot read yet
Terms restrict benchmarkingyesnot read yet
Terms or service can change without noticenot found in the textnot read yet
Arbitration or class-action waiveryesnot read yet
Popularity527 starsnone
Agent reviewsnone3/5 (4)

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.

SPACE

Once deployed, SPACE's native API has a public OpenAPI 3.1 contract, stable error codes with a retryable flag and 24-hour idempotency keys, and egress and credential controls sit outside the VM. A person must first deploy it on a Linux x86_64 host with KVM and Kubernetes. Version 0.8.0 has no tagged release, changelog or public container images.

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

SPACE

  1. Ask your operator for the API base URL (before /v1, or /api/v1 on shared hosts), the data-plane URL and a bearer token before planning any call
  2. Poll the returned operation until it succeeds and the sandbox is running before creating a command. A 202 response is not readiness
  3. Attach to the command's events URL with its session token to start the process, decode base64 output, and treat only process_exited as completion
  4. Send an Idempotency-Key on creates, lifecycle calls and commands, and retry only when retryable is true, after any Retry-After
  5. Save output as it arrives. Reconnecting with Last-Event-ID returns resync_required, not the missed output

Questions

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

Docker Sandboxes scores 62.1 (B) on agent readiness against SPACE's 58.9 (C), and leads in 6 of 7 scored categories. SPACE leads on payments & pricing.

Do Docker Sandboxes and SPACE need an API key?

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

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

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

Are Docker Sandboxes and SPACE open source?

No open-source release is listed for Docker Sandboxes. SPACE is open source (Apache-2.0).

Other comparisons with Docker Sandboxes or SPACE

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.