Head to head · Code sandboxes · October 2026 research run

Docker Sandboxes vs Microsoft Execution Containers

Microsoft Execution Containers scores 77.1 (BB) on agent readiness against Docker Sandboxes's 62.1 (B), and leads in 4 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

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 81
  • Agent ergonomics, 83 against 74

Also in its favour

  • No incidents deducted, where Microsoft Execution Containers loses 3 points for them

Watch for

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

Microsoft Execution Containers BB

Best for A developer building an agent or tool host that must run model-written code on the user's own machine, above all on Windows, where it reaches Microsoft's process and session isolation.

Ahead on

  • Reliability, 81 against 45
  • Payments & pricing, 90 against 0
  • Maintenance & community, 92 against 71
  • Transparency & trust, 84 against 77

Also in its favour

  • Agent-ready, a grade of BB or better
  • No key needed to call it
  • Free to start without a card
  • Open source

Watch for

1.0.1, the newest release on 1 November 2026, still grants read access to the whole system drive from the Windows tool-discovery helper when PowerShell is on PATH, fixed on main only

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 Microsoft Execution Containers +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.

Microsoft Execution Containers 90

Read with the self-hosted rule. No x402, MPP or L402 (0 of 40). MIT software with nothing to buy and no hosted option, so 20 for pricing, 20 for free use with no card and 20 because an agent can install it from npm with no account. 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.

Reliability Microsoft Execution Containers +36

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.

Microsoft Execution Containers 81

Read with the local-software lines, because MXC is a library the owner runs. Official packages on npm, NuGet and crates.io. Node.js 24 or later is stated and Windows 11 builds are listed per release, but the README gives no minimum host version for Linux or macOS (18 of 20). The Build workflow runs lint, Windows, Linux and macOS builds and SDK unit and integration tests on every push to main. Of the last 14 completed runs on main, 10 passed and 4 failed, and the newest (7 October 2026) passed, per the 8 October check, not re-read on 1 November because GitHub's web pages refused our reader. 47 commits on main from 17 to 30 October include CI fixes for nightly test failures (18 of 25). 38 open issues against 261 closed, ten of them labelled bug, and three outside reports from 24 September to 2 October with no reply, per the 8 October check, not re-read on 1 November (19 of 25). The changelogs follow Keep a Changelog with breaking changes marked, and the v1.0.0 release notes have a breaking-changes section. The Node and .NET changelogs still list the V1 changes under Unreleased on 1 November, with no 1.0.0 or 1.0.1 heading although 1.0.1 shipped on 17 October (11 of 15). Version 1.0.0, which the release notes call the first stable release, was published on 6 October 2026 and 1.0.1 on 17 October, and three backends are marked experimental (15). 18+18+19+11+15 = 81.

Maintenance & community Microsoft Execution Containers +21

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.

Microsoft Execution Containers 92

v1.0.1 on npm and crates.io on 17 October 2026, 15 days before the check, still the newest release on 1 November (30). Four npm releases in the 90 days from 3 August, 0.8.0 on 22 August, 0.9.0 on 28 September, 1.0.0 on 6 October and 1.0.1 on 17 October (the npm dates per the 17 October check, crates.io and the tags re-read on 1 November) (20). 261 issues closed against 38 open, with issue forms, triage labels and fixes that land within days, and three outside bug reports filed between 24 September and 2 October with no comment, per the 8 October check, not re-read on 1 November (19 of 25). Official SDKs for Node.js, .NET and Rust, all at 1.0.1 (15). A package-lock check, CodeQL and Dependabot in CI, with 47 commits on main from 17 to 30 October. The npm package has no repository field and no provenance attestation, per the 17 October check (8 of 10). 30+20+19+15+8 = 92.

Schema & documentation Docker Sandboxes +9

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.

Microsoft Execution Containers 81

Read as an SDK with a published request contract. A draft-07 JSON Schema for the stable 1.0.0 request sits in the repository, and the Node SDK ships TypeScript declarations (25). No llms.txt. The docs are Markdown files in the repository (5 of 10). The API reference states what each operation does and has a table for choosing between captured, piped and terminal execution, and the backend guides say which policies each backend enforces and which are cooperative (15 of 20). Containment is a closed union, network actions and clipboard levels are enums, the schema has 33 enums and 39 objects closed to extra properties, and 135 of 150 properties carry a description. command is one free string (13 of 15). Ten sample scenarios, each in Rust, .NET and Node. The 12 error codes are a closed type, but we found no page that explains each one (11 of 15). A versioned /v1 entry point, a schema version table with retired contracts, a changelog for each SDK and GitHub release notes. The Node changelog still has no 1.0.0 or 1.0.1 entry on 1 November (12 of 15). 25+5+15+13+11+12 = 81.

