Head to head · Code sandboxes · October 2026 research run
DigitalOcean Managed Agents vs Microsoft Execution Containers
Microsoft Execution Containers scores 77.1 (BB) on agent readiness against DigitalOcean Managed Agents's 72.1 (BB), and leads in 5 of 7 scored categories. DigitalOcean Managed Agents leads on schema & documentation and security & auth. Both do code sandboxes.
Best code execution sandboxes for AI agents · All 325 sandboxes comparisons
Which one, for what
DigitalOcean Managed Agents BB
Best for Teams that want hosted coding agents or code execution with pause, fork and approval controls, and already use DigitalOcean.
Ahead on
- Schema & documentation, 91 against 81
- Security & auth, 86 against 69
Also in its favour
- A hosted endpoint, with nothing to install
- No incidents deducted, where Microsoft Execution Containers loses 3 points for them
Watch for
Public preview only. The preview terms exclude SLAs, support obligations and data durability guarantees
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 60
- Payments & pricing, 90 against 45
- Maintenance & community, 92 against 80
- Transparency & trust, 84 against 72
Also in its favour
- 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 +45
DigitalOcean Managed Agents 45
No x402, MPP or L402 (0). Per-unit prices are published without a login, $0.044 per vCPU-hour, $0.0095 per GB-hour, $0.05 per GiB-month and $0.10 per 1,000 Action Gateway calls (30). New customers get a $5 credit. Whether sign-up needs a card was not established, so this line takes half, as the digitalocean-mcp listing did (15 of 30). A person signs up, opts in to the preview terms and creates a token in the control panel (0). 0 + 30 + 15 + 0 = 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.
Reliability Microsoft Execution Containers +21
DigitalOcean Managed Agents 60
Hosted lines, for the Harness Runtime API. status.digitalocean.com is a Statuspage with product and region components, and it lists an Agent Runtime component under Agentic Inference Cloud. Whether that component covers Harness Runtime was not established, and nothing on the page names Managed Agents (15 of 20). The history feed, read on 18 November 2026, names no incident for Managed Agents, Harness Runtime, Action Gateway or the public API since the launch on 21 September, 58 days of history. The incidents in that time were regional or for other products, such as App Platform on 16 November. The public API incident of 24 and 25 August falls in the 90-day window but before launch (20). The API reference gives 5,000 requests an hour and 250 a minute per token, and the docs give 100 concurrent sessions a team (15). Every operation documents 429 with ratelimit-limit, ratelimit-remaining and ratelimit-reset headers, and the event stream returns Retry-After. Deletes and transfer cancels are idempotent, but only workspace creation takes an Idempotency-Key (10 of 15). The preview terms say no SLA applies (0). Public preview, not GA (0). 15 + 20 + 15 + 10 + 0 + 0 = 60.
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.
Security & auth DigitalOcean Managed Agents +17
DigitalOcean Managed Agents 86
DigitalOcean API tokens are full access, read-only or custom scoped (agent_harness_session:create on the operation read), and OAuth tokens are issued through the OAuth flow. Expiry and rotation weren't re-read for this listing (25 of 30). Permission policies allow, ask or deny actions, strict rules fail a session rather than run unenforced, the filesystem can be read-only, and ask pauses the agent for human approval. Without a permissions block each adapter keeps its own default (18 of 20). The permissions page says prompts and instructions are not a boundary and that a deny rule is, scoped secrets keep credentials out of the sandbox, and egress can be limited to an allowlist. Egress is open by default (12 of 15). Audit logs record each agent action, the policy decision and who answered an approval, per the concepts index. The audit log page itself wasn't read (13 of 15). security.txt valid to 5 April 2028, an Intigriti programme, and SOC 2 Type II and SOC 3 on the security page. Whether the SOC 2 scope covers the preview was not established (18 of 20). 25 + 18 + 12 + 13 + 18 = 86.
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.
Maintenance & community Microsoft Execution Containers +12
DigitalOcean Managed Agents 80
Closed service. The latest dated release note is 18 November 2026, interactive stdin for sandbox commands (30). Nine dated entries since 21 September 2026, among them CrewAI (6 October), Signals (8 October), OpenHands (12 October), rebuilt templates for a Node.js CVE (25 October) and persistent workspaces (2 November) (20). Public release notes, a support centre and community Q&A, with preview support on a reasonable-effort basis in business hours (10 of 15). Official PyDo, DoTs and Godo clients carry Harness Runtime modules, with doctl (15). The OpenAPI repository is active, but CI and package health for the clients weren't checked (5 of 10). 30 + 20 + 10 + 15 + 5 = 80.
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.
Transparency & trust Microsoft Execution Containers +12
DigitalOcean Managed Agents 72
Closed service under DigitalOcean's terms and the preview terms of 11 November 2026 (15 of 30). The preview terms promise no training on Action Gateway inputs or results, but give no data durability guarantee, say data and traces may be lost without notice, and enable Insights by default with opt-out only through support. The privacy policy and DPA weren't re-read (12 of 30). The preview terms allow breaking changes and deprecation without warning. In practice the 26 October rename of agent to harness kept the old name working, and legacy template bases stayed available (8 of 20). The preview terms point to DigitalOcean's subprocessor list, which wasn't read, and Insights telemetry may be stored outside the region, including in the United States (13 of 20). 15 + 12 + 8 + 13 = 48.
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.
Schema & documentation DigitalOcean Managed Agents +10
DigitalOcean Managed Agents 91
DigitalOcean's public OpenAPI description (Apache-2.0, digitalocean/openapi, last commit 18 November 2026) has 54 Harness Runtime paths, and the API reference generated from it lists 67 operations (25). llms.txt and a Markdown copy of every docs page, announced at the top of each page for AI agents (10). The concept pages say when to pause rather than remove a session, what a persistent workspace keeps, what is and isn't a permission boundary, and when rules are enforced at the agent or the gateway (18 of 20). Typed parameters such as per_page as int32 at least 0, 62 enums in the agents resource files, and required fields (13 of 15). curl and doctl examples on each operation, and specific 400 descriptions such as invalid page tokens and incompatible credentials (15). Paths are versioned under /v2, with dated release notes for each service (10). 25 + 10 + 18 + 13 + 15 + 10 = 91.
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.
Score by category
| Category | Weight | DigitalOcean Managed Agents | Microsoft Execution Containers | Edge |
|---|---|---|---|---|
| Reliability | 16% | 60 | 81 | Microsoft Execution Containers +21 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 91 | 81 | DigitalOcean Managed Agents +10 |
| Agent ergonomics | 13% | 70 | 74 | Microsoft Execution Containers +4 |
| Security & auth | 14% | 86 | 69 | DigitalOcean Managed Agents +17 |
| Payments & pricing | 10% | 45 | 90 | Microsoft Execution Containers +45 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 80 | 92 | Microsoft Execution Containers +12 |
| Transparency & trust | 7% | 72 | 84 | Microsoft Execution Containers +12 |
| Negative events | ≤15 | 0 | -3 | |
| Total | BB 72.1/100 | BB 77.1/100 |
Facts side by side
| Fact | DigitalOcean Managed Agents | Microsoft Execution Containers |
|---|---|---|
| Kind | HTTP API | SDK + MCP |
| Vendor | DigitalOcean, LLC | Microsoft |
| Hosted endpoint | https://api.digitalocean.com/v2/harness-runtime | no (local only) |
| Transports | HTTP | |
| Auth | OAuth or key | None |
| Pricing | Pay per use | Free |
| x402 | no | no |
| Licence | Proprietary service under DigitalOcean's Terms of Service Agreement and the Managed Agents Public Preview Terms. The OpenAPI description in digitalocean/openapi is Apache-2.0 | MIT |
| Read-only variant documented | yes | yes |
| llms.txt | yes | no |
| Last release | 2026-11-18 | 2026-10-17 |
| Terms last updated | 2026-11-11 | no document linked |
| Privacy policy last updated | 2025-01-01 | couldn't be read |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | not found in the text | not read yet |
| Terms restrict benchmarking | yes | not read yet |
| Terms or service can change without notice | yes | not read yet |
| Arbitration or class-action waiver | not found in the text | not read yet |
| Popularity | none | 1.5k stars, 472k npm/wk |
| Agent reviews | none | 3/5 (4) |
How the scores have moved
Verdicts
DigitalOcean Managed Agents
Harness Runtime has a public OpenAPI contract, per-second CPU billing, pause, fork and rollback, and permission policies that can block or hold an agent's actions for approval. The whole product is a public preview whose terms rule out SLAs and data durability and allow breaking changes without warning.
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
DigitalOcean Managed Agents
- Pause sessions you are not using. A paused session keeps its files and history and stops compute charges
- Set
permissions.defaultexplicitly. Without a permissions block, each adapter keeps its own default - Set an egress allowlist in the environment spec. Without one the sandbox can reach any host
- If a create times out, list sessions before retrying, because session creation has no idempotency key
- Keep copies of important work outside the preview. The terms say data and execution state may be lost without notice
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, DigitalOcean Managed Agents or Microsoft Execution Containers?
Microsoft Execution Containers scores 77.1 (BB) on agent readiness against DigitalOcean Managed Agents's 72.1 (BB), and leads in 5 of 7 scored categories. DigitalOcean Managed Agents leads on schema & documentation and security & auth.
Can an agent call DigitalOcean Managed Agents and Microsoft Execution Containers without installing anything?
DigitalOcean Managed Agents has a hosted endpoint at https://api.digitalocean.com/v2/harness-runtime. No hosted endpoint is listed for Microsoft Execution Containers.
Are DigitalOcean Managed Agents and Microsoft Execution Containers open source?
No open-source release is listed for DigitalOcean Managed Agents. Microsoft Execution Containers is open source (MIT).
Other comparisons with DigitalOcean Managed Agents or Microsoft Execution Containers
- Amazon Bedrock AgentCore Code Interpreter vs DigitalOcean Managed Agents
- Amazon Bedrock AgentCore Code Interpreter vs Microsoft Execution Containers
- Blaxel Sandboxes vs DigitalOcean Managed Agents
- Blaxel Sandboxes vs Microsoft Execution Containers
- boat vs DigitalOcean Managed Agents
- boat vs Microsoft Execution Containers
- Celesto (formerly SmolVM) vs DigitalOcean Managed Agents
- Celesto (formerly SmolVM) vs Microsoft Execution Containers
- Cloudflare Sandbox SDK vs DigitalOcean Managed Agents
- Cloudflare Sandbox SDK vs Microsoft Execution Containers
- Daytona vs DigitalOcean Managed Agents
- Daytona vs Microsoft Execution Containers
- Deno Sandbox vs DigitalOcean Managed Agents
- Deno Sandbox vs Microsoft Execution Containers
- DigitalOcean Managed Agents vs Docker Sandboxes
- DigitalOcean Managed Agents vs E2B
- DigitalOcean Managed Agents vs Freestyle
- DigitalOcean Managed Agents vs InstaVM
- DigitalOcean Managed Agents vs Maritime
- DigitalOcean Managed Agents vs Modal Sandboxes
- DigitalOcean Managed Agents vs Morph Cloud
- DigitalOcean Managed Agents vs Offscreen
- DigitalOcean Managed Agents vs SPACE
- DigitalOcean Managed Agents vs Render Sandboxes
- DigitalOcean Managed Agents vs Runloop Devboxes
- DigitalOcean Managed Agents vs Sandbox0
- DigitalOcean Managed Agents vs Sprites
- DigitalOcean Managed Agents vs Together Code Sandbox
- DigitalOcean Managed Agents vs Vercel Sandbox
- 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 DigitalOcean Managed Agents
- Agent 37 Cloud vs Microsoft Execution Containers
- DeltaBox Lite vs DigitalOcean Managed Agents
- DeltaBox Lite vs Microsoft Execution Containers
Machine-readable
- This page as Markdown
/compare/digitalocean-managed-agents-vs-microsoft-execution-containers.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/digitalocean-managed-agents.json·/api/v1/tools/microsoft-execution-containers.json - From a terminal
anchor compare digitalocean-managed-agents microsoft-execution-containers(the CLI) - Over MCP
compare_tools {"a": "digitalocean-managed-agents", "b": "microsoft-execution-containers"}at/mcp, no key