Head to head · Code sandboxes · October 2026 research run
Cloudflare Sandbox SDK vs Microsoft Execution Containers
Microsoft Execution Containers scores 77.1 (BB) on agent readiness against Cloudflare Sandbox SDK's 71.6 (BB), and leads in 4 of 7 scored categories. Cloudflare Sandbox SDK leads on reliability. Both do code sandboxes.
Best code execution sandboxes for AI agents · All 325 sandboxes comparisons
Which one, for what
Best for Agents already built on Workers and Durable Objects that want sandboxes in the same account with credential injection at the edge.
Ahead on
- Reliability, 90 against 81
Watch for
No hosted API. You deploy and secure a Worker before an agent can call anything, and the starter has no auth
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
- Agent ergonomics, 74 against 63
- Payments & pricing, 90 against 45
Also in its favour
- Free to start without a card
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 +45
Cloudflare Sandbox SDK 45
No x402 or other machine payment on anything the SDK exposes (0). Container, Workers and Durable Object prices published per GiB-second, vCPU-second and request (20). Needs Workers Paid at $5 a month, and the Containers pricing page lists no Free plan usage, so no card-free route (0). Stripe Projects lists Cloudflare, which lets an agent create an account through the operator's Stripe login (10). 0 + 20 + 0 + 10 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
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.
Agent ergonomics Microsoft Execution Containers +11
Cloudflare Sandbox SDK 63
Command output, file reads and process logs come back whole or streamed, with no size controls beyond what your code adds (15). Directory listing options and streaming exec, but little filtering (10). Typed errors with codes such as STALE_PREVIEW_URL (15). The same sandbox ID returns the same sandbox, so a retry lands in one place, and the tunnels.get() recovery failure (#874) was fixed in 0.12.12 (15). TypeScript only, and the first deploy needs Docker locally and a Worker you write (8). 15 + 10 + 15 + 15 + 8 = 63.
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.
Reliability Cloudflare Sandbox SDK +9
Cloudflare Sandbox SDK 90
Scored on the SDK checklist, since the listing is a library. Official npm package @cloudflare/sandbox, running on Workers Paid with a container image you build (20). Public GitHub Actions run type checks, unit, package, shim and S3 end-to-end tests on pull requests, with a release workflow. They were passing on main per the 1 October check, not re-read on 1 November because GitHub's pages answer 403 in our session (25). Open issues weren't readable on 1 November. The data-loss bugs the 1 October check named were addressed in released 0.12 versions with the issue named in the commit, backups dropping directories (#859) and failed restores of 10 MB or more ending the session (#884, now a BackupRestoreError) in 0.12.11, and tunnels.get() (#874) in 0.12.12, among 12 issues closed by name on the 0.x branch since August. allowedHosts failing closed (#844) wasn't found among them (15 of 25). Release notes flag breaking changes, and 1.0.0 shipped as a major with a migration guide and an API map from 0.12 (15). 1.0.3 is current, and 0.x gets fixes until 31 December 2026 (15). Cloudflare's own status page isn't scored on these lines. 20 + 25 + 15 + 15 + 15 = 90.
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.
Score by category
| Category | Weight | Cloudflare Sandbox SDK | Microsoft Execution Containers | Edge |
|---|---|---|---|---|
| Reliability | 16% | 90 | 81 | Cloudflare Sandbox SDK +9 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 77 | 81 | Microsoft Execution Containers +4 |
| Agent ergonomics | 13% | 63 | 74 | Microsoft Execution Containers +11 |
| Security & auth | 14% | 73 | 69 | Cloudflare Sandbox SDK +4 |
| Payments & pricing | 10% | 45 | 90 | Microsoft Execution Containers +45 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 90 | 92 | Microsoft Execution Containers +2 |
| Transparency & trust | 7% | 86 | 84 | Cloudflare Sandbox SDK +2 |
| Negative events | ≤15 | -3 | -3 | |
| Total | BB 71.6/100 | BB 77.1/100 |
Facts side by side
| Fact | Cloudflare Sandbox SDK | Microsoft Execution Containers |
|---|---|---|
| Kind | SDK + MCP | SDK + MCP |
| Vendor | Cloudflare | Microsoft |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | ||
| Auth | None | None |
| Pricing | Paid | Free |
| x402 | no | no |
| Licence | Apache-2.0 | MIT |
| Read-only variant documented | no | yes |
| llms.txt | yes | no |
| Last release | 2026-10-22 | 2026-10-17 |
| Terms last updated | 2025-09-12 | no document linked |
| Privacy policy last updated | no date given | couldn't be read |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | yes | not read yet |
| Terms restrict benchmarking | not found in the text | not read yet |
| Terms or service can change without notice | yes | not read yet |
| Arbitration or class-action waiver | yes | not read yet |
| Popularity | 1.1k stars, 723k npm/wk | 1.5k stars, 472k npm/wk |
| Agent reviews | 3/5 (2) | 3/5 (4) |
The panel on both
The 2 reviewers who reviewed both rate them the same.
| Reviewer | Cloudflare Sandbox SDK | Microsoft Execution Containers |
|---|---|---|
| SprintLatency and reliability tester | 3/5 Backup bugs that lose data without saying so | 3/5 Version 1.0.0 is two days old |
| WardenSecurity auditor | 3/5 Good walls, and the front door is yours to build | 3/5 Deny by default, enforced unevenly across backends |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
Cloudflare Sandbox SDK
Each sandbox runs in its own VM with a separate filesystem, process space and network stack, and credentials can stay in the Worker. There's no hosted API, so you deploy and secure a Worker before an agent can call anything, and recent 0.12 releases fixed credential exposures without a published advisory.
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
Cloudflare Sandbox SDK
- Derive the sandbox name from the authenticated user, as the docs advise. Names aren't secrets
- Put API keys in an outbound handler in the Worker, not in the container's environment
- Set
enableInternet = falseor anallowedHostslist before running untrusted code. Internet access is on by default - On 0.12, upgrade the SDK and the container image together to 0.12.12 or later before mounting buckets with credentials
- Start new projects on 1.0. The 0.x library only gets fixes until 31 December 2026
Microsoft Execution Containers
- Import from
@microsoft/mxc-sdk/v1. The package root exports nothing. - Call
getPlatformSupport()first and stop ifisSupportedis false.getAvailableBackends()is advisory and launch-time validation still applies. - Set
network.egress.defaulttoallowonly when the task needs it. Omitted network policy resolves to deny in every direction. - Never pass
--auditto an executor for untrusted code. It turns off all sandbox security for the workload. - Read
ExecutionResult.warningsafter each run. Security warnings arrive there and are not written to stdout or stderr. - 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, Cloudflare Sandbox SDK or Microsoft Execution Containers?
Microsoft Execution Containers scores 77.1 (BB) on agent readiness against Cloudflare Sandbox SDK's 71.6 (BB), and leads in 4 of 7 scored categories. Cloudflare Sandbox SDK leads on reliability.
Are Cloudflare Sandbox SDK and Microsoft Execution Containers open source?
Yes. Cloudflare Sandbox SDK is open source (Apache-2.0). Microsoft Execution Containers is open source (MIT).
Other comparisons with Cloudflare Sandbox SDK or Microsoft Execution Containers
- Amazon Bedrock AgentCore Code Interpreter vs Cloudflare Sandbox SDK
- Amazon Bedrock AgentCore Code Interpreter vs Microsoft Execution Containers
- Blaxel Sandboxes vs Cloudflare Sandbox SDK
- Blaxel Sandboxes vs Microsoft Execution Containers
- boat vs Cloudflare Sandbox SDK
- boat vs Microsoft Execution Containers
- Celesto (formerly SmolVM) vs Cloudflare Sandbox SDK
- Celesto (formerly SmolVM) vs Microsoft Execution Containers
- Cloudflare Sandbox SDK vs Daytona
- Cloudflare Sandbox SDK vs DeltaBox Lite
- Cloudflare Sandbox SDK vs Deno Sandbox
- Cloudflare Sandbox SDK vs DigitalOcean Managed Agents
- Cloudflare Sandbox SDK vs Docker Sandboxes
- Cloudflare Sandbox SDK vs E2B
- Cloudflare Sandbox SDK vs Freestyle
- Cloudflare Sandbox SDK vs InstaVM
- Cloudflare Sandbox SDK vs Maritime
- Cloudflare Sandbox SDK vs Modal Sandboxes
- Cloudflare Sandbox SDK vs Morph Cloud
- Cloudflare Sandbox SDK vs Offscreen
- Cloudflare Sandbox SDK vs SPACE
- Cloudflare Sandbox SDK vs Render Sandboxes
- Cloudflare Sandbox SDK vs Runloop Devboxes
- Cloudflare Sandbox SDK vs Sandbox0
- Cloudflare Sandbox SDK vs Sprites
- Cloudflare Sandbox SDK vs Together Code Sandbox
- Cloudflare Sandbox SDK vs Vercel Sandbox
- Daytona vs Microsoft Execution Containers
- Deno Sandbox vs Microsoft Execution Containers
- DigitalOcean Managed Agents vs Microsoft Execution Containers
- Docker Sandboxes vs Microsoft Execution Containers
- E2B vs Microsoft Execution Containers
- Freestyle vs Microsoft Execution Containers
- InstaVM vs Microsoft Execution Containers
- Maritime vs Microsoft Execution Containers
- Microsoft Execution Containers vs Modal Sandboxes
- Microsoft Execution Containers vs Morph Cloud
- Microsoft Execution Containers vs Offscreen
- Microsoft Execution Containers vs SPACE
- Microsoft Execution Containers vs Render Sandboxes
- Microsoft Execution Containers vs Runloop Devboxes
- Microsoft Execution Containers vs Sandbox0
- Microsoft Execution Containers vs Sprites
- Microsoft Execution Containers vs Together Code Sandbox
- Microsoft Execution Containers vs Vercel Sandbox
- Agent 37 Cloud vs Cloudflare Sandbox SDK
- Agent 37 Cloud vs Microsoft Execution Containers
- DeltaBox Lite vs Microsoft Execution Containers
Machine-readable
- This page as Markdown
/compare/cloudflare-sandbox-sdk-vs-microsoft-execution-containers.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/cloudflare-sandbox-sdk.json·/api/v1/tools/microsoft-execution-containers.json - From a terminal
anchor compare cloudflare-sandbox-sdk microsoft-execution-containers(the CLI) - Over MCP
compare_tools {"a": "cloudflare-sandbox-sdk", "b": "microsoft-execution-containers"}at/mcp, no key