{
  "data": {
    "a": {
      "slug": "docker-sandboxes",
      "name": "Docker Sandboxes",
      "vendor": "Docker",
      "vendorUrl": "https://www.docker.com",
      "company": "docker.com",
      "kind": "http-api",
      "category": "code-sandboxes",
      "summary": "Docker Sandboxes runs AI agents in microVM sandboxes, locally through the `sbx` CLI or on Docker-managed cloud compute through `sbx --cloud`, a REST API and a TypeScript SDK. Cloud sandboxes belong to the experimental Docker Agentic Platform.",
      "url": "https://www.anchorterminal.com/tools/docker-sandboxes",
      "markdownUrl": "https://www.anchorterminal.com/tools/docker-sandboxes.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/docker-sandboxes.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/docker-sandboxes.json",
      "dns": "docker-sandboxes.grade.anchorterminal.com",
      "repo": "https://github.com/docker/sbx-releases",
      "license": "Proprietary. The `sbx` binaries in docker/sbx-releases are under a licence that reserves all rights to Docker Inc., and cloud sandboxes run under a Docker Agentic Platform subscription",
      "transports": [
        "http"
      ],
      "packages": [
        {
          "registry": "npm",
          "name": "@docker/sandboxes"
        }
      ],
      "auth": "mixed",
      "authNotes": "Cloud access needs a Docker account with an active Docker Agentic Platform pay-as-you-go subscription, bought through Docker Billing in a browser. Automation uses a Docker personal access token created with Allow Cloud Sandboxes access (the `sandbox:use` scope), which the SDK exchanges for short-lived access tokens. Interactive use signs in through a browser device flow. Each operation checks a named permission such as `sandboxesCreate` or `sandboxesDelete`.",
      "pricing": "usage",
      "pricingNotes": "Cloud compute is pay-as-you-go with no recurring fee, metered by the second on runtime and the chosen CPU and memory size, billed monthly. The docs publish no unit prices, which appear in the Agentic Platform console. Signup needs billing and payment details and gives a one-time promotional credit. The `sbx` CLI and local sandboxes are free, including for commercial work. Model inference is billed by the user's own provider.",
      "priceSummary": "Pay per use",
      "where": "local",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the Sandboxes API's OpenAPI document, the sandbox and Agentic Platform docs or the billing pages in the docker/docs repository (checked 2026-11-18). Payment is a Docker Billing subscription.",
        "endpoints": []
      },
      "toolCount": null,
      "popularity": {
        "githubStars": 527,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-11-18"
      },
      "docsUrl": "https://docs.docker.com/ai/sandboxes/",
      "llmsTxt": "https://docs.docker.com/llms.txt",
      "openapi": "https://github.com/docker/docs/blob/main/content/reference/api/sandboxes/api.yaml",
      "capabilities": [
        "sandbox.code",
        "sandbox.fs",
        "sandbox.persist"
      ],
      "tags": [
        "hosted",
        "usage",
        "beta",
        "microvm",
        "typescript",
        "cli",
        "openapi",
        "llms-txt",
        "docker"
      ],
      "lastRelease": "2026-11-16",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 62.1,
        "grade": "B",
        "agentReady": false,
        "rank": 698,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 17,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 83,
          "maintenance": 71,
          "payments": 0,
          "reliability": 45,
          "schema": 90,
          "security": 69,
          "transparency": 77
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-18"
        },
        "negative": 0,
        "verdict": "The cloud Sandboxes API has a public OpenAPI contract, idempotency keys, etag checks and credential injection that keeps keys out of the VM. Cloud access needs a paid Docker Agentic Platform subscription that is still experimental, and the docs publish no unit prices.",
        "bestFor": "Running coding agents such as Claude Code or Codex in a disposable cloud VM, or the same kit locally for free.",
        "strengths": [
          "Public OpenAPI 3.2 contract with 58 described operations, and llms.txt and Markdown copies of the docs",
          "`Idempotency-Key` on creates, starts, stops and deletes, kept for at least 24 hours, and `If-Match` etags on updates",
          "Credentials are added to outbound requests outside the VM, so code in the sandbox never holds the raw key",
          "Errors carry stable codes and typed details, with a documented action for each code",
          "Three stable `sbx` releases between 3 and 16 November 2026, with dated release notes"
        ],
        "weaknesses": [
          "Docker Agentic Platform, needed for every cloud interface, is experimental, and no SLA was found",
          "No unit prices on docker.com or in the docs, and signup asks for payment details in a browser",
          "The SDK is TypeScript only, and the source of `sbx` and the SDK is not public",
          "Request rate limits are described without numbers",
          "Cloud sandboxes live at most 24 hours from creation, and snapshots are deleted after seven days of non-use"
        ],
        "agentNotes": [
          "Create the Docker personal access token with Allow Cloud Sandboxes access. Registry permissions alone don't grant the `sandbox:use` scope",
          "Send the same `Idempotency-Key` when you retry a create, so a lost response doesn't start a second sandbox",
          "Pass the etag from your latest read in `If-Match`. A stale etag returns 412 and a missing one 428",
          "Set `--ttl` and `--on-timeout` at creation. The default deletes sandboxes that can't be resumed after one hour",
          "Set the account network policy to deny-all and add allow rules per sandbox, since allow-all lets the sandbox reach any host"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "B",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 62.1
          }
        ],
        "editorialScores": {
          "ergonomics": 83,
          "maintenance": 71,
          "payments": 0,
          "reliability": 45,
          "schema": 90,
          "security": 69,
          "transparency": 57
        },
        "provenanceScore": 97,
        "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",
          "lastMoved": "2026-11-18",
          "oldest": "2026-11-18",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "install": "npm install @docker/sandboxes  # or brew install docker/tap/sbx"
      },
      "letme": {
        "capability": "https://letme.dev/sandbox.code",
        "tool": "https://letme.dev/docker-sandboxes"
      },
      "sameCompany": [
        "docker-agent",
        "docker-model-runner"
      ],
      "area": "agent-runtime",
      "provenance": {
        "legalEntity": "Docker, Inc.",
        "domain": "docker.com",
        "domainRegistered": "1995-01-25",
        "endpointOnVendorDomain": true,
        "terms": "https://www.docker.com/legal/docker-subscription-service-agreement/",
        "privacy": "https://www.docker.com/legal/privacy/",
        "statusPage": "https://www.dockerstatus.com/",
        "changelog": "https://docs.docker.com/ai/sandboxes/release-notes/",
        "securityTxt": "valid",
        "checked": "2026-11-18",
        "notes": [
          "The Docker Subscription Service Agreement (last updated 26 August 2026), which Docker's Terms of Use say governs paid services, defines Agentic Platform Services and Sandbox, so it governs cloud sandboxes. The privacy policy at /legal/privacy/ says the Agentic Platform and cloud sandboxes are hosted in the United States.",
          "The API base URL https://connect.docker.com/sandboxes is a docker.com subdomain, per the OpenAPI document.",
          "docs.docker.com's robots.txt allows all agents with Content-Signal ai-train=yes, search=yes, ai-input=yes, and the published pages are served as Markdown. www.docker.com's robots.txt disallows only admin, thank-you, search and asset paths (read 18 November 2026).",
          "dockerstatus.com (incident.io) lists Docker Sandboxes under Cloud and AI Services and Docker Agentic Platform under Beta Products. Its incident history is drawn by a script and wasn't readable.",
          "docker/sbx-releases holds release binaries, a SECURITY.md sending reports to security@docker.com with acknowledgement within 72 hours, and an all-rights-reserved licence. The source of `sbx` and of `@docker/sandboxes` is not public. Legal entity, security.txt and domain date are carried from docker-agent (checked 1 November 2026)."
        ],
        "score": 97
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/docker-sandboxes.json",
      "live": {
        "slug": "docker-sandboxes",
        "vendorStatus": {
          "page": "https://www.dockerstatus.com",
          "indicator": "none",
          "summary": "All Systems Operational",
          "checkedAt": "2026-11-18T22:37:48.853198999Z"
        },
        "updatedAt": "2026-11-18T22:37:48.853198999Z"
      }
    },
    "answer": "Microsoft Execution Containers scores 77.1 (BB) on agent readiness against Docker Sandboxes's 62.1 (B), and leads in 4 of 7 scored categories. Docker Sandboxes leads on schema \u0026 documentation and agent ergonomics.",
    "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": 90,
        "category": "payments",
        "leads": "microsoft-execution-containers",
        "name": "Payments \u0026 pricing",
        "reasons": {
          "a": "No x402, MPP or L402 (0). Compute is metered per second by size, but neither the docs, the Docker Sandboxes product page nor docker.com/pricing publishes a unit price. The plans page says usage and pricing show on the Usage \u0026 billing page after sign-in (0). Signup to Docker Agentic Platform asks for billing and payment details at checkout, with a one-time promotional credit after, so there is no card-free start for cloud sandboxes (0). A person subscribes in a browser and creates the access token (0). The free local `sbx` CLI is not the graded surface. 0+0+0+0 = 0.",
          "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": 0,
          "b": 90
        }
      },
      {
        "by": 36,
        "category": "reliability",
        "leads": "microsoft-execution-containers",
        "name": "Reliability",
        "reasons": {
          "a": "Hosted lines, for the cloud Sandboxes API. dockerstatus.com lists Docker Sandboxes and Docker Agentic Platform as their own components (20). Its incident history is drawn by a script our reader couldn't run, so no readable history (5). Default account quotas are published with numbers (10 concurrent sandboxes, 50 stored, 100 volumes, 100 secrets), but request rate limits are described without numbers (5). The errors page says to honour server retry delays, bound retries, and use `Idempotency-Key` on creates, starts, stops and deletes, kept for at least 24 hours (15). No SLA found in the docs (0). Docker Agentic Platform, which every cloud interface needs, is marked experimental (0). 20+5+5+15+0+0 = 45.",
          "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": 45,
          "b": 81
        }
      },
      {
        "by": 21,
        "category": "maintenance",
        "leads": "microsoft-execution-containers",
        "name": "Maintenance \u0026 community",
        "reasons": {
          "a": "`sbx` 0.54.0 on 16 November 2026, per the dated release notes (30). Stable releases 0.51.0 on 3 November, 0.53.0 on 11 November and 0.54.0 on 16 November, with nightly builds tagged daily in docker/sbx-releases (20). Closed service with dated release notes and GitHub issues on docker/sbx-releases as the feedback channel. Issue response times could not be read (8). One official SDK, `@docker/sandboxes` for TypeScript, plus the CLI (10). Source and CI are not public, so package health is unchecked (3). 30+20+8+10+3 = 71.",
          "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": 71,
          "b": 92
        }
      },
      {
        "by": 9,
        "category": "schema",
        "leads": "docker-sandboxes",
        "name": "Schema \u0026 documentation",
        "reasons": {
          "a": "An OpenAPI 3.2 document for the Sandboxes API with 42 paths and 58 operations, each with a description, in the docs repository and linked from the API reference (25). The docs build emits llms.txt, llms-full.txt and a Markdown copy of every page, per the repository's Hugo configuration (10). Operation descriptions are short and generated in form (\"List lists directory entries by path ascending\"), and the concepts and cookbook pages explain when to use kits, images, snapshots and volumes (12). Typed inputs with 95 enums, required fields and `additionalProperties` constraints (13). 36 cookbook recipes in TypeScript and an errors page with a code table (15). Paths are versioned under `/v1`, and dated release notes cover `sbx` and the Agentic Platform (15). 25+10+12+13+15+15 = 90.",
          "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": 90,
          "b": 81
        }
      },
      {
        "by": 9,
        "category": "ergonomics",
        "leads": "docker-sandboxes",
        "name": "Agent ergonomics",
        "reasons": {
          "a": "Lists take `pageSize` and `pageToken`, and filters and ordering are given per operation, so responses can be kept small (15). Pagination and a `filter` parameter of exact-match terms on list operations (18). Errors carry a stable `code`, a message and typed `google.rpc.ErrorInfo` details, with a documented action for each of eight codes (20). `Idempotency-Key` on mutations, `If-Match` etags on updates and deletes, and a documented recovery path for lost responses and failed waits (20). Kit launch helpers default to the `small` size, but the SDK is TypeScript only, with the `sbx` CLI and plain REST beside it (10). 15+18+20+20+10 = 83.",
          "b": "One request type with `command` as the only required field, and `run` returns stdout, stderr, the exit code, a timeout flag and warnings. We found no documented cap on captured output, and the npm package is a 37.7 MB tarball (18 of 25). `spawn` streams output and `timeoutMs` bounds a run, but there is no truncation or size control on captured output (10 of 20). `MxcError` carries one of 12 codes with optional operation, native code and remediation, and a deny-and-record mode lists blocked accesses on ProcessContainer (18 of 20). `validate*` calls dry-run every lifecycle step, and lifecycle state errors are typed (`already_started`, `stale_id`). Issue #1429, open since 6 October, reports a second deprovision returning success, per the 8 October check, not re-read on 17 October. Not an MCP server, so no tool annotations apply (13 of 20). Network, filesystem and UI policy default to deny, and official SDKs exist for Node.js, .NET and Rust (15). 18+10+18+13+15 = 74."
        },
        "scores": {
          "a": 83,
          "b": 74
        }
      },
      {
        "by": 7,
        "category": "transparency",
        "leads": "microsoft-execution-containers",
        "name": "Transparency \u0026 trust",
        "reasons": {
          "a": "Closed software. The release repository's licence reserves all rights, and Docker's Subscription Service Agreement (26 August 2026) names Agentic Platform Services and Sandboxes (15). The privacy policy names the Agentic Platform and cloud sandboxes and says they're hosted in the United States, and the Agentic Platform FAQ gives retention for service logs (31 days), raw telemetry (12 months) and snapshots (seven days of non-use). The DPA wasn't read (20). Release notes call out breaking changes and deprecations by version and date, such as `sbx ports`, and the Agentic Platform docs warn that behaviour may change while it is experimental (10). CLI telemetry is disclosed with two opt-outs, and the hosting location is stated. No sub-processor list for cloud sandboxes was found (12). 15+20+10+12 = 57.",
          "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": 77,
          "b": 84
        }
      }
    ],
    "facts": [
      {
        "a": "HTTP API",
        "b": "SDK + MCP",
        "name": "Kind"
      },
      {
        "a": "Docker",
        "b": "Microsoft",
        "name": "Vendor"
      },
      {
        "a": "no (local only)",
        "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. The `sbx` binaries in docker/sbx-releases are under a licence that reserves all rights to Docker Inc., and cloud sandboxes run under a Docker Agentic Platform subscription",
        "b": "MIT",
        "name": "Licence"
      },
      {
        "a": "no",
        "b": "yes",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "no",
        "name": "llms.txt"
      },
      {
        "a": "2026-11-16",
        "b": "2026-10-17",
        "name": "Last release"
      },
      {
        "a": "2026-08-26",
        "b": "no document linked",
        "name": "Terms last updated"
      },
      {
        "a": "2026-08-26",
        "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": "yes",
        "b": "not read yet",
        "name": "Terms restrict automated access"
      },
      {
        "a": "yes",
        "b": "not read yet",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "not found in the text",
        "b": "not read yet",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "yes",
        "b": "not read yet",
        "name": "Arbitration or class-action waiver"
      },
      {
        "a": "527 stars",
        "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 Docker Sandboxes's 62.1 (B), and leads in 4 of 7 scored categories. Docker Sandboxes leads on schema \u0026 documentation and agent ergonomics.",
        "question": "Which is better for AI agents, Docker Sandboxes or Microsoft Execution Containers?"
      },
      {
        "answer": "No hosted endpoint is listed for Docker Sandboxes. No hosted endpoint is listed for Microsoft Execution Containers.",
        "question": "Can an agent call Docker Sandboxes and Microsoft Execution Containers without installing anything?"
      },
      {
        "answer": "No open-source release is listed for Docker Sandboxes. Microsoft Execution Containers is open source (MIT).",
        "question": "Are Docker Sandboxes and Microsoft Execution Containers open source?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Schema \u0026 documentation, 90 against 81",
          "Agent ergonomics, 83 against 74"
        ],
        "also": [
          "No incidents deducted, where Microsoft Execution Containers loses 3 points for them"
        ],
        "goodFor": "Running coding agents such as Claude Code or Codex in a disposable cloud VM, or the same kit locally for free.",
        "slug": "docker-sandboxes",
        "watchFor": "Docker Agentic Platform, needed for every cloud interface, is experimental, and no SLA was found"
      },
      {
        "aheadOn": [
          "Reliability, 81 against 45",
          "Payments \u0026 pricing, 90 against 0",
          "Maintenance \u0026 community, 92 against 71",
          "Transparency \u0026 trust, 84 against 77"
        ],
        "also": [
          "Agent-ready, a grade of BB or better",
          "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": {
      "docker-sandboxes": [
        {
          "causes": [
            "terms",
            "evidence"
          ],
          "date": "2026-11-18",
          "delta": 4.7,
          "from": 57.4,
          "fromGrade": "C",
          "to": 62.1,
          "toGrade": "B"
        }
      ],
      "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-docker-sandboxes.json",
        "title": "Amazon Bedrock AgentCore Code Interpreter vs Docker Sandboxes",
        "url": "https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-docker-sandboxes"
      },
      {
        "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-docker-sandboxes.json",
        "title": "Blaxel Sandboxes vs Docker Sandboxes",
        "url": "https://www.anchorterminal.com/compare/blaxel-sandboxes-vs-docker-sandboxes"
      },
      {
        "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-docker-sandboxes.json",
        "title": "boat vs Docker Sandboxes",
        "url": "https://www.anchorterminal.com/compare/boat-vs-docker-sandboxes"
      },
      {
        "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-docker-sandboxes.json",
        "title": "Celesto (formerly SmolVM) vs Docker Sandboxes",
        "url": "https://www.anchorterminal.com/compare/celesto-vs-docker-sandboxes"
      },
      {
        "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-docker-sandboxes.json",
        "title": "Cloudflare Sandbox SDK vs Docker Sandboxes",
        "url": "https://www.anchorterminal.com/compare/cloudflare-sandbox-sdk-vs-docker-sandboxes"
      },
      {
        "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-docker-sandboxes.json",
        "title": "Daytona vs Docker Sandboxes",
        "url": "https://www.anchorterminal.com/compare/daytona-vs-docker-sandboxes"
      },
      {
        "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-docker-sandboxes.json",
        "title": "Deno Sandbox vs Docker Sandboxes",
        "url": "https://www.anchorterminal.com/compare/deno-sandbox-vs-docker-sandboxes"
      },
      {
        "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-microsoft-execution-containers.json",
        "title": "DigitalOcean Managed Agents vs Microsoft Execution Containers",
        "url": "https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-microsoft-execution-containers"
      },
      {
        "json": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-e2b.json",
        "title": "Docker Sandboxes vs E2B",
        "url": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-e2b"
      },
      {
        "json": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-freestyle.json",
        "title": "Docker Sandboxes vs Freestyle",
        "url": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-freestyle"
      },
      {
        "json": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-instavm.json",
        "title": "Docker Sandboxes vs InstaVM",
        "url": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-instavm"
      },
      {
        "json": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-maritime.json",
        "title": "Docker Sandboxes vs Maritime",
        "url": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-maritime"
      },
      {
        "json": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-modal-sandboxes.json",
        "title": "Docker Sandboxes vs Modal Sandboxes",
        "url": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-modal-sandboxes"
      },
      {
        "json": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-morph-cloud.json",
        "title": "Docker Sandboxes vs Morph Cloud",
        "url": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-morph-cloud"
      },
      {
        "json": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-offscreen.json",
        "title": "Docker Sandboxes vs Offscreen",
        "url": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-offscreen"
      },
      {
        "json": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-perplexity-space.json",
        "title": "Docker Sandboxes vs SPACE",
        "url": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-perplexity-space"
      },
      {
        "json": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-render-sandboxes.json",
        "title": "Docker Sandboxes vs Render Sandboxes",
        "url": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-render-sandboxes"
      },
      {
        "json": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-runloop.json",
        "title": "Docker Sandboxes vs Runloop Devboxes",
        "url": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-runloop"
      },
      {
        "json": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-sandbox0.json",
        "title": "Docker Sandboxes vs Sandbox0",
        "url": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-sandbox0"
      },
      {
        "json": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-sprites.json",
        "title": "Docker Sandboxes vs Sprites",
        "url": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-sprites"
      },
      {
        "json": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-together-code-sandbox.json",
        "title": "Docker Sandboxes vs Together Code Sandbox",
        "url": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-together-code-sandbox"
      },
      {
        "json": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-vercel-sandbox.json",
        "title": "Docker Sandboxes vs Vercel Sandbox",
        "url": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-vercel-sandbox"
      },
      {
        "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-docker-sandboxes.json",
        "title": "Agent 37 Cloud vs Docker Sandboxes",
        "url": "https://www.anchorterminal.com/compare/agent37-vs-docker-sandboxes"
      },
      {
        "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-docker-sandboxes.json",
        "title": "DeltaBox Lite vs Docker Sandboxes",
        "url": "https://www.anchorterminal.com/compare/deltabox-lite-vs-docker-sandboxes"
      },
      {
        "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": 36,
        "docker-sandboxes": 45,
        "edge": "microsoft-execution-containers",
        "key": "reliability",
        "microsoft-execution-containers": 81,
        "name": "Reliability",
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 9,
        "docker-sandboxes": 90,
        "edge": "docker-sandboxes",
        "key": "schema",
        "microsoft-execution-containers": 81,
        "name": "Schema \u0026 documentation",
        "weight": 13
      },
      {
        "by": 9,
        "docker-sandboxes": 83,
        "edge": "docker-sandboxes",
        "key": "ergonomics",
        "microsoft-execution-containers": 74,
        "name": "Agent ergonomics",
        "weight": 13
      },
      {
        "by": 0,
        "docker-sandboxes": 69,
        "edge": "",
        "key": "security",
        "microsoft-execution-containers": 69,
        "name": "Security \u0026 auth",
        "weight": 14
      },
      {
        "by": 90,
        "docker-sandboxes": 0,
        "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": 21,
        "docker-sandboxes": 71,
        "edge": "microsoft-execution-containers",
        "key": "maintenance",
        "microsoft-execution-containers": 92,
        "name": "Maintenance \u0026 community",
        "weight": 7
      },
      {
        "by": 7,
        "docker-sandboxes": 77,
        "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 Docker Sandboxes's 62.1 (B), and leads in 4 of 7 scored categories. Docker Sandboxes leads on schema \u0026 documentation and agent ergonomics. Both do code sandboxes.",
    "tasks": null,
    "tutorials": [],
    "verdicts": {
      "docker-sandboxes": "The cloud Sandboxes API has a public OpenAPI contract, idempotency keys, etag checks and credential injection that keeps keys out of the VM. Cloud access needs a paid Docker Agentic Platform subscription that is still experimental, and the docs publish no unit prices.",
      "microsoft-execution-containers": "MXC puts nine operating-system sandbox backends behind one typed request, with network access denied by default and a JSON Schema for the stable 1.0.0 contract. Enforcement varies by backend, `isolation_session` cannot restrict networking, and enforcement fixes made since 1.0.1, one of them a documented security fix, had not reached a release by 1 November 2026."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-microsoft-execution-containers",
    "json": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-microsoft-execution-containers.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-microsoft-execution-containers.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-microsoft-execution-containers.min.md"
  },
  "markdown": "Microsoft Execution Containers scores 77.1 (BB) on agent readiness against Docker Sandboxes's 62.1 (B), and leads in 4 of 7 scored categories. Docker Sandboxes leads on schema \u0026 documentation and agent ergonomics. Both do code sandboxes.\n\n- Docker Sandboxes: grade B, 62.1/100, rank #698 of 1557. Markdown https://www.anchorterminal.com/tools/docker-sandboxes.md · JSON https://www.anchorterminal.com/api/v1/tools/docker-sandboxes.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### Docker Sandboxes (B)\n\nGood for: Running coding agents such as Claude Code or Codex in a disposable cloud VM, or the same kit locally for free.\n\nAhead on:\n- Schema \u0026 documentation, 90 against 81\n- Agent ergonomics, 83 against 74\n\nAlso in its favour:\n- No incidents deducted, where Microsoft Execution Containers loses 3 points for them\n\nWatch for: Docker Agentic Platform, needed for every cloud interface, is experimental, and no SLA was found\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 45\n- Payments \u0026 pricing, 90 against 0\n- Maintenance \u0026 community, 92 against 71\n- Transparency \u0026 trust, 84 against 77\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\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 +90\n\n- Docker Sandboxes (0): No x402, MPP or L402 (0). Compute is metered per second by size, but neither the docs, the Docker Sandboxes product page nor docker.com/pricing publishes a unit price. The plans page says usage and pricing show on the Usage \u0026 billing page after sign-in (0). Signup to Docker Agentic Platform asks for billing and payment details at checkout, with a one-time promotional credit after, so there is no card-free start for cloud sandboxes (0). A person subscribes in a browser and creates the access token (0). The free local `sbx` CLI is not the graded surface. 0+0+0+0 = 0.\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 +36\n\n- Docker Sandboxes (45): Hosted lines, for the cloud Sandboxes API. dockerstatus.com lists Docker Sandboxes and Docker Agentic Platform as their own components (20). Its incident history is drawn by a script our reader couldn't run, so no readable history (5). Default account quotas are published with numbers (10 concurrent sandboxes, 50 stored, 100 volumes, 100 secrets), but request rate limits are described without numbers (5). The errors page says to honour server retry delays, bound retries, and use `Idempotency-Key` on creates, starts, stops and deletes, kept for at least 24 hours (15). No SLA found in the docs (0). Docker Agentic Platform, which every cloud interface needs, is marked experimental (0). 20+5+5+15+0+0 = 45.\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### Maintenance \u0026 community: Microsoft Execution Containers +21\n\n- Docker Sandboxes (71): `sbx` 0.54.0 on 16 November 2026, per the dated release notes (30). Stable releases 0.51.0 on 3 November, 0.53.0 on 11 November and 0.54.0 on 16 November, with nightly builds tagged daily in docker/sbx-releases (20). Closed service with dated release notes and GitHub issues on docker/sbx-releases as the feedback channel. Issue response times could not be read (8). One official SDK, `@docker/sandboxes` for TypeScript, plus the CLI (10). Source and CI are not public, so package health is unchecked (3). 30+20+8+10+3 = 71.\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### Schema \u0026 documentation: Docker Sandboxes +9\n\n- Docker Sandboxes (90): An OpenAPI 3.2 document for the Sandboxes API with 42 paths and 58 operations, each with a description, in the docs repository and linked from the API reference (25). The docs build emits llms.txt, llms-full.txt and a Markdown copy of every page, per the repository's Hugo configuration (10). Operation descriptions are short and generated in form (\"List lists directory entries by path ascending\"), and the concepts and cookbook pages explain when to use kits, images, snapshots and volumes (12). Typed inputs with 95 enums, required fields and `additionalProperties` constraints (13). 36 cookbook recipes in TypeScript and an errors page with a code table (15). Paths are versioned under `/v1`, and dated release notes cover `sbx` and the Agentic Platform (15). 25+10+12+13+15+15 = 90.\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### Agent ergonomics: Docker Sandboxes +9\n\n- Docker Sandboxes (83): Lists take `pageSize` and `pageToken`, and filters and ordering are given per operation, so responses can be kept small (15). Pagination and a `filter` parameter of exact-match terms on list operations (18). Errors carry a stable `code`, a message and typed `google.rpc.ErrorInfo` details, with a documented action for each of eight codes (20). `Idempotency-Key` on mutations, `If-Match` etags on updates and deletes, and a documented recovery path for lost responses and failed waits (20). Kit launch helpers default to the `small` size, but the SDK is TypeScript only, with the `sbx` CLI and plain REST beside it (10). 15+18+20+20+10 = 83.\n- Microsoft Execution Containers (74): One request type with `command` as the only required field, and `run` returns stdout, stderr, the exit code, a timeout flag and warnings. We found no documented cap on captured output, and the npm package is a 37.7 MB tarball (18 of 25). `spawn` streams output and `timeoutMs` bounds a run, but there is no truncation or size control on captured output (10 of 20). `MxcError` carries one of 12 codes with optional operation, native code and remediation, and a deny-and-record mode lists blocked accesses on ProcessContainer (18 of 20). `validate*` calls dry-run every lifecycle step, and lifecycle state errors are typed (`already_started`, `stale_id`). Issue #1429, open since 6 October, reports a second deprovision returning success, per the 8 October check, not re-read on 17 October. Not an MCP server, so no tool annotations apply (13 of 20). Network, filesystem and UI policy default to deny, and official SDKs exist for Node.js, .NET and Rust (15). 18+10+18+13+15 = 74.\n\n### Transparency \u0026 trust: Microsoft Execution Containers +7\n\n- Docker Sandboxes (77): Closed software. The release repository's licence reserves all rights, and Docker's Subscription Service Agreement (26 August 2026) names Agentic Platform Services and Sandboxes (15). The privacy policy names the Agentic Platform and cloud sandboxes and says they're hosted in the United States, and the Agentic Platform FAQ gives retention for service logs (31 days), raw telemetry (12 months) and snapshots (seven days of non-use). The DPA wasn't read (20). Release notes call out breaking changes and deprecations by version and date, such as `sbx ports`, and the Agentic Platform docs warn that behaviour may change while it is experimental (10). CLI telemetry is disclosed with two opt-outs, and the hosting location is stated. No sub-processor list for cloud sandboxes was found (12). 15+20+10+12 = 57.\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## Score by category\n\n| Category | Weight | Docker Sandboxes | Microsoft Execution Containers | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 45 | 81 | Microsoft Execution Containers +36 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% | 90 | 81 | Docker Sandboxes +9 |\n| Agent ergonomics | 13% | 83 | 74 | Docker Sandboxes +9 |\n| Security \u0026 auth | 14% | 69 | 69 | even |\n| Payments \u0026 pricing | 10% | 0 | 90 | Microsoft Execution Containers +90 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% | 71 | 92 | Microsoft Execution Containers +21 |\n| Transparency \u0026 trust | 7% | 77 | 84 | Microsoft Execution Containers +7 |\n| Negative events | ≤15 | 0 | -3 | |\n| **Total** | | **62.1 · B** | **77.1 · BB** | |\n\n## Facts side by side\n\n| Fact | Docker Sandboxes | Microsoft Execution Containers |\n| --- | --- | --- |\n| Kind | HTTP API | SDK + MCP |\n| Vendor | Docker | Microsoft |\n| Hosted endpoint | no (local only) | 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. The `sbx` binaries in docker/sbx-releases are under a licence that reserves all rights to Docker Inc., and cloud sandboxes run under a Docker Agentic Platform subscription | MIT |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | no |\n| Last release | 2026-11-16 | 2026-10-17 |\n| Terms last updated | 2026-08-26 | no document linked |\n| Privacy policy last updated | 2026-08-26 | couldn't be read |\n| Customer content may train models | not found in the text | not read yet |\n| Terms restrict automated access | yes | not read yet |\n| Terms restrict benchmarking | yes | not read yet |\n| Terms or service can change without notice | not found in the text | not read yet |\n| Arbitration or class-action waiver | yes | not read yet |\n| Popularity | 527 stars | 1.5k stars, 472k npm/wk |\n| Agent reviews | none | 3/5 (4) |\n\n## How the scores have moved\n\n### Docker Sandboxes\n\n- +4.7 on 18 November 2026 (C to B): terms, new evidence\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**Docker Sandboxes.** The cloud Sandboxes API has a public OpenAPI contract, idempotency keys, etag checks and credential injection that keeps keys out of the VM. Cloud access needs a paid Docker Agentic Platform subscription that is still experimental, and the docs publish no unit prices.\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### Docker Sandboxes\n\n1. Create the Docker personal access token with Allow Cloud Sandboxes access. Registry permissions alone don't grant the `sandbox:use` scope\n2. Send the same `Idempotency-Key` when you retry a create, so a lost response doesn't start a second sandbox\n3. Pass the etag from your latest read in `If-Match`. A stale etag returns 412 and a missing one 428\n4. Set `--ttl` and `--on-timeout` at creation. The default deletes sandboxes that can't be resumed after one hour\n5. Set the account network policy to deny-all and add allow rules per sandbox, since allow-all lets the sandbox reach any host\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, Docker Sandboxes or Microsoft Execution Containers?\n\nMicrosoft Execution Containers scores 77.1 (BB) on agent readiness against Docker Sandboxes's 62.1 (B), and leads in 4 of 7 scored categories. Docker Sandboxes leads on schema \u0026 documentation and agent ergonomics.\n\n### Can an agent call Docker Sandboxes and Microsoft Execution Containers without installing anything?\n\nNo hosted endpoint is listed for Docker Sandboxes. No hosted endpoint is listed for Microsoft Execution Containers.\n\n### Are Docker Sandboxes and Microsoft Execution Containers open source?\n\nNo open-source release is listed for Docker Sandboxes. Microsoft Execution Containers is open source (MIT).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/docker-sandboxes-vs-microsoft-execution-containers.json, and with the fewest tokens: https://www.anchorterminal.com/compare/docker-sandboxes-vs-microsoft-execution-containers.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"docker-sandboxes\", \"b\": \"microsoft-execution-containers\"}`. From a terminal: `anchor compare docker-sandboxes microsoft-execution-containers`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/docker-sandboxes.json and https://www.anchorterminal.com/api/v1/tools/microsoft-execution-containers.json\n\n## Other comparisons with Docker Sandboxes or Microsoft Execution Containers\n\n- [Amazon Bedrock AgentCore Code Interpreter vs Docker Sandboxes](https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-docker-sandboxes.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 Docker Sandboxes](https://www.anchorterminal.com/compare/blaxel-sandboxes-vs-docker-sandboxes.md)\n- [Blaxel Sandboxes vs Microsoft Execution Containers](https://www.anchorterminal.com/compare/blaxel-sandboxes-vs-microsoft-execution-containers.md)\n- [boat vs Docker Sandboxes](https://www.anchorterminal.com/compare/boat-vs-docker-sandboxes.md)\n- [boat vs Microsoft Execution Containers](https://www.anchorterminal.com/compare/boat-vs-microsoft-execution-containers.md)\n- [Celesto (formerly SmolVM) vs Docker Sandboxes](https://www.anchorterminal.com/compare/celesto-vs-docker-sandboxes.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 Docker Sandboxes](https://www.anchorterminal.com/compare/cloudflare-sandbox-sdk-vs-docker-sandboxes.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 Docker Sandboxes](https://www.anchorterminal.com/compare/daytona-vs-docker-sandboxes.md)\n- [Daytona vs Microsoft Execution Containers](https://www.anchorterminal.com/compare/daytona-vs-microsoft-execution-containers.md)\n- [Deno Sandbox vs Docker Sandboxes](https://www.anchorterminal.com/compare/deno-sandbox-vs-docker-sandboxes.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 Microsoft Execution Containers](https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-microsoft-execution-containers.md)\n- [Docker Sandboxes vs E2B](https://www.anchorterminal.com/compare/docker-sandboxes-vs-e2b.md)\n- [Docker Sandboxes vs Freestyle](https://www.anchorterminal.com/compare/docker-sandboxes-vs-freestyle.md)\n- [Docker Sandboxes vs InstaVM](https://www.anchorterminal.com/compare/docker-sandboxes-vs-instavm.md)\n- [Docker Sandboxes vs Maritime](https://www.anchorterminal.com/compare/docker-sandboxes-vs-maritime.md)\n- [Docker Sandboxes vs Modal Sandboxes](https://www.anchorterminal.com/compare/docker-sandboxes-vs-modal-sandboxes.md)\n- [Docker Sandboxes vs Morph Cloud](https://www.anchorterminal.com/compare/docker-sandboxes-vs-morph-cloud.md)\n- [Docker Sandboxes vs Offscreen](https://www.anchorterminal.com/compare/docker-sandboxes-vs-offscreen.md)\n- [Docker Sandboxes vs SPACE](https://www.anchorterminal.com/compare/docker-sandboxes-vs-perplexity-space.md)\n- [Docker Sandboxes vs Render Sandboxes](https://www.anchorterminal.com/compare/docker-sandboxes-vs-render-sandboxes.md)\n- [Docker Sandboxes vs Runloop Devboxes](https://www.anchorterminal.com/compare/docker-sandboxes-vs-runloop.md)\n- [Docker Sandboxes vs Sandbox0](https://www.anchorterminal.com/compare/docker-sandboxes-vs-sandbox0.md)\n- [Docker Sandboxes vs Sprites](https://www.anchorterminal.com/compare/docker-sandboxes-vs-sprites.md)\n- [Docker Sandboxes vs Together Code Sandbox](https://www.anchorterminal.com/compare/docker-sandboxes-vs-together-code-sandbox.md)\n- [Docker Sandboxes vs Vercel Sandbox](https://www.anchorterminal.com/compare/docker-sandboxes-vs-vercel-sandbox.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 Docker Sandboxes](https://www.anchorterminal.com/compare/agent37-vs-docker-sandboxes.md)\n- [Agent 37 Cloud vs Microsoft Execution Containers](https://www.anchorterminal.com/compare/agent37-vs-microsoft-execution-containers.md)\n- [DeltaBox Lite vs Docker Sandboxes](https://www.anchorterminal.com/compare/deltabox-lite-vs-docker-sandboxes.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": "Docker Sandboxes vs Microsoft Execution Containers",
        "url": ""
      }
    ],
    "description": "Microsoft Execution Containers scores 77.1 (BB) to Docker Sandboxes's 62.1 (B) for code sandboxes. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "Docker Sandboxes B 62.1",
      "Microsoft Execution Containers BB 77.1",
      "scores"
    ],
    "h1": "Docker Sandboxes vs Microsoft Execution Containers",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/compare/docker-sandboxes-vs-microsoft-execution-containers",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Docker Sandboxes vs Microsoft Execution Containers (2026)",
    "toc": null,
    "updated": "2026-11-18",
    "url": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-microsoft-execution-containers"
  },
  "tokens": {
    "markdown": 6300,
    "slim": 1230
  },
  "version": 1
}
