{
  "data": {
    "a": {
      "slug": "digitalocean-managed-agents",
      "name": "DigitalOcean Managed Agents",
      "vendor": "DigitalOcean, LLC",
      "vendorUrl": "https://www.digitalocean.com/products/managed-agents",
      "company": "digitalocean.com",
      "kind": "http-api",
      "category": "code-sandboxes",
      "summary": "DigitalOcean Managed Agents runs agent harnesses and arbitrary code in Firecracker microVM sandboxes with pause, resume, checkpoint and fork, through Harness Runtime, and brokers tool access through Action Gateway's managed MCP endpoint. Both are in public preview.",
      "url": "https://www.anchorterminal.com/tools/digitalocean-managed-agents",
      "markdownUrl": "https://www.anchorterminal.com/tools/digitalocean-managed-agents.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/digitalocean-managed-agents.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/digitalocean-managed-agents.json",
      "dns": "digitalocean-managed-agents.grade.anchorterminal.com",
      "repo": "https://github.com/digitalocean/openapi",
      "license": "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",
      "transports": [
        "http"
      ],
      "remoteUrl": "https://api.digitalocean.com/v2/harness-runtime",
      "packages": [
        {
          "registry": "pypi",
          "name": "pydo"
        },
        {
          "registry": "go",
          "name": "github.com/digitalocean/godo"
        }
      ],
      "auth": "mixed",
      "authNotes": "DigitalOcean API tokens sent as `Authorization: Bearer`, either personal access tokens (`dop_v1_`) made in the control panel or OAuth tokens (`doo_v1_`) from an app's OAuth flow. Tokens can be full access, read-only or custom scopes such as `agent_harness_session:create`. Using the preview needs a person to opt in to the Managed Agents Public Preview Terms. Scoped secrets bind a credential to one HTTPS destination so it never enters the sandbox.",
      "pricing": "usage",
      "pricingNotes": "Harness Runtime is billed per second of actual CPU use, $0.044 per vCPU-hour, with memory at $0.0095 per GB-hour and storage at $0.05 per GiB-month. The default 2 vCPU, 4 GB sandbox costs $0.126 an hour at full use, and paused sessions incur no compute charge. Action Gateway costs $0.10 per 1,000 tool invocations. New customers get a $5 credit. Agent Droplets plans at $50 and $200 a month discount usage by 15 and 20 per cent. Whether sign-up needs a card was not established.",
      "priceSummary": "$0.044 / vCPU-hr",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the Managed Agents docs, the Harness Runtime pricing page, the public preview terms or the OpenAPI description (checked 2026-11-18). Usage draws on the account's prepaid wallet, and new requests are blocked when it reaches zero.",
        "endpoints": []
      },
      "toolCount": null,
      "popularity": {
        "githubStars": null,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-11-18"
      },
      "docsUrl": "https://docs.digitalocean.com/products/managed-agents/",
      "llmsTxt": "https://docs.digitalocean.com/llms.txt",
      "openapi": "https://github.com/digitalocean/openapi/blob/main/specification/DigitalOcean-public.v2.yaml",
      "capabilities": [
        "sandbox.code",
        "sandbox.fs",
        "sandbox.persist",
        "sandbox.browser",
        "agent.harness",
        "agent.tools"
      ],
      "tags": [
        "official",
        "hosted",
        "usage",
        "beta",
        "microvm",
        "openapi",
        "llms-txt",
        "status-page",
        "python",
        "go",
        "typescript",
        "cli",
        "mcp",
        "soc2",
        "bug-bounty"
      ],
      "lastRelease": "2026-11-18",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 72.1,
        "grade": "BB",
        "agentReady": true,
        "rank": 236,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 5,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 70,
          "maintenance": 80,
          "payments": 45,
          "reliability": 60,
          "schema": 91,
          "security": 86,
          "transparency": 72
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-18"
        },
        "negative": 0,
        "verdict": "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.",
        "bestFor": "Teams that want hosted coding agents or code execution with pause, fork and approval controls, and already use DigitalOcean.",
        "strengths": [
          "67 Harness Runtime operations in the API reference, generated from DigitalOcean's public OpenAPI description, with llms.txt and a Markdown copy of every docs page",
          "Permission policies with allow, ask and deny, a read-only filesystem option, egress allowlists and audit logs of each agent action",
          "Scoped secrets bind a credential to one HTTPS destination so it never enters the sandbox",
          "Per-second CPU billing at $0.044 per vCPU-hour, with no compute charge while a session is paused",
          "Nine dated release notes between 21 September and 18 November 2026"
        ],
        "weaknesses": [
          "Public preview only. The preview terms exclude SLAs, support obligations and data durability guarantees",
          "The preview terms allow breaking changes to endpoints, SDKs and the spec schema without prior warning",
          "Sandbox egress is open to any host unless the environment spec sets an allowlist",
          "No idempotency key on session creation. Only workspace creation takes `Idempotency-Key`",
          "Insights is switched on by default for preview accounts and can be turned off only through support"
        ],
        "agentNotes": [
          "Pause sessions you are not using. A paused session keeps its files and history and stops compute charges",
          "Set `permissions.default` explicitly. 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"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "BB",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 72.1
          }
        ],
        "editorialScores": {
          "ergonomics": 70,
          "maintenance": 80,
          "payments": 45,
          "reliability": 60,
          "schema": 91,
          "security": 86,
          "transparency": 48
        },
        "provenanceScore": 95,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-18",
            "maintenance": "2026-11-18",
            "payments": "2026-11-18",
            "reliability": "2026-11-18",
            "schema": "2026-11-18",
            "security": "2026-11-18",
            "transparency": "2026-11-18"
          },
          "last": "2026-11-18",
          "oldest": "2026-11-18",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "install": "pip install pydo  # or doctl harness-runtime --help",
        "http": "curl -H \"Authorization: Bearer $DIGITALOCEAN_TOKEN\" https://api.digitalocean.com/v2/harness-runtime/sessions"
      },
      "letme": {
        "capability": "https://letme.dev/sandbox.code",
        "tool": "https://letme.dev/digitalocean-managed-agents"
      },
      "sameCompany": [
        "digitalocean-mcp",
        "digitalocean-spaces"
      ],
      "area": "agent-runtime",
      "unitPrices": [
        {
          "item": "Harness Runtime CPU",
          "unit": "vcpu-hour",
          "usd": 0.044,
          "note": "billed per second on actual CPU used"
        },
        {
          "item": "Harness Runtime memory",
          "unit": "gb",
          "usd": 0.0095,
          "note": "per GB-hour allocated"
        },
        {
          "item": "Session, snapshot and checkpoint storage",
          "unit": "gb-month",
          "usd": 0.05
        },
        {
          "item": "Action Gateway tool invocations",
          "unit": "1k-calls",
          "usd": 0.1
        },
        {
          "item": "Agent Droplets Pro plan",
          "unit": "month",
          "usd": 50,
          "note": "15 per cent off eligible usage"
        }
      ],
      "provenance": {
        "legalEntity": "DigitalOcean, LLC",
        "domain": "digitalocean.com",
        "domainRegistered": "2000-04-12",
        "endpointOnVendorDomain": true,
        "terms": "https://www.digitalocean.com/legal/mars-preview-terms",
        "privacy": "https://www.digitalocean.com/legal/privacy-policy",
        "statusPage": "https://status.digitalocean.com",
        "changelog": "https://docs.digitalocean.com/release-notes/agent-harness-runtime/",
        "securityTxt": "valid",
        "checked": "2026-11-18",
        "notes": [
          "The Managed Agents Public Preview Terms, last updated 11 November 2026, supplement DigitalOcean's Terms of Service Agreement. The legal entity, the domain's registration date and the privacy policy address come from the DigitalOcean company facts on the digitalocean-mcp listing.",
          "docs.digitalocean.com, www.digitalocean.com and status.digitalocean.com robots.txt files allowed every page read on 18 November 2026.",
          "www.digitalocean.com/.well-known/security.txt, read on 18 November 2026, names security@digitalocean.com and the Intigriti programme and expires on 5 April 2028.",
          "status.digitalocean.com lists an Agent Runtime component under Agentic Inference Cloud. Whether it covers Harness Runtime was not established."
        ],
        "score": 95
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/digitalocean-managed-agents.json",
      "live": {
        "slug": "digitalocean-managed-agents",
        "probe": {
          "target": "https://api.digitalocean.com/v2/harness-runtime",
          "method": "get",
          "lastAt": "2026-11-18T22:43:20.8364428Z",
          "lastOk": true,
          "lastStatus": 404,
          "lastMs": 348,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 304,
          "p95ms24h": 1231,
          "samples24h": 11,
          "samples30d": 11,
          "days": [
            {
              "date": "2026-11-18",
              "probes": 11,
              "ok": 11
            }
          ],
          "since": "2026-11-18T21:37:54.203264315Z"
        },
        "vendorStatus": {
          "page": "https://status.digitalocean.com",
          "indicator": "none",
          "summary": "All Systems Operational",
          "checkedAt": "2026-11-18T22:37:47.549173017Z"
        },
        "updatedAt": "2026-11-18T22:43:20.8364428Z"
      },
      "streak": {
        "days": 0,
        "from": "2026-11-18",
        "sinceWatching": true,
        "best": 0
      }
    },
    "answer": "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 \u0026 documentation and security \u0026 auth.",
    "b": {
      "slug": "microsoft-execution-containers",
      "name": "Microsoft Execution Containers",
      "vendor": "Microsoft",
      "vendorUrl": "https://github.com/microsoft/mxc",
      "company": "microsoft.com",
      "kind": "sdk",
      "category": "code-sandboxes",
      "summary": "Microsoft Execution Containers (MXC) is an open-source SDK for running untrusted code in a local sandbox on Windows, Linux and macOS. An application embeds it through Node.js, .NET or Rust and sets filesystem, network and UI policy for each run.",
      "url": "https://www.anchorterminal.com/tools/microsoft-execution-containers",
      "markdownUrl": "https://www.anchorterminal.com/tools/microsoft-execution-containers.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/microsoft-execution-containers.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/microsoft-execution-containers.json",
      "dns": "microsoft-execution-containers.grade.anchorterminal.com",
      "repo": "https://github.com/microsoft/mxc",
      "license": "MIT",
      "transports": [],
      "packages": [
        {
          "registry": "npm",
          "name": "@microsoft/mxc-sdk"
        },
        {
          "registry": "nuget",
          "name": "Microsoft.Mxc.Sdk"
        }
      ],
      "auth": "none",
      "authNotes": "No account, key or sign-in. MXC is a library the host application loads in its own process, so it holds no credential of its own. The workload runs with whatever the request grants. Network egress, ingress and host loopback resolve to `deny` when omitted, and filesystem access is limited to the `readonlyPaths` and `readwritePaths` the caller lists. On Windows the `isolation_session` backend creates a separate agent user account for each container and returns its name and SID.",
      "pricing": "free",
      "pricingNotes": "Free. The SDKs and native runtime are MIT and install from npm, NuGet and crates.io with no account or card. There is no hosted service and nothing to buy. Compute is the owner's own machine. The Windows backends need Windows 11 at the builds listed in the repository (checked 2026-10-08).",
      "priceSummary": "Free · OSS",
      "where": "local",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the README, the docs or the SDK source. Local open-source software with no paid endpoint (checked 2026-10-08).",
        "endpoints": []
      },
      "toolCount": null,
      "popularity": {
        "githubStars": 1506,
        "npmWeekly": 471674,
        "pypiWeekly": null,
        "asOf": "2026-10-08"
      },
      "docsUrl": "https://github.com/microsoft/mxc/blob/main/docs/api-reference/README.md",
      "capabilities": [
        "sandbox.code",
        "sandbox.fs",
        "sandbox.persist"
      ],
      "tags": [
        "sdk",
        "open-source",
        "local",
        "free",
        "no-auth",
        "no-card",
        "typescript",
        "dotnet",
        "rust",
        "windows",
        "linux",
        "macos",
        "json-schema",
        "new-1.0"
      ],
      "lastRelease": "2026-10-17",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 77.1,
        "grade": "BB",
        "agentReady": true,
        "rank": 77,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 1,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 74,
          "maintenance": 92,
          "payments": 90,
          "reliability": 81,
          "schema": 81,
          "security": 69,
          "transparency": 84
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-01"
        },
        "negative": -3,
        "negativeNotes": [
          "-3: on 27 October 2026 commit 0c5a1f5 (#1590) stopped the Windows tool-discovery helpers (Node `policy.filesystem.getAvailableToolsPolicy`, Rust `available_tools_policy`) from granting read access to the whole system drive when `pwsh.exe` is on PATH, which the versioning docs call a \"security-servicing exception\" because the grant \"can expose host files beyond the discovered tool directories\". On 1 November the fix was on main only. The newest release, 1.0.1 of 17 October, still adds `C:\\` to `readonlyPaths`. A documented security fix in no release yet takes the floor, as composio-rube and clawboo did on 1 November. It is read-only, needs the caller to use the helper on Windows with PowerShell installed, and the vendor documented it, so 3 (https://github.com/microsoft/mxc/commit/0c5a1f5e67794f96ac8e1783dc83e57057102b45; https://github.com/microsoft/mxc/blob/main/docs/development/architecture/versioning.md)."
        ],
        "verdict": "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.",
        "bestFor": "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.",
        "strengths": [
          "MIT licence, with SDKs for Node.js, .NET and Rust all at 1.0.1 and the native runtime bundled in the npm and NuGet packages",
          "Egress, ingress and host loopback default to `deny`, and filesystem access is limited to listed read-only and read-write paths",
          "A draft-07 JSON Schema for the stable 1.0.0 request, with descriptions on 135 of 150 properties",
          "Errors carry one of 12 typed codes plus an optional remediation, and `validate*` calls dry-run a request without creating a container",
          "Telemetry is opt-in, Windows-only and gated on user consent and an administrative policy that can only block it"
        ],
        "weaknesses": [
          "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",
          "Enforcement differs by backend. `isolation_session` cannot restrict networking, and proxy routing is cooperative on Seatbelt and WSLC",
          "The Node and .NET changelogs still list the V1 changes under Unreleased, with no 1.0.0 or 1.0.1 heading",
          "On Windows the Node SDK runs a PATH-resolved `whoami` when it loads, reported on 24 September 2026 and still in the 1.0.1 source",
          "The npm package is 37.7 MB compressed, needs Node.js 24 or later, and carries no `repository` field or provenance attestation"
        ],
        "agentNotes": [
          "Import from `@microsoft/mxc-sdk/v1`. The package root exports nothing.",
          "Call `getPlatformSupport()` first and stop if `isSupported` is false. `getAvailableBackends()` is advisory and launch-time validation still applies.",
          "Set `network.egress.default` to `allow` only when the task needs it. Omitted network policy resolves to deny in every direction.",
          "Never pass `--audit` to an executor for untrusted code. It turns off all sandbox security for the workload.",
          "Read `ExecutionResult.warnings` after 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."
        ],
        "metrics": {
          "kind": "local",
          "measured": false
        },
        "reviewCount": 4,
        "avgRating": 3,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "BB",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 77.1
          }
        ],
        "editorialScores": {
          "ergonomics": 74,
          "maintenance": 92,
          "payments": 90,
          "reliability": 81,
          "schema": 81,
          "security": 69,
          "transparency": 86
        },
        "provenanceScore": 82,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-01",
            "maintenance": "2026-11-01",
            "payments": "2026-11-01",
            "reliability": "2026-11-01",
            "schema": "2026-11-01",
            "security": "2026-11-01",
            "transparency": "2026-11-01"
          },
          "last": "2026-11-01",
          "lastMoved": "2026-11-13",
          "oldest": "2026-11-01",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "install": "npm install @microsoft/mxc-sdk"
      },
      "letme": {
        "capability": "https://letme.dev/sandbox.code",
        "tool": "https://letme.dev/microsoft-execution-containers"
      },
      "sameCompany": [
        "azure-openai",
        "azure-foundry-fine-tuning",
        "azure-ai-content-safety",
        "azure-speech-to-text",
        "azure-text-to-speech",
        "microsoft-agent-framework",
        "microsoft-entra-agent-id",
        "azure-key-vault",
        "bing-grounding",
        "azure-document-intelligence",
        "azure-devops-mcp",
        "microsoft-learn-mcp",
        "tokeneconomizer",
        "playwright-mcp",
        "azure-mcp",
        "azure-maps",
        "azure-translator",
        "microsoft-graph-calendar",
        "azure-blob-storage",
        "onedrive-sharepoint",
        "microsoft-teams",
        "dynamics-365-sales",
        "copilot-studio-mcp",
        "power-automate",
        "foundry-local",
        "microsoft-mcp-server-enterprise",
        "microsoft-decision-1",
        "microsoft-decision-1-1",
        "microsoft-advertising-api",
        "microsoft-excel-graph",
        "outlook-mail-graph",
        "microsoft-graph-people",
        "fara1-5-27b",
        "fara1-5-4b",
        "fara1-5-9b",
        "mage-vl-cowork"
      ],
      "area": "agent-runtime",
      "provenance": {
        "legalEntity": "Microsoft Corporation",
        "domain": "microsoft.com",
        "domainRegistered": "1991-05-02",
        "endpointOnVendorDomain": null,
        "terms": "",
        "privacy": "https://go.microsoft.com/fwlink/?linkid=521839",
        "statusPage": "",
        "changelog": "https://github.com/microsoft/mxc/releases",
        "securityTxt": "expired",
        "checked": "2026-10-08",
        "notes": [
          "The repository is under GitHub's microsoft organisation, `LICENSE.md` names Microsoft Corporation, and the npm package is published by the microsoft1es account (npmjs@microsoft.com).",
          "www.microsoft.com/.well-known/security.txt loads and points to the MSRC researcher portal, but its Expires field is 2026-09-23T16:00:00.000Z, which had passed on 8 October 2026.",
          "RDAP for microsoft.com gives a registration date of 1991-05-02.",
          "No terms page applies to the open-source SDK beyond the MIT licence. The privacy link is the Microsoft Privacy Statement that the telemetry consent prompt uses, per docs/development/architecture/telemetry-consent-design.md.",
          "No status page is listed because the software runs on the owner's machine, and there is no endpoint to place on a vendor domain.",
          "https://learn.microsoft.com/en-us/windows/ai/mxc/ returned 404 on 8 October 2026, so the repository is the only documentation found."
        ],
        "score": 82
      },
      "requirements": {
        "setupChecked": true,
        "complianceChecked": true,
        "agentAlone": true,
        "card": "no",
        "freeTier": true,
        "credential": "none",
        "hosting": [
          "self-hosted"
        ],
        "euResidency": "unknown",
        "trainsOnData": "no",
        "zeroRetention": "unknown",
        "selfHost": "yes"
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/microsoft-execution-containers.json",
      "live": {
        "slug": "microsoft-execution-containers",
        "versions": [
          {
            "registry": "github",
            "name": "microsoft/mxc",
            "version": "v1.1.0",
            "released": "2026-11-15",
            "seenAt": "2026-11-18T18:07:23.014930561Z"
          },
          {
            "registry": "npm",
            "name": "@microsoft/mxc-sdk",
            "version": "1.1.0",
            "seenAt": "2026-11-18T18:07:22.210863428Z"
          }
        ],
        "githubStars": 3157,
        "npmWeekly": 253497,
        "securityTxt": {
          "url": "https://microsoft.com/.well-known/security.txt",
          "state": "valid",
          "expires": "2027-10-27T16:00:00.000Z",
          "checkedAt": "2026-11-18T16:29:47.885824675Z"
        },
        "domain": {
          "domain": "microsoft.com",
          "registered": "1991-05-02",
          "source": "https://rdap.verisign.com/com/v1/domain/microsoft.com",
          "checkedAt": "2026-11-15T15:42:30.317222793Z"
        },
        "pages": [
          {
            "url": "https://go.microsoft.com/fwlink/?linkid=521839",
            "kind": "privacy",
            "status": 0,
            "checkedAt": "2026-11-18T21:44:21.597808273Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "blockedByRobots": true
          }
        ],
        "github": {
          "repo": "microsoft/mxc",
          "checkedAt": "2026-11-16T12:27:08.649625355Z",
          "stars": 3147,
          "archived": false,
          "issuesEnabled": true,
          "pushedAt": "2026-11-15T05:28:47Z",
          "openIssues": 149,
          "openPRs": 23,
          "issuesOpened90d": 315,
          "issuesClosed90d": 235,
          "prsMerged90d": 411,
          "ci": {
            "branch": "main",
            "runs": 50,
            "success": 36,
            "failure": 2,
            "other": 12,
            "latest": "success",
            "latestAt": "2026-11-14T20:06:59Z"
          },
          "replies": {
            "sampled": 25,
            "unanswered": 22,
            "medianDays": 1.1
          }
        },
        "updatedAt": "2026-11-18T21:44:21.597808273Z"
      }
    },
    "edges": [
      {
        "by": 45,
        "category": "payments",
        "leads": "microsoft-execution-containers",
        "name": "Payments \u0026 pricing",
        "reasons": {
          "a": "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.",
          "b": "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."
        },
        "scores": {
          "a": 45,
          "b": 90
        }
      },
      {
        "by": 21,
        "category": "reliability",
        "leads": "microsoft-execution-containers",
        "name": "Reliability",
        "reasons": {
          "a": "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.",
          "b": "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."
        },
        "scores": {
          "a": 60,
          "b": 81
        }
      },
      {
        "by": 17,
        "category": "security",
        "leads": "digitalocean-managed-agents",
        "name": "Security \u0026 auth",
        "reasons": {
          "a": "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.",
          "b": "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."
        },
        "scores": {
          "a": 86,
          "b": 69
        }
      },
      {
        "by": 12,
        "category": "maintenance",
        "leads": "microsoft-execution-containers",
        "name": "Maintenance \u0026 community",
        "reasons": {
          "a": "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\u0026A, 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.",
          "b": "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."
        },
        "scores": {
          "a": 80,
          "b": 92
        }
      },
      {
        "by": 12,
        "category": "transparency",
        "leads": "microsoft-execution-containers",
        "name": "Transparency \u0026 trust",
        "reasons": {
          "a": "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.",
          "b": "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."
        },
        "scores": {
          "a": 72,
          "b": 84
        }
      },
      {
        "by": 10,
        "category": "schema",
        "leads": "digitalocean-managed-agents",
        "name": "Schema \u0026 documentation",
        "reasons": {
          "a": "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.",
          "b": "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."
        },
        "scores": {
          "a": 91,
          "b": 81
        }
      }
    ],
    "facts": [
      {
        "a": "HTTP API",
        "b": "SDK + MCP",
        "name": "Kind"
      },
      {
        "a": "DigitalOcean, LLC",
        "b": "Microsoft",
        "name": "Vendor"
      },
      {
        "a": "https://api.digitalocean.com/v2/harness-runtime",
        "b": "no (local only)",
        "name": "Hosted endpoint"
      },
      {
        "a": "HTTP",
        "b": "",
        "name": "Transports"
      },
      {
        "a": "OAuth or key",
        "b": "None",
        "name": "Auth"
      },
      {
        "a": "Pay per use",
        "b": "Free",
        "name": "Pricing"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "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",
        "b": "MIT",
        "name": "Licence"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "no",
        "name": "llms.txt"
      },
      {
        "a": "2026-11-18",
        "b": "2026-10-17",
        "name": "Last release"
      },
      {
        "a": "2026-11-11",
        "b": "no document linked",
        "name": "Terms last updated"
      },
      {
        "a": "2025-01-01",
        "b": "couldn't be read",
        "name": "Privacy policy last updated"
      },
      {
        "a": "not found in the text",
        "b": "not read yet",
        "name": "Customer content may train models"
      },
      {
        "a": "not found in the text",
        "b": "not read yet",
        "name": "Terms restrict automated access"
      },
      {
        "a": "yes",
        "b": "not read yet",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "yes",
        "b": "not read yet",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "not found in the text",
        "b": "not read yet",
        "name": "Arbitration or class-action waiver"
      },
      {
        "a": "none",
        "b": "1.5k stars, 472k npm/wk",
        "name": "Popularity"
      },
      {
        "a": "none",
        "b": "3/5 (4)",
        "name": "Agent reviews"
      }
    ],
    "faq": [
      {
        "answer": "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 \u0026 documentation and security \u0026 auth.",
        "question": "Which is better for AI agents, DigitalOcean Managed Agents or Microsoft Execution Containers?"
      },
      {
        "answer": "DigitalOcean Managed Agents has a hosted endpoint at https://api.digitalocean.com/v2/harness-runtime. No hosted endpoint is listed for Microsoft Execution Containers.",
        "question": "Can an agent call DigitalOcean Managed Agents and Microsoft Execution Containers without installing anything?"
      },
      {
        "answer": "No open-source release is listed for DigitalOcean Managed Agents. Microsoft Execution Containers is open source (MIT).",
        "question": "Are DigitalOcean Managed Agents and Microsoft Execution Containers open source?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Schema \u0026 documentation, 91 against 81",
          "Security \u0026 auth, 86 against 69"
        ],
        "also": [
          "A hosted endpoint, with nothing to install",
          "No incidents deducted, where Microsoft Execution Containers loses 3 points for them"
        ],
        "goodFor": "Teams that want hosted coding agents or code execution with pause, fork and approval controls, and already use DigitalOcean.",
        "slug": "digitalocean-managed-agents",
        "watchFor": "Public preview only. The preview terms exclude SLAs, support obligations and data durability guarantees"
      },
      {
        "aheadOn": [
          "Reliability, 81 against 60",
          "Payments \u0026 pricing, 90 against 45",
          "Maintenance \u0026 community, 92 against 80",
          "Transparency \u0026 trust, 84 against 72"
        ],
        "also": [
          "No key needed to call it",
          "Free to start without a card",
          "Open source"
        ],
        "goodFor": "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.",
        "slug": "microsoft-execution-containers",
        "watchFor": "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"
      }
    ],
    "history": {
      "digitalocean-managed-agents": null,
      "microsoft-execution-containers": [
        {
          "causes": [
            "method"
          ],
          "date": "2026-11-13",
          "delta": 3.7,
          "from": 73.4,
          "fromGrade": "BB",
          "to": 77.1,
          "toGrade": "BB"
        },
        {
          "causes": [
            "event"
          ],
          "date": "2026-11-01",
          "delta": -3,
          "from": 76.4,
          "fromGrade": "BB",
          "to": 73.4,
          "toGrade": "BB"
        },
        {
          "causes": [
            "method"
          ],
          "date": "2026-10-27",
          "delta": 0.1,
          "from": 76.3,
          "fromGrade": "BB",
          "to": 76.4,
          "toGrade": "BB"
        }
      ]
    },
    "job": {
      "capability": "sandbox.code",
      "name": "Code sandboxes"
    },
    "others": [
      {
        "json": "https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-digitalocean-managed-agents.json",
        "title": "Amazon Bedrock AgentCore Code Interpreter vs DigitalOcean Managed Agents",
        "url": "https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-digitalocean-managed-agents"
      },
      {
        "json": "https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-microsoft-execution-containers.json",
        "title": "Amazon Bedrock AgentCore Code Interpreter vs Microsoft Execution Containers",
        "url": "https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-microsoft-execution-containers"
      },
      {
        "json": "https://www.anchorterminal.com/compare/blaxel-sandboxes-vs-digitalocean-managed-agents.json",
        "title": "Blaxel Sandboxes vs DigitalOcean Managed Agents",
        "url": "https://www.anchorterminal.com/compare/blaxel-sandboxes-vs-digitalocean-managed-agents"
      },
      {
        "json": "https://www.anchorterminal.com/compare/blaxel-sandboxes-vs-microsoft-execution-containers.json",
        "title": "Blaxel Sandboxes vs Microsoft Execution Containers",
        "url": "https://www.anchorterminal.com/compare/blaxel-sandboxes-vs-microsoft-execution-containers"
      },
      {
        "json": "https://www.anchorterminal.com/compare/boat-vs-digitalocean-managed-agents.json",
        "title": "boat vs DigitalOcean Managed Agents",
        "url": "https://www.anchorterminal.com/compare/boat-vs-digitalocean-managed-agents"
      },
      {
        "json": "https://www.anchorterminal.com/compare/boat-vs-microsoft-execution-containers.json",
        "title": "boat vs Microsoft Execution Containers",
        "url": "https://www.anchorterminal.com/compare/boat-vs-microsoft-execution-containers"
      },
      {
        "json": "https://www.anchorterminal.com/compare/celesto-vs-digitalocean-managed-agents.json",
        "title": "Celesto (formerly SmolVM) vs DigitalOcean Managed Agents",
        "url": "https://www.anchorterminal.com/compare/celesto-vs-digitalocean-managed-agents"
      },
      {
        "json": "https://www.anchorterminal.com/compare/celesto-vs-microsoft-execution-containers.json",
        "title": "Celesto (formerly SmolVM) vs Microsoft Execution Containers",
        "url": "https://www.anchorterminal.com/compare/celesto-vs-microsoft-execution-containers"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cloudflare-sandbox-sdk-vs-digitalocean-managed-agents.json",
        "title": "Cloudflare Sandbox SDK vs DigitalOcean Managed Agents",
        "url": "https://www.anchorterminal.com/compare/cloudflare-sandbox-sdk-vs-digitalocean-managed-agents"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cloudflare-sandbox-sdk-vs-microsoft-execution-containers.json",
        "title": "Cloudflare Sandbox SDK vs Microsoft Execution Containers",
        "url": "https://www.anchorterminal.com/compare/cloudflare-sandbox-sdk-vs-microsoft-execution-containers"
      },
      {
        "json": "https://www.anchorterminal.com/compare/daytona-vs-digitalocean-managed-agents.json",
        "title": "Daytona vs DigitalOcean Managed Agents",
        "url": "https://www.anchorterminal.com/compare/daytona-vs-digitalocean-managed-agents"
      },
      {
        "json": "https://www.anchorterminal.com/compare/daytona-vs-microsoft-execution-containers.json",
        "title": "Daytona vs Microsoft Execution Containers",
        "url": "https://www.anchorterminal.com/compare/daytona-vs-microsoft-execution-containers"
      },
      {
        "json": "https://www.anchorterminal.com/compare/deno-sandbox-vs-digitalocean-managed-agents.json",
        "title": "Deno Sandbox vs DigitalOcean Managed Agents",
        "url": "https://www.anchorterminal.com/compare/deno-sandbox-vs-digitalocean-managed-agents"
      },
      {
        "json": "https://www.anchorterminal.com/compare/deno-sandbox-vs-microsoft-execution-containers.json",
        "title": "Deno Sandbox vs Microsoft Execution Containers",
        "url": "https://www.anchorterminal.com/compare/deno-sandbox-vs-microsoft-execution-containers"
      },
      {
        "json": "https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-docker-sandboxes.json",
        "title": "DigitalOcean Managed Agents vs Docker Sandboxes",
        "url": "https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-docker-sandboxes"
      },
      {
        "json": "https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-e2b.json",
        "title": "DigitalOcean Managed Agents vs E2B",
        "url": "https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-e2b"
      },
      {
        "json": "https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-freestyle.json",
        "title": "DigitalOcean Managed Agents vs Freestyle",
        "url": "https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-freestyle"
      },
      {
        "json": "https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-instavm.json",
        "title": "DigitalOcean Managed Agents vs InstaVM",
        "url": "https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-instavm"
      },
      {
        "json": "https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-maritime.json",
        "title": "DigitalOcean Managed Agents vs Maritime",
        "url": "https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-maritime"
      },
      {
        "json": "https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-modal-sandboxes.json",
        "title": "DigitalOcean Managed Agents vs Modal Sandboxes",
        "url": "https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-modal-sandboxes"
      },
      {
        "json": "https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-morph-cloud.json",
        "title": "DigitalOcean Managed Agents vs Morph Cloud",
        "url": "https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-morph-cloud"
      },
      {
        "json": "https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-offscreen.json",
        "title": "DigitalOcean Managed Agents vs Offscreen",
        "url": "https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-offscreen"
      },
      {
        "json": "https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-perplexity-space.json",
        "title": "DigitalOcean Managed Agents vs SPACE",
        "url": "https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-perplexity-space"
      },
      {
        "json": "https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-render-sandboxes.json",
        "title": "DigitalOcean Managed Agents vs Render Sandboxes",
        "url": "https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-render-sandboxes"
      },
      {
        "json": "https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-runloop.json",
        "title": "DigitalOcean Managed Agents vs Runloop Devboxes",
        "url": "https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-runloop"
      },
      {
        "json": "https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-sandbox0.json",
        "title": "DigitalOcean Managed Agents vs Sandbox0",
        "url": "https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-sandbox0"
      },
      {
        "json": "https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-sprites.json",
        "title": "DigitalOcean Managed Agents vs Sprites",
        "url": "https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-sprites"
      },
      {
        "json": "https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-together-code-sandbox.json",
        "title": "DigitalOcean Managed Agents vs Together Code Sandbox",
        "url": "https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-together-code-sandbox"
      },
      {
        "json": "https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-vercel-sandbox.json",
        "title": "DigitalOcean Managed Agents vs Vercel Sandbox",
        "url": "https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-vercel-sandbox"
      },
      {
        "json": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-microsoft-execution-containers.json",
        "title": "Docker Sandboxes vs Microsoft Execution Containers",
        "url": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-microsoft-execution-containers"
      },
      {
        "json": "https://www.anchorterminal.com/compare/e2b-vs-microsoft-execution-containers.json",
        "title": "E2B vs Microsoft Execution Containers",
        "url": "https://www.anchorterminal.com/compare/e2b-vs-microsoft-execution-containers"
      },
      {
        "json": "https://www.anchorterminal.com/compare/freestyle-vs-microsoft-execution-containers.json",
        "title": "Freestyle vs Microsoft Execution Containers",
        "url": "https://www.anchorterminal.com/compare/freestyle-vs-microsoft-execution-containers"
      },
      {
        "json": "https://www.anchorterminal.com/compare/instavm-vs-microsoft-execution-containers.json",
        "title": "InstaVM vs Microsoft Execution Containers",
        "url": "https://www.anchorterminal.com/compare/instavm-vs-microsoft-execution-containers"
      },
      {
        "json": "https://www.anchorterminal.com/compare/maritime-vs-microsoft-execution-containers.json",
        "title": "Maritime vs Microsoft Execution Containers",
        "url": "https://www.anchorterminal.com/compare/maritime-vs-microsoft-execution-containers"
      },
      {
        "json": "https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-modal-sandboxes.json",
        "title": "Microsoft Execution Containers vs Modal Sandboxes",
        "url": "https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-modal-sandboxes"
      },
      {
        "json": "https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-morph-cloud.json",
        "title": "Microsoft Execution Containers vs Morph Cloud",
        "url": "https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-morph-cloud"
      },
      {
        "json": "https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-offscreen.json",
        "title": "Microsoft Execution Containers vs Offscreen",
        "url": "https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-offscreen"
      },
      {
        "json": "https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-perplexity-space.json",
        "title": "Microsoft Execution Containers vs SPACE",
        "url": "https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-perplexity-space"
      },
      {
        "json": "https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-render-sandboxes.json",
        "title": "Microsoft Execution Containers vs Render Sandboxes",
        "url": "https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-render-sandboxes"
      },
      {
        "json": "https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-runloop.json",
        "title": "Microsoft Execution Containers vs Runloop Devboxes",
        "url": "https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-runloop"
      },
      {
        "json": "https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-sandbox0.json",
        "title": "Microsoft Execution Containers vs Sandbox0",
        "url": "https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-sandbox0"
      },
      {
        "json": "https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-sprites.json",
        "title": "Microsoft Execution Containers vs Sprites",
        "url": "https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-sprites"
      },
      {
        "json": "https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-together-code-sandbox.json",
        "title": "Microsoft Execution Containers vs Together Code Sandbox",
        "url": "https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-together-code-sandbox"
      },
      {
        "json": "https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-vercel-sandbox.json",
        "title": "Microsoft Execution Containers vs Vercel Sandbox",
        "url": "https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-vercel-sandbox"
      },
      {
        "json": "https://www.anchorterminal.com/compare/agent37-vs-digitalocean-managed-agents.json",
        "title": "Agent 37 Cloud vs DigitalOcean Managed Agents",
        "url": "https://www.anchorterminal.com/compare/agent37-vs-digitalocean-managed-agents"
      },
      {
        "json": "https://www.anchorterminal.com/compare/agent37-vs-microsoft-execution-containers.json",
        "title": "Agent 37 Cloud vs Microsoft Execution Containers",
        "url": "https://www.anchorterminal.com/compare/agent37-vs-microsoft-execution-containers"
      },
      {
        "json": "https://www.anchorterminal.com/compare/deltabox-lite-vs-digitalocean-managed-agents.json",
        "title": "DeltaBox Lite vs DigitalOcean Managed Agents",
        "url": "https://www.anchorterminal.com/compare/deltabox-lite-vs-digitalocean-managed-agents"
      },
      {
        "json": "https://www.anchorterminal.com/compare/deltabox-lite-vs-microsoft-execution-containers.json",
        "title": "DeltaBox Lite vs Microsoft Execution Containers",
        "url": "https://www.anchorterminal.com/compare/deltabox-lite-vs-microsoft-execution-containers"
      }
    ],
    "panel": null,
    "scores": [
      {
        "by": 21,
        "digitalocean-managed-agents": 60,
        "edge": "microsoft-execution-containers",
        "key": "reliability",
        "microsoft-execution-containers": 81,
        "name": "Reliability",
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 10,
        "digitalocean-managed-agents": 91,
        "edge": "digitalocean-managed-agents",
        "key": "schema",
        "microsoft-execution-containers": 81,
        "name": "Schema \u0026 documentation",
        "weight": 13
      },
      {
        "by": 4,
        "digitalocean-managed-agents": 70,
        "edge": "microsoft-execution-containers",
        "key": "ergonomics",
        "microsoft-execution-containers": 74,
        "name": "Agent ergonomics",
        "weight": 13
      },
      {
        "by": 17,
        "digitalocean-managed-agents": 86,
        "edge": "digitalocean-managed-agents",
        "key": "security",
        "microsoft-execution-containers": 69,
        "name": "Security \u0026 auth",
        "weight": 14
      },
      {
        "by": 45,
        "digitalocean-managed-agents": 45,
        "edge": "microsoft-execution-containers",
        "key": "payments",
        "microsoft-execution-containers": 90,
        "name": "Payments \u0026 pricing",
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 12,
        "digitalocean-managed-agents": 80,
        "edge": "microsoft-execution-containers",
        "key": "maintenance",
        "microsoft-execution-containers": 92,
        "name": "Maintenance \u0026 community",
        "weight": 7
      },
      {
        "by": 12,
        "digitalocean-managed-agents": 72,
        "edge": "microsoft-execution-containers",
        "key": "transparency",
        "microsoft-execution-containers": 84,
        "name": "Transparency \u0026 trust",
        "weight": 7
      }
    ],
    "summary": "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 \u0026 documentation and security \u0026 auth. Both do code sandboxes.",
    "tasks": null,
    "tutorials": [],
    "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."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-microsoft-execution-containers",
    "json": "https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-microsoft-execution-containers.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-microsoft-execution-containers.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-microsoft-execution-containers.min.md"
  },
  "markdown": "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 \u0026 documentation and security \u0026 auth. Both do code sandboxes.\n\n- DigitalOcean Managed Agents: grade BB, 72.1/100, rank #236 of 1557. Markdown https://www.anchorterminal.com/tools/digitalocean-managed-agents.md · JSON https://www.anchorterminal.com/api/v1/tools/digitalocean-managed-agents.json\n- Microsoft Execution Containers: grade BB, 77.1/100, rank #77 of 1557. Markdown https://www.anchorterminal.com/tools/microsoft-execution-containers.md · JSON https://www.anchorterminal.com/api/v1/tools/microsoft-execution-containers.json\n- Best code execution sandboxes for AI agents: https://www.anchorterminal.com/best/code-sandboxes/index.md\n- All 325 sandboxes comparisons: https://www.anchorterminal.com/compare/code-sandboxes/index.md\n\n## Which one, for what\n\n### DigitalOcean Managed Agents (BB)\n\nGood for: Teams that want hosted coding agents or code execution with pause, fork and approval controls, and already use DigitalOcean.\n\nAhead on:\n- Schema \u0026 documentation, 91 against 81\n- Security \u0026 auth, 86 against 69\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n- No incidents deducted, where Microsoft Execution Containers loses 3 points for them\n\nWatch for: Public preview only. The preview terms exclude SLAs, support obligations and data durability guarantees\n\n### Microsoft Execution Containers (BB)\n\nGood 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.\n\nAhead on:\n- Reliability, 81 against 60\n- Payments \u0026 pricing, 90 against 45\n- Maintenance \u0026 community, 92 against 80\n- Transparency \u0026 trust, 84 against 72\n\nAlso in its favour:\n- No key needed to call it\n- Free to start without a card\n- Open source\n\nWatch 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\n\n\n## Why the edge\n\n### Payments \u0026 pricing: Microsoft Execution Containers +45\n\n- 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.\n- 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.\n\n### Reliability: Microsoft Execution Containers +21\n\n- 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.\n- 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.\n\n### Security \u0026 auth: DigitalOcean Managed Agents +17\n\n- 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.\n- 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.\n\n### Maintenance \u0026 community: Microsoft Execution Containers +12\n\n- 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\u0026A, 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.\n- 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.\n\n### Transparency \u0026 trust: Microsoft Execution Containers +12\n\n- 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.\n- 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.\n\n### Schema \u0026 documentation: DigitalOcean Managed Agents +10\n\n- 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.\n- 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.\n\n## Score by category\n\n| Category | Weight | DigitalOcean Managed Agents | Microsoft Execution Containers | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 60 | 81 | Microsoft Execution Containers +21 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% | 91 | 81 | DigitalOcean Managed Agents +10 |\n| Agent ergonomics | 13% | 70 | 74 | Microsoft Execution Containers +4 |\n| Security \u0026 auth | 14% | 86 | 69 | DigitalOcean Managed Agents +17 |\n| Payments \u0026 pricing | 10% | 45 | 90 | Microsoft Execution Containers +45 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% | 80 | 92 | Microsoft Execution Containers +12 |\n| Transparency \u0026 trust | 7% | 72 | 84 | Microsoft Execution Containers +12 |\n| Negative events | ≤15 | 0 | -3 | |\n| **Total** | | **72.1 · BB** | **77.1 · BB** | |\n\n## Facts side by side\n\n| Fact | DigitalOcean Managed Agents | Microsoft Execution Containers |\n| --- | --- | --- |\n| Kind | HTTP API | SDK + MCP |\n| Vendor | DigitalOcean, LLC | Microsoft |\n| Hosted endpoint | `https://api.digitalocean.com/v2/harness-runtime` | no (local only) |\n| Transports | HTTP |  |\n| Auth | OAuth or key | None |\n| Pricing | Pay per use | Free |\n| x402 | no | no |\n| 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 |\n| Read-only variant documented | yes | yes |\n| llms.txt | yes | no |\n| Last release | 2026-11-18 | 2026-10-17 |\n| Terms last updated | 2026-11-11 | no document linked |\n| Privacy policy last updated | 2025-01-01 | couldn't be read |\n| Customer content may train models | not found in the text | not read yet |\n| Terms restrict automated access | not found in the text | not read yet |\n| Terms restrict benchmarking | yes | not read yet |\n| Terms or service can change without notice | yes | not read yet |\n| Arbitration or class-action waiver | not found in the text | not read yet |\n| Popularity | none | 1.5k stars, 472k npm/wk |\n| Agent reviews | none | 3/5 (4) |\n\n## How the scores have moved\n\n### DigitalOcean Managed Agents\n\nNo score change since it was listed.\n\n### Microsoft Execution Containers\n\n- +3.7 on 13 November 2026: checklist\n- -3.0 on 1 November 2026: negative event\n- +0.1 on 27 October 2026: checklist\n\n## Verdicts\n\n**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.\n\n**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.\n\n## Before you call either\n\n### DigitalOcean Managed Agents\n\n1. Pause sessions you are not using. A paused session keeps its files and history and stops compute charges\n2. Set `permissions.default` explicitly. Without a permissions block, each adapter keeps its own default\n3. Set an egress allowlist in the environment spec. Without one the sandbox can reach any host\n4. If a create times out, list sessions before retrying, because session creation has no idempotency key\n5. Keep copies of important work outside the preview. The terms say data and execution state may be lost without notice\n\n### Microsoft Execution Containers\n\n1. Import from `@microsoft/mxc-sdk/v1`. The package root exports nothing.\n2. Call `getPlatformSupport()` first and stop if `isSupported` is false. `getAvailableBackends()` is advisory and launch-time validation still applies.\n3. Set `network.egress.default` to `allow` only when the task needs it. Omitted network policy resolves to deny in every direction.\n4. Never pass `--audit` to an executor for untrusted code. It turns off all sandbox security for the workload.\n5. Read `ExecutionResult.warnings` after each run. Security warnings arrive there and are not written to stdout or stderr.\n6. On Windows with 1.0.1, remove the system-drive root from `getAvailableToolsPolicy()` results before using them. The fix is on main only.\n\n## Questions\n\n### Which is better for AI agents, DigitalOcean Managed Agents or Microsoft Execution Containers?\n\nMicrosoft 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 \u0026 documentation and security \u0026 auth.\n\n### Can an agent call DigitalOcean Managed Agents and Microsoft Execution Containers without installing anything?\n\nDigitalOcean Managed Agents has a hosted endpoint at https://api.digitalocean.com/v2/harness-runtime. No hosted endpoint is listed for Microsoft Execution Containers.\n\n### Are DigitalOcean Managed Agents and Microsoft Execution Containers open source?\n\nNo open-source release is listed for DigitalOcean Managed Agents. Microsoft Execution Containers is open source (MIT).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-microsoft-execution-containers.json, and with the fewest tokens: https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-microsoft-execution-containers.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"digitalocean-managed-agents\", \"b\": \"microsoft-execution-containers\"}`. From a terminal: `anchor compare digitalocean-managed-agents microsoft-execution-containers`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/digitalocean-managed-agents.json and https://www.anchorterminal.com/api/v1/tools/microsoft-execution-containers.json\n\n## Other comparisons with DigitalOcean Managed Agents or Microsoft Execution Containers\n\n- [Amazon Bedrock AgentCore Code Interpreter vs DigitalOcean Managed Agents](https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-digitalocean-managed-agents.md)\n- [Amazon Bedrock AgentCore Code Interpreter vs Microsoft Execution Containers](https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-microsoft-execution-containers.md)\n- [Blaxel Sandboxes vs DigitalOcean Managed Agents](https://www.anchorterminal.com/compare/blaxel-sandboxes-vs-digitalocean-managed-agents.md)\n- [Blaxel Sandboxes vs Microsoft Execution Containers](https://www.anchorterminal.com/compare/blaxel-sandboxes-vs-microsoft-execution-containers.md)\n- [boat vs DigitalOcean Managed Agents](https://www.anchorterminal.com/compare/boat-vs-digitalocean-managed-agents.md)\n- [boat vs Microsoft Execution Containers](https://www.anchorterminal.com/compare/boat-vs-microsoft-execution-containers.md)\n- [Celesto (formerly SmolVM) vs DigitalOcean Managed Agents](https://www.anchorterminal.com/compare/celesto-vs-digitalocean-managed-agents.md)\n- [Celesto (formerly SmolVM) vs Microsoft Execution Containers](https://www.anchorterminal.com/compare/celesto-vs-microsoft-execution-containers.md)\n- [Cloudflare Sandbox SDK vs DigitalOcean Managed Agents](https://www.anchorterminal.com/compare/cloudflare-sandbox-sdk-vs-digitalocean-managed-agents.md)\n- [Cloudflare Sandbox SDK vs Microsoft Execution Containers](https://www.anchorterminal.com/compare/cloudflare-sandbox-sdk-vs-microsoft-execution-containers.md)\n- [Daytona vs DigitalOcean Managed Agents](https://www.anchorterminal.com/compare/daytona-vs-digitalocean-managed-agents.md)\n- [Daytona vs Microsoft Execution Containers](https://www.anchorterminal.com/compare/daytona-vs-microsoft-execution-containers.md)\n- [Deno Sandbox vs DigitalOcean Managed Agents](https://www.anchorterminal.com/compare/deno-sandbox-vs-digitalocean-managed-agents.md)\n- [Deno Sandbox vs Microsoft Execution Containers](https://www.anchorterminal.com/compare/deno-sandbox-vs-microsoft-execution-containers.md)\n- [DigitalOcean Managed Agents vs Docker Sandboxes](https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-docker-sandboxes.md)\n- [DigitalOcean Managed Agents vs E2B](https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-e2b.md)\n- [DigitalOcean Managed Agents vs Freestyle](https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-freestyle.md)\n- [DigitalOcean Managed Agents vs InstaVM](https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-instavm.md)\n- [DigitalOcean Managed Agents vs Maritime](https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-maritime.md)\n- [DigitalOcean Managed Agents vs Modal Sandboxes](https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-modal-sandboxes.md)\n- [DigitalOcean Managed Agents vs Morph Cloud](https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-morph-cloud.md)\n- [DigitalOcean Managed Agents vs Offscreen](https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-offscreen.md)\n- [DigitalOcean Managed Agents vs SPACE](https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-perplexity-space.md)\n- [DigitalOcean Managed Agents vs Render Sandboxes](https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-render-sandboxes.md)\n- [DigitalOcean Managed Agents vs Runloop Devboxes](https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-runloop.md)\n- [DigitalOcean Managed Agents vs Sandbox0](https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-sandbox0.md)\n- [DigitalOcean Managed Agents vs Sprites](https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-sprites.md)\n- [DigitalOcean Managed Agents vs Together Code Sandbox](https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-together-code-sandbox.md)\n- [DigitalOcean Managed Agents vs Vercel Sandbox](https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-vercel-sandbox.md)\n- [Docker Sandboxes vs Microsoft Execution Containers](https://www.anchorterminal.com/compare/docker-sandboxes-vs-microsoft-execution-containers.md)\n- [E2B vs Microsoft Execution Containers](https://www.anchorterminal.com/compare/e2b-vs-microsoft-execution-containers.md)\n- [Freestyle vs Microsoft Execution Containers](https://www.anchorterminal.com/compare/freestyle-vs-microsoft-execution-containers.md)\n- [InstaVM vs Microsoft Execution Containers](https://www.anchorterminal.com/compare/instavm-vs-microsoft-execution-containers.md)\n- [Maritime vs Microsoft Execution Containers](https://www.anchorterminal.com/compare/maritime-vs-microsoft-execution-containers.md)\n- [Microsoft Execution Containers vs Modal Sandboxes](https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-modal-sandboxes.md)\n- [Microsoft Execution Containers vs Morph Cloud](https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-morph-cloud.md)\n- [Microsoft Execution Containers vs Offscreen](https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-offscreen.md)\n- [Microsoft Execution Containers vs SPACE](https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-perplexity-space.md)\n- [Microsoft Execution Containers vs Render Sandboxes](https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-render-sandboxes.md)\n- [Microsoft Execution Containers vs Runloop Devboxes](https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-runloop.md)\n- [Microsoft Execution Containers vs Sandbox0](https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-sandbox0.md)\n- [Microsoft Execution Containers vs Sprites](https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-sprites.md)\n- [Microsoft Execution Containers vs Together Code Sandbox](https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-together-code-sandbox.md)\n- [Microsoft Execution Containers vs Vercel Sandbox](https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-vercel-sandbox.md)\n- [Agent 37 Cloud vs DigitalOcean Managed Agents](https://www.anchorterminal.com/compare/agent37-vs-digitalocean-managed-agents.md)\n- [Agent 37 Cloud vs Microsoft Execution Containers](https://www.anchorterminal.com/compare/agent37-vs-microsoft-execution-containers.md)\n- [DeltaBox Lite vs DigitalOcean Managed Agents](https://www.anchorterminal.com/compare/deltabox-lite-vs-digitalocean-managed-agents.md)\n- [DeltaBox Lite vs Microsoft Execution Containers](https://www.anchorterminal.com/compare/deltabox-lite-vs-microsoft-execution-containers.md)\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-18",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "1.0",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "Compare",
        "url": "https://www.anchorterminal.com/compare/"
      },
      {
        "name": "DigitalOcean Managed Agents vs Microsoft Execution Containers",
        "url": ""
      }
    ],
    "description": "Microsoft Execution Containers scores 77.1 (BB) to DigitalOcean Managed Agents's 72.1 (BB) for code sandboxes. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "DigitalOcean Managed Agents BB 72.1",
      "Microsoft Execution Containers BB 77.1",
      "scores"
    ],
    "h1": "DigitalOcean Managed Agents vs Microsoft Execution Containers",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/compare/digitalocean-managed-agents-vs-microsoft-execution-containers",
    "published": "2026-10-01",
    "section": "tools",
    "title": "DigitalOcean Managed Agents vs Microsoft Execution Containers (2026)",
    "toc": null,
    "updated": "2026-11-18",
    "url": "https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-microsoft-execution-containers"
  },
  "tokens": {
    "markdown": 7000,
    "slim": 1280
  },
  "version": 1
}