Agent ergonomics Docker Sandboxes +9

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.

Microsoft Execution Containers 74

One request type with command as the only required field, and run returns stdout, stderr, the exit code, a timeout flag and warnings. We found no documented cap on captured output, and the npm package is a 37.7 MB tarball (18 of 25). spawn streams output and timeoutMs bounds a run, but there is no truncation or size control on captured output (10 of 20). MxcError carries one of 12 codes with optional operation, native code and remediation, and a deny-and-record mode lists blocked accesses on ProcessContainer (18 of 20). validate* calls dry-run every lifecycle step, and lifecycle state errors are typed (already_started, stale_id). Issue #1429, open since 6 October, reports a second deprovision returning success, per the 8 October check, not re-read on 17 October. Not an MCP server, so no tool annotations apply (13 of 20). Network, filesystem and UI policy default to deny, and official SDKs exist for Node.js, .NET and Rust (15). 18+10+18+13+15 = 74.

Transparency & trust Microsoft Execution Containers +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.

Microsoft Execution Containers 84

MIT for the repository and for the published npm package, whose LICENSE.md we compared with the repository's (30). Local software with no service behind it. The telemetry docs list what the optional Windows events contain (version, backend, bounded outcomes, policy fingerprints) and what they omit (commands, file paths, credentials, free-form error text), and the consent prompt links Microsoft's privacy statement. No retention period for those events is stated (24 of 30). The release notes name V1 as the compatibility boundary for 1.x under semver 2.0, breaking changes need a new versioned surface, and the schema docs mark retired contracts. No notice period with dates was found (12 of 20). Telemetry is disclosed in the README, off by default, opt-in for each run, subject to user consent and an administrative block, and absent on Linux and macOS (20). 30+24+12+20 = 86.

Score by category

CategoryWeightDocker SandboxesMicrosoft Execution ContainersEdge
Reliability16%4581Microsoft Execution Containers +36
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9081Docker Sandboxes +9
Agent ergonomics13%8374Docker Sandboxes +9
Security & auth14%6969even
Payments & pricing10%090Microsoft Execution Containers +90
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7192Microsoft Execution Containers +21
Transparency & trust7%7784Microsoft Execution Containers +7
Negative events≤150-3
TotalB 62.1/100BB 77.1/100

Facts side by side

FactDocker SandboxesMicrosoft Execution Containers
KindHTTP APISDK + MCP
VendorDockerMicrosoft
Hosted endpointno (local only)no (local only)
TransportsHTTP
AuthOAuth or keyNone
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 subscriptionMIT
Read-only variant documentednoyes
llms.txtyesno
Last release2026-11-162026-10-17
Terms last updated2026-08-26no document linked
Privacy policy last updated2026-08-26couldn't be read
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 stars1.5k stars, 472k npm/wk
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.

Microsoft Execution Containers

MXC puts nine operating-system sandbox backends behind one typed request, with network access denied by default and a JSON Schema for the stable 1.0.0 contract. Enforcement varies by backend, isolation_session cannot restrict networking, and enforcement fixes made since 1.0.1, one of them a documented security fix, had not reached a release by 1 November 2026.

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

Microsoft Execution Containers

  1. Import from @microsoft/mxc-sdk/v1. The package root exports nothing.
  2. Call getPlatformSupport() first and stop if isSupported is false. getAvailableBackends() is advisory and launch-time validation still applies.
  3. Set network.egress.default to allow only when the task needs it. Omitted network policy resolves to deny in every direction.
  4. Never pass --audit to an executor for untrusted code. It turns off all sandbox security for the workload.
  5. Read ExecutionResult.warnings after each run. Security warnings arrive there and are not written to stdout or stderr.
  6. On Windows with 1.0.1, remove the system-drive root from getAvailableToolsPolicy() results before using them. The fix is on main only.

Questions

Which is better for AI agents, Docker Sandboxes or Microsoft Execution Containers?

Microsoft Execution Containers scores 77.1 (BB) on agent readiness against Docker Sandboxes's 62.1 (B), and leads in 4 of 7 scored categories. Docker Sandboxes leads on schema & documentation and agent ergonomics.

Can an agent call Docker Sandboxes and Microsoft Execution Containers without installing anything?

No hosted endpoint is listed for Docker Sandboxes. No hosted endpoint is listed for Microsoft Execution Containers.

Are Docker Sandboxes and Microsoft Execution Containers open source?

No open-source release is listed for Docker Sandboxes. Microsoft Execution Containers is open source (MIT).

Other comparisons with Docker Sandboxes or Microsoft Execution Containers

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.