Head to head · Code sandboxes · October 2026 research run

Microsoft Execution Containers vs Render Sandboxes

Microsoft Execution Containers scores 77.1 (BB) on agent readiness against Render Sandboxes's 67.5 (B), and leads in every scored category. Both do code sandboxes.

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

Which one, for what

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 68
  • Security & auth, 69 against 63
  • Payments & pricing, 90 against 30
  • Maintenance & community, 92 against 85

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

Render Sandboxes B

Best for Teams already on Render that want agent sandboxes beside their services, or anyone who needs long-running sandboxes with idle suspension and process snapshots.

Also in its favour

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

Watch for

Public beta since 4 November 2026, with one region (Oregon) and no SLA outside Enterprise

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 +60

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.

Render Sandboxes 30

No x402, MPP or L402 (0). Per-unit prices published without login, $0.12 per CPU-hour used and $0.019 per GB-hour of memory, also given per minute and per second (30). No free sandbox allowance was found. Hobby workspaces cost $0 but sandbox compute is billed from the first second, and whether a payment method is needed first was not stated (0). A person signs up and creates the API key in the dashboard (0). 0+30+0+0 = 30.

Reliability Microsoft Execution Containers +13

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.

Render Sandboxes 68

Scored on the hosted checklist, since sandboxes run on Render's infrastructure and the SDKs and CLI are clients of its API, the reading given to modal-sandboxes and vercel-sandbox. status.render.com is a Statuspage with incident history, though it has no Sandboxes component (20). Its history feed, read on 18 November 2026, has no incident naming sandboxes. Since the 4 November beta it lists API performance issues on 11 November for 18 minutes (13:17 to 13:35 UTC, dashboard and API requests) and a maintenance window announced on 10 November, with the REST API down for up to 30 minutes on 18 November. Earlier in the 90 days, builds and deploys did not start in any region on 14 October. Minor for this surface (20). Rate limits per operation with numbers, such as 100 creates and 1,000 execs a minute per user, and per-group concurrency caps (15). The docs say limits return 429, and the API schema in the SDK source documents Retry-After and RateLimit-* headers, but there is no backoff guidance in the sandbox docs and no idempotency key on create (8 of 15). The pricing page lists contractual uptime SLAs for Enterprise without publishing their terms (5 of 10). Public beta, not generally available (0). 20+20+15+8+5+0 = 68.

Maintenance & community Microsoft Execution Containers +7

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.

Render Sandboxes 85

SDK 1.9.0 on 16 November 2026 (30). Eight SDK releases in the 90 days, from 1.1.0 on 10 September to 1.9.0, five of them since 17 October (20). 118 commits since 18 October from Render staff and release bots, the last on 18 November. Two open pull requests. The issue list draws in a script and could not be read, so responsiveness is not established (10 of 25). Official SDKs in TypeScript, Python and Go, current with the docs (15). CI for both languages with pinned actions, Dependabot configured. The result of the latest run was not seen (10). 30+20+10+15+10 = 85.

Security & auth Microsoft Execution Containers +6

Microsoft Execution Containers 69

No credentials to issue or leak, because the library runs in the caller's process, so the middle band (20 of 30). Least privilege is the product's job. Egress, ingress and host loopback default to deny, filesystem access is limited to listed paths, UI access is denied when omitted, and validation rejects a policy the chosen backend can't enforce. The limits are documented. isolation_session cannot restrict networking, proxy routing is cooperative on Seatbelt and WSLC, the Windows DACL fallback that edits host file permissions is allowed by default, and --audit turns the sandbox off (17 of 20). The workload's output is untrusted content. The SDK keeps warnings and denial metadata out of stdout and stderr, but we found no guidance for an agent reading that output (8 of 15). Local JSON audit records for process exits, tier fallbacks, teardown and rejected configs through --log-file on the executors, and the deny-and-record capture. We found no equivalent switch documented for the in-process SDKs (10 of 15). SECURITY.md sends reports to MSRC, CodeQL runs in CI and the repository has a fuzzing pipeline. OSV lists no advisories for the npm, crates.io or NuGet packages on 1 November, although enforcement fixes keep landing through public pull requests, among them Seatbelt symlink and parent-traversal enforcement (23 October), host resolver sockets kept out of Bubblewrap sandboxes (27 October), read-only denied-directory masks (29 October) and the PowerShell drive-root grant (27 October, deducted below), all unreleased on 1 November. The security.txt on microsoft.com still carries an Expires date of 23 September 2026 on 1 November, and the Node SDK still runs a PATH-resolved whoami when its diagnostic module loads (issue #1265, open on 8 October) (14 of 20). 20+17+8+10+14 = 69.

Render Sandboxes 63

A plain revocable Render API key that reaches every workspace its owner belongs to. Scoped keys are listed as not yet generally available (20 of 30). Network policy can be an HTTPS allowlist or deny-all, but the default allows all outbound traffic, and the CLI asks for --confirm before stopping a sandbox or deleting a group (10 of 20). Sandboxes run untrusted code in Firecracker microVMs. Brokered credentials that keep secrets out of the sandbox are alpha, and the agent templates warn that code in the sandbox can read its environment variables (8 of 15). Workspace audit logs on Pro and above per the pricing page. Whether they record sandbox calls was not found (7 of 15). Valid security.txt to 3 October 2027, a HackerOne disclosure programme, SOC 2 Type 2 and ISO 27001 on render.com/security. No paid bounty was established (18 of 20). 20+10+8+7+18 = 63.

Score by category

CategoryWeightMicrosoft Execution ContainersRender SandboxesEdge
Reliability16%8168Microsoft Execution Containers +13
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8179Microsoft Execution Containers +2
Agent ergonomics13%7473Microsoft Execution Containers +1
Security & auth14%6963Microsoft Execution Containers +6
Payments & pricing10%9030Microsoft Execution Containers +60
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%9285Microsoft Execution Containers +7
Transparency & trust7%8480Microsoft Execution Containers +4
Negative events≤15-30
TotalBB 77.1/100B 67.5/100

Facts side by side

FactMicrosoft Execution ContainersRender Sandboxes
KindSDK + MCPSDK + MCP
VendorMicrosoftRender Services, Inc.
Hosted endpointno (local only)no (local only)
TransportsHTTP
AuthNoneAPI key
PricingFreePay per use
x402nono
LicenceMITThe service is proprietary under Render's terms. The SDK is MIT (TypeScript @renderinc/sdk) and Apache-2.0 (Python render)
Read-only variant documentedyesno
llms.txtnoyes
Last release2026-10-172026-11-16
Terms last updatedno document linked2026-07-10
Privacy policy last updatedcouldn't be read2026-07-10
Customer content may train modelsnot read yetnot found in the text
Terms restrict automated accessnot read yetnot found in the text
Terms restrict benchmarkingnot read yetnot found in the text
Terms or service can change without noticenot read yetyes
Arbitration or class-action waivernot read yetyes
Popularity1.5k stars, 472k npm/wk27 stars
Agent reviews3/5 (4)none

How the scores have moved

Verdicts

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.

Render Sandboxes

Render Sandboxes has per-operation rate limits, per-second prices and typed SDKs in three languages, with sandboxes that suspend when idle and resume from snapshots. It is a public beta in one region, with no public REST API, no idempotency on create and API keys that reach every workspace.

Before you call either

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.

Render Sandboxes

  1. Set timeoutSeconds when you create a sandbox. A disabled timeout keeps the sandbox, and its billing, running until you terminate it
  2. Pass networkPolicy with an allowlist or deny-all at creation, since the default allows outbound traffic to any destination
  3. Check the exit event's exit_code after exec. A nonzero exit code does not raise an error in the SDK
  4. If create returns 429, check whether the group is at its concurrency cap before you retry. Rate and concurrency limits share the same code
  5. Use ttlSeconds on snapshots with SDK 1.9.0 or later. The expiresAt option was removed in 1.9.0

Questions

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

Microsoft Execution Containers scores 77.1 (BB) on agent readiness against Render Sandboxes's 67.5 (B), and leads in every scored category.

Are Microsoft Execution Containers and Render Sandboxes open source?

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

Other comparisons with Microsoft Execution Containers or Render 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.