{
  "data": {
    "a": {
      "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"
      }
    },
    "answer": "Microsoft Execution Containers scores 77.1 (BB) on agent readiness against Render Sandboxes's 67.5 (B), and leads in every scored category.",
    "b": {
      "slug": "render-sandboxes",
      "name": "Render Sandboxes",
      "vendor": "Render Services, Inc.",
      "vendorUrl": "https://render.com/sandboxes",
      "company": "render.com",
      "kind": "sdk",
      "category": "code-sandboxes",
      "summary": "Render Sandboxes runs isolated Linux environments in Firecracker microVMs for AI agents and untrusted code, created and controlled through the Render CLI and the TypeScript and Python SDKs. It is in public beta, in the Oregon region.",
      "url": "https://www.anchorterminal.com/tools/render-sandboxes",
      "markdownUrl": "https://www.anchorterminal.com/tools/render-sandboxes.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/render-sandboxes.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/render-sandboxes.json",
      "dns": "render-sandboxes.grade.anchorterminal.com",
      "repo": "https://github.com/render-oss/sdk",
      "license": "The service is proprietary under Render's terms. The SDK is MIT (TypeScript `@renderinc/sdk`) and Apache-2.0 (Python `render`)",
      "transports": [
        "http"
      ],
      "packages": [
        {
          "registry": "npm",
          "name": "@renderinc/sdk"
        },
        {
          "registry": "pypi",
          "name": "render"
        }
      ],
      "auth": "api-key",
      "authNotes": "A Render API key (`rnd_...`) created by a person in the dashboard's Account Settings, sent with the workspace ID (`RENDER_WORKSPACE_ID`). The key reaches every workspace its owner belongs to. Scoped API keys are listed as a beta limitation, not yet generally available. Rate limits apply per user across all of that user's keys.",
      "pricing": "usage",
      "pricingNotes": "$0.12 per CPU-hour of CPU used, plus $0.019 per GB-hour of provisioned memory, billed per second and not while suspended. Four plans from `1c-2g` ($0.038 an hour of memory) to `8c-16g`. No free sandbox allowance was found. Hobby workspaces get 100 concurrent sandboxes a group, Pro 1,000.",
      "priceSummary": "$0.12 / vCPU-hr",
      "where": "local",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the sandboxes documentation bundle, the limits and pricing page or the SDK source (checked 2026-11-18). Billing is through a Render workspace.",
        "endpoints": []
      },
      "toolCount": null,
      "popularity": {
        "githubStars": 27,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-11-18"
      },
      "docsUrl": "https://render.com/docs/sandboxes",
      "llmsTxt": "https://render.com/llms.txt",
      "capabilities": [
        "sandbox.code",
        "sandbox.fs",
        "sandbox.persist"
      ],
      "tags": [
        "hosted",
        "usage",
        "beta",
        "microvm",
        "typescript",
        "python",
        "cli",
        "llms-txt",
        "status-page",
        "soc2"
      ],
      "lastRelease": "2026-11-16",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 67.5,
        "grade": "B",
        "agentReady": false,
        "rank": 441,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 12,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 73,
          "maintenance": 85,
          "payments": 30,
          "reliability": 68,
          "schema": 79,
          "security": 63,
          "transparency": 80
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-18"
        },
        "negative": 0,
        "verdict": "Render Sandboxes has per-operation rate limits, per-second prices and typed SDKs in three languages, with sandboxes that suspend when idle and resume from snapshots. It is a public beta in one region, with no public REST API, no idempotency on create and API keys that reach every workspace.",
        "bestFor": "Teams already on Render that want agent sandboxes beside their services, or anyone who needs long-running sandboxes with idle suspension and process snapshots.",
        "strengths": [
          "Prices published per CPU-hour, minute and second, with CPU billed on use and nothing billed while suspended",
          "Rate limits published per operation, and per-group concurrency caps of 100 (Hobby) or 1,000 (Pro)",
          "Typed SDKs in TypeScript, Python and Go, with 18 named error types and a dated semver changelog",
          "Filesystem and process snapshots, idle suspension and runtime timeouts up to 30 days or none",
          "SOC 2 Type 2, ISO 27001, a HackerOne programme and a valid security.txt"
        ],
        "weaknesses": [
          "Public beta since 4 November 2026, with one region (Oregon) and no SLA outside Enterprise",
          "No public REST API or OpenAPI document. The CLI and SDKs are the only documented interfaces",
          "API keys reach every workspace of their owner, and scoped keys are not yet generally available",
          "Outbound network access is open by default, and credential brokering is alpha",
          "No free sandbox allowance, and no idempotency key for creating sandboxes"
        ],
        "agentNotes": [
          "Set `timeoutSeconds` when you create a sandbox. A disabled timeout keeps the sandbox, and its billing, running until you terminate it",
          "Pass `networkPolicy` with an allowlist or deny-all at creation, since the default allows outbound traffic to any destination",
          "Check the exit event's `exit_code` after `exec`. A nonzero exit code does not raise an error in the SDK",
          "If create returns 429, check whether the group is at its concurrency cap before you retry. Rate and concurrency limits share the same code",
          "Use `ttlSeconds` on snapshots with SDK 1.9.0 or later. The `expiresAt` option was removed in 1.9.0"
        ],
        "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": 67.5
          }
        ],
        "editorialScores": {
          "ergonomics": 73,
          "maintenance": 85,
          "payments": 30,
          "reliability": 68,
          "schema": 79,
          "security": 63,
          "transparency": 63
        },
        "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",
          "oldest": "2026-11-18",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "install": "npm install @renderinc/sdk  # or pip install render, or brew install render"
      },
      "letme": {
        "capability": "https://letme.dev/sandbox.code",
        "tool": "https://letme.dev/render-sandboxes"
      },
      "sameCompany": [
        "render-mcp-server"
      ],
      "area": "agent-runtime",
      "unitPrices": [
        {
          "item": "Sandbox CPU",
          "unit": "vcpu-hour",
          "usd": 0.12,
          "note": "Billed on CPU used. Memory is extra at $0.019 per GB-hour of provisioned RAM"
        }
      ],
      "provenance": {
        "legalEntity": "Render Services, Inc.",
        "domain": "render.com",
        "domainRegistered": "1998-10-01",
        "endpointOnVendorDomain": true,
        "terms": "https://render.com/terms",
        "privacy": "https://render.com/privacy",
        "statusPage": "https://status.render.com",
        "changelog": "https://render.com/changelog",
        "securityTxt": "valid",
        "checked": "2026-11-18",
        "notes": [
          "The terms, last modified 10 July 2026, were re-read on 18 November 2026. Legal entity, address and domain date are carried from render-mcp-server (checked 8 October 2026).",
          "render.com/robots.txt allows all agents except /contact-sales, /newsletters/ and /lp/, names ClaudeBot and Claude-User, and sets `Content-Signal: ai-train=yes, search=yes, ai-input=yes`. status.render.com disallows /api/ and /embed/ only.",
          "render.com/.well-known/security.txt names security@render.com and the HackerOne programme and expires on 3 October 2027 (read 18 November 2026).",
          "status.render.com has no Sandboxes component. Its components cover the website, the Platform API, the REST API and services by region.",
          "The changelog entry for the beta is dated 11 November 2026, a week after the 4 November blog post."
        ],
        "score": 97
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/render-sandboxes.json",
      "live": {
        "slug": "render-sandboxes",
        "vendorStatus": {
          "page": "https://status.render.com",
          "indicator": "none",
          "summary": "All Systems Operational",
          "checkedAt": "2026-11-18T22:38:49.26685015Z"
        },
        "updatedAt": "2026-11-18T22:38:49.26685015Z"
      }
    },
    "edges": [
      {
        "by": 60,
        "category": "payments",
        "leads": "microsoft-execution-containers",
        "name": "Payments \u0026 pricing",
        "reasons": {
          "a": "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.",
          "b": "No x402, MPP or L402 (0). Per-unit prices published without login, $0.12 per CPU-hour used and $0.019 per GB-hour of memory, also given per minute and per second (30). No free sandbox allowance was found. Hobby workspaces cost $0 but sandbox compute is billed from the first second, and whether a payment method is needed first was not stated (0). A person signs up and creates the API key in the dashboard (0). 0+30+0+0 = 30."
        },
        "scores": {
          "a": 90,
          "b": 30
        }
      },
      {
        "by": 13,
        "category": "reliability",
        "leads": "microsoft-execution-containers",
        "name": "Reliability",
        "reasons": {
          "a": "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.",
          "b": "Scored on the hosted checklist, since sandboxes run on Render's infrastructure and the SDKs and CLI are clients of its API, the reading given to modal-sandboxes and vercel-sandbox. status.render.com is a Statuspage with incident history, though it has no Sandboxes component (20). Its history feed, read on 18 November 2026, has no incident naming sandboxes. Since the 4 November beta it lists API performance issues on 11 November for 18 minutes (13:17 to 13:35 UTC, dashboard and API requests) and a maintenance window announced on 10 November, with the REST API down for up to 30 minutes on 18 November. Earlier in the 90 days, builds and deploys did not start in any region on 14 October. Minor for this surface (20). Rate limits per operation with numbers, such as 100 creates and 1,000 execs a minute per user, and per-group concurrency caps (15). The docs say limits return 429, and the API schema in the SDK source documents `Retry-After` and `RateLimit-*` headers, but there is no backoff guidance in the sandbox docs and no idempotency key on create (8 of 15). The pricing page lists contractual uptime SLAs for Enterprise without publishing their terms (5 of 10). Public beta, not generally available (0). 20+20+15+8+5+0 = 68."
        },
        "scores": {
          "a": 81,
          "b": 68
        }
      },
      {
        "by": 7,
        "category": "maintenance",
        "leads": "microsoft-execution-containers",
        "name": "Maintenance \u0026 community",
        "reasons": {
          "a": "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.",
          "b": "SDK 1.9.0 on 16 November 2026 (30). Eight SDK releases in the 90 days, from 1.1.0 on 10 September to 1.9.0, five of them since 17 October (20). 118 commits since 18 October from Render staff and release bots, the last on 18 November. Two open pull requests. The issue list draws in a script and could not be read, so responsiveness is not established (10 of 25). Official SDKs in TypeScript, Python and Go, current with the docs (15). CI for both languages with pinned actions, Dependabot configured. The result of the latest run was not seen (10). 30+20+10+15+10 = 85."
        },
        "scores": {
          "a": 92,
          "b": 85
        }
      },
      {
        "by": 6,
        "category": "security",
        "leads": "microsoft-execution-containers",
        "name": "Security \u0026 auth",
        "reasons": {
          "a": "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.",
          "b": "A plain revocable Render API key that reaches every workspace its owner belongs to. Scoped keys are listed as not yet generally available (20 of 30). Network policy can be an HTTPS allowlist or deny-all, but the default allows all outbound traffic, and the CLI asks for `--confirm` before stopping a sandbox or deleting a group (10 of 20). Sandboxes run untrusted code in Firecracker microVMs. Brokered credentials that keep secrets out of the sandbox are alpha, and the agent templates warn that code in the sandbox can read its environment variables (8 of 15). Workspace audit logs on Pro and above per the pricing page. Whether they record sandbox calls was not found (7 of 15). Valid security.txt to 3 October 2027, a HackerOne disclosure programme, SOC 2 Type 2 and ISO 27001 on render.com/security. No paid bounty was established (18 of 20). 20+10+8+7+18 = 63."
        },
        "scores": {
          "a": 69,
          "b": 63
        }
      }
    ],
    "facts": [
      {
        "a": "SDK + MCP",
        "b": "SDK + MCP",
        "name": "Kind"
      },
      {
        "a": "Microsoft",
        "b": "Render Services, Inc.",
        "name": "Vendor"
      },
      {
        "a": "no (local only)",
        "b": "no (local only)",
        "name": "Hosted endpoint"
      },
      {
        "a": "",
        "b": "HTTP",
        "name": "Transports"
      },
      {
        "a": "None",
        "b": "API key",
        "name": "Auth"
      },
      {
        "a": "Free",
        "b": "Pay per use",
        "name": "Pricing"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "MIT",
        "b": "The service is proprietary under Render's terms. The SDK is MIT (TypeScript `@renderinc/sdk`) and Apache-2.0 (Python `render`)",
        "name": "Licence"
      },
      {
        "a": "yes",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "no",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "2026-10-17",
        "b": "2026-11-16",
        "name": "Last release"
      },
      {
        "a": "no document linked",
        "b": "2026-07-10",
        "name": "Terms last updated"
      },
      {
        "a": "couldn't be read",
        "b": "2026-07-10",
        "name": "Privacy policy last updated"
      },
      {
        "a": "not read yet",
        "b": "not found in the text",
        "name": "Customer content may train models"
      },
      {
        "a": "not read yet",
        "b": "not found in the text",
        "name": "Terms restrict automated access"
      },
      {
        "a": "not read yet",
        "b": "not found in the text",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "not read yet",
        "b": "yes",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "not read yet",
        "b": "yes",
        "name": "Arbitration or class-action waiver"
      },
      {
        "a": "1.5k stars, 472k npm/wk",
        "b": "27 stars",
        "name": "Popularity"
      },
      {
        "a": "3/5 (4)",
        "b": "none",
        "name": "Agent reviews"
      }
    ],
    "faq": [
      {
        "answer": "Microsoft Execution Containers scores 77.1 (BB) on agent readiness against Render Sandboxes's 67.5 (B), and leads in every scored category.",
        "question": "Which is better for AI agents, Microsoft Execution Containers or Render Sandboxes?"
      },
      {
        "answer": "Microsoft Execution Containers is open source (MIT). No open-source release is listed for Render Sandboxes.",
        "question": "Are Microsoft Execution Containers and Render Sandboxes open source?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Reliability, 81 against 68",
          "Security \u0026 auth, 69 against 63",
          "Payments \u0026 pricing, 90 against 30",
          "Maintenance \u0026 community, 92 against 85"
        ],
        "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"
      },
      {
        "aheadOn": null,
        "also": [
          "No incidents deducted, where Microsoft Execution Containers loses 3 points for them"
        ],
        "goodFor": "Teams already on Render that want agent sandboxes beside their services, or anyone who needs long-running sandboxes with idle suspension and process snapshots.",
        "slug": "render-sandboxes",
        "watchFor": "Public beta since 4 November 2026, with one region (Oregon) and no SLA outside Enterprise"
      }
    ],
    "history": {
      "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"
        }
      ],
      "render-sandboxes": null
    },
    "job": {
      "capability": "sandbox.code",
      "name": "Code sandboxes"
    },
    "others": [
      {
        "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/agentcore-code-interpreter-vs-render-sandboxes.json",
        "title": "Amazon Bedrock AgentCore Code Interpreter vs Render Sandboxes",
        "url": "https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-render-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/blaxel-sandboxes-vs-render-sandboxes.json",
        "title": "Blaxel Sandboxes vs Render Sandboxes",
        "url": "https://www.anchorterminal.com/compare/blaxel-sandboxes-vs-render-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/boat-vs-render-sandboxes.json",
        "title": "boat vs Render Sandboxes",
        "url": "https://www.anchorterminal.com/compare/boat-vs-render-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/celesto-vs-render-sandboxes.json",
        "title": "Celesto (formerly SmolVM) vs Render Sandboxes",
        "url": "https://www.anchorterminal.com/compare/celesto-vs-render-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/cloudflare-sandbox-sdk-vs-render-sandboxes.json",
        "title": "Cloudflare Sandbox SDK vs Render Sandboxes",
        "url": "https://www.anchorterminal.com/compare/cloudflare-sandbox-sdk-vs-render-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/daytona-vs-render-sandboxes.json",
        "title": "Daytona vs Render Sandboxes",
        "url": "https://www.anchorterminal.com/compare/daytona-vs-render-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/deno-sandbox-vs-render-sandboxes.json",
        "title": "Deno Sandbox vs Render Sandboxes",
        "url": "https://www.anchorterminal.com/compare/deno-sandbox-vs-render-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/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/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/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/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/e2b-vs-render-sandboxes.json",
        "title": "E2B vs Render Sandboxes",
        "url": "https://www.anchorterminal.com/compare/e2b-vs-render-sandboxes"
      },
      {
        "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/freestyle-vs-render-sandboxes.json",
        "title": "Freestyle vs Render Sandboxes",
        "url": "https://www.anchorterminal.com/compare/freestyle-vs-render-sandboxes"
      },
      {
        "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/instavm-vs-render-sandboxes.json",
        "title": "InstaVM vs Render Sandboxes",
        "url": "https://www.anchorterminal.com/compare/instavm-vs-render-sandboxes"
      },
      {
        "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/maritime-vs-render-sandboxes.json",
        "title": "Maritime vs Render Sandboxes",
        "url": "https://www.anchorterminal.com/compare/maritime-vs-render-sandboxes"
      },
      {
        "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-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/modal-sandboxes-vs-render-sandboxes.json",
        "title": "Modal Sandboxes vs Render Sandboxes",
        "url": "https://www.anchorterminal.com/compare/modal-sandboxes-vs-render-sandboxes"
      },
      {
        "json": "https://www.anchorterminal.com/compare/morph-cloud-vs-render-sandboxes.json",
        "title": "Morph Cloud vs Render Sandboxes",
        "url": "https://www.anchorterminal.com/compare/morph-cloud-vs-render-sandboxes"
      },
      {
        "json": "https://www.anchorterminal.com/compare/offscreen-vs-render-sandboxes.json",
        "title": "Offscreen vs Render Sandboxes",
        "url": "https://www.anchorterminal.com/compare/offscreen-vs-render-sandboxes"
      },
      {
        "json": "https://www.anchorterminal.com/compare/perplexity-space-vs-render-sandboxes.json",
        "title": "SPACE vs Render Sandboxes",
        "url": "https://www.anchorterminal.com/compare/perplexity-space-vs-render-sandboxes"
      },
      {
        "json": "https://www.anchorterminal.com/compare/render-sandboxes-vs-runloop.json",
        "title": "Render Sandboxes vs Runloop Devboxes",
        "url": "https://www.anchorterminal.com/compare/render-sandboxes-vs-runloop"
      },
      {
        "json": "https://www.anchorterminal.com/compare/render-sandboxes-vs-sandbox0.json",
        "title": "Render Sandboxes vs Sandbox0",
        "url": "https://www.anchorterminal.com/compare/render-sandboxes-vs-sandbox0"
      },
      {
        "json": "https://www.anchorterminal.com/compare/render-sandboxes-vs-sprites.json",
        "title": "Render Sandboxes vs Sprites",
        "url": "https://www.anchorterminal.com/compare/render-sandboxes-vs-sprites"
      },
      {
        "json": "https://www.anchorterminal.com/compare/render-sandboxes-vs-together-code-sandbox.json",
        "title": "Render Sandboxes vs Together Code Sandbox",
        "url": "https://www.anchorterminal.com/compare/render-sandboxes-vs-together-code-sandbox"
      },
      {
        "json": "https://www.anchorterminal.com/compare/render-sandboxes-vs-vercel-sandbox.json",
        "title": "Render Sandboxes vs Vercel Sandbox",
        "url": "https://www.anchorterminal.com/compare/render-sandboxes-vs-vercel-sandbox"
      },
      {
        "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/agent37-vs-render-sandboxes.json",
        "title": "Agent 37 Cloud vs Render Sandboxes",
        "url": "https://www.anchorterminal.com/compare/agent37-vs-render-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"
      },
      {
        "json": "https://www.anchorterminal.com/compare/deltabox-lite-vs-render-sandboxes.json",
        "title": "DeltaBox Lite vs Render Sandboxes",
        "url": "https://www.anchorterminal.com/compare/deltabox-lite-vs-render-sandboxes"
      }
    ],
    "panel": null,
    "scores": [
      {
        "by": 13,
        "edge": "microsoft-execution-containers",
        "key": "reliability",
        "microsoft-execution-containers": 81,
        "name": "Reliability",
        "render-sandboxes": 68,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 2,
        "edge": "microsoft-execution-containers",
        "key": "schema",
        "microsoft-execution-containers": 81,
        "name": "Schema \u0026 documentation",
        "render-sandboxes": 79,
        "weight": 13
      },
      {
        "by": 1,
        "edge": "microsoft-execution-containers",
        "key": "ergonomics",
        "microsoft-execution-containers": 74,
        "name": "Agent ergonomics",
        "render-sandboxes": 73,
        "weight": 13
      },
      {
        "by": 6,
        "edge": "microsoft-execution-containers",
        "key": "security",
        "microsoft-execution-containers": 69,
        "name": "Security \u0026 auth",
        "render-sandboxes": 63,
        "weight": 14
      },
      {
        "by": 60,
        "edge": "microsoft-execution-containers",
        "key": "payments",
        "microsoft-execution-containers": 90,
        "name": "Payments \u0026 pricing",
        "render-sandboxes": 30,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 7,
        "edge": "microsoft-execution-containers",
        "key": "maintenance",
        "microsoft-execution-containers": 92,
        "name": "Maintenance \u0026 community",
        "render-sandboxes": 85,
        "weight": 7
      },
      {
        "by": 4,
        "edge": "microsoft-execution-containers",
        "key": "transparency",
        "microsoft-execution-containers": 84,
        "name": "Transparency \u0026 trust",
        "render-sandboxes": 80,
        "weight": 7
      }
    ],
    "summary": "Microsoft Execution Containers scores 77.1 (BB) on agent readiness against Render Sandboxes's 67.5 (B), and leads in every scored category. Both do code sandboxes.",
    "tasks": null,
    "tutorials": [],
    "verdicts": {
      "microsoft-execution-containers": "MXC puts nine operating-system sandbox backends behind one typed request, with network access denied by default and a JSON Schema for the stable 1.0.0 contract. Enforcement varies by backend, `isolation_session` cannot restrict networking, and enforcement fixes made since 1.0.1, one of them a documented security fix, had not reached a release by 1 November 2026.",
      "render-sandboxes": "Render Sandboxes has per-operation rate limits, per-second prices and typed SDKs in three languages, with sandboxes that suspend when idle and resume from snapshots. It is a public beta in one region, with no public REST API, no idempotency on create and API keys that reach every workspace."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-render-sandboxes",
    "json": "https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-render-sandboxes.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-render-sandboxes.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-render-sandboxes.min.md"
  },
  "markdown": "Microsoft Execution Containers scores 77.1 (BB) on agent readiness against Render Sandboxes's 67.5 (B), and leads in every scored category. Both do code sandboxes.\n\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- Render Sandboxes: grade B, 67.5/100, rank #441 of 1557. Markdown https://www.anchorterminal.com/tools/render-sandboxes.md · JSON https://www.anchorterminal.com/api/v1/tools/render-sandboxes.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### 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 68\n- Security \u0026 auth, 69 against 63\n- Payments \u0026 pricing, 90 against 30\n- Maintenance \u0026 community, 92 against 85\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### Render Sandboxes (B)\n\nGood for: Teams already on Render that want agent sandboxes beside their services, or anyone who needs long-running sandboxes with idle suspension and process snapshots.\n\nAlso in its favour:\n- No incidents deducted, where Microsoft Execution Containers loses 3 points for them\n\nWatch for: Public beta since 4 November 2026, with one region (Oregon) and no SLA outside Enterprise\n\n\n## Why the edge\n\n### Payments \u0026 pricing: Microsoft Execution Containers +60\n\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- Render Sandboxes (30): No x402, MPP or L402 (0). Per-unit prices published without login, $0.12 per CPU-hour used and $0.019 per GB-hour of memory, also given per minute and per second (30). No free sandbox allowance was found. Hobby workspaces cost $0 but sandbox compute is billed from the first second, and whether a payment method is needed first was not stated (0). A person signs up and creates the API key in the dashboard (0). 0+30+0+0 = 30.\n\n### Reliability: Microsoft Execution Containers +13\n\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- Render Sandboxes (68): Scored on the hosted checklist, since sandboxes run on Render's infrastructure and the SDKs and CLI are clients of its API, the reading given to modal-sandboxes and vercel-sandbox. status.render.com is a Statuspage with incident history, though it has no Sandboxes component (20). Its history feed, read on 18 November 2026, has no incident naming sandboxes. Since the 4 November beta it lists API performance issues on 11 November for 18 minutes (13:17 to 13:35 UTC, dashboard and API requests) and a maintenance window announced on 10 November, with the REST API down for up to 30 minutes on 18 November. Earlier in the 90 days, builds and deploys did not start in any region on 14 October. Minor for this surface (20). Rate limits per operation with numbers, such as 100 creates and 1,000 execs a minute per user, and per-group concurrency caps (15). The docs say limits return 429, and the API schema in the SDK source documents `Retry-After` and `RateLimit-*` headers, but there is no backoff guidance in the sandbox docs and no idempotency key on create (8 of 15). The pricing page lists contractual uptime SLAs for Enterprise without publishing their terms (5 of 10). Public beta, not generally available (0). 20+20+15+8+5+0 = 68.\n\n### Maintenance \u0026 community: Microsoft Execution Containers +7\n\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- Render Sandboxes (85): SDK 1.9.0 on 16 November 2026 (30). Eight SDK releases in the 90 days, from 1.1.0 on 10 September to 1.9.0, five of them since 17 October (20). 118 commits since 18 October from Render staff and release bots, the last on 18 November. Two open pull requests. The issue list draws in a script and could not be read, so responsiveness is not established (10 of 25). Official SDKs in TypeScript, Python and Go, current with the docs (15). CI for both languages with pinned actions, Dependabot configured. The result of the latest run was not seen (10). 30+20+10+15+10 = 85.\n\n### Security \u0026 auth: Microsoft Execution Containers +6\n\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- Render Sandboxes (63): A plain revocable Render API key that reaches every workspace its owner belongs to. Scoped keys are listed as not yet generally available (20 of 30). Network policy can be an HTTPS allowlist or deny-all, but the default allows all outbound traffic, and the CLI asks for `--confirm` before stopping a sandbox or deleting a group (10 of 20). Sandboxes run untrusted code in Firecracker microVMs. Brokered credentials that keep secrets out of the sandbox are alpha, and the agent templates warn that code in the sandbox can read its environment variables (8 of 15). Workspace audit logs on Pro and above per the pricing page. Whether they record sandbox calls was not found (7 of 15). Valid security.txt to 3 October 2027, a HackerOne disclosure programme, SOC 2 Type 2 and ISO 27001 on render.com/security. No paid bounty was established (18 of 20). 20+10+8+7+18 = 63.\n\n## Score by category\n\n| Category | Weight | Microsoft Execution Containers | Render Sandboxes | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 81 | 68 | Microsoft Execution Containers +13 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% | 81 | 79 | Microsoft Execution Containers +2 |\n| Agent ergonomics | 13% | 74 | 73 | Microsoft Execution Containers +1 |\n| Security \u0026 auth | 14% | 69 | 63 | Microsoft Execution Containers +6 |\n| Payments \u0026 pricing | 10% | 90 | 30 | Microsoft Execution Containers +60 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% | 92 | 85 | Microsoft Execution Containers +7 |\n| Transparency \u0026 trust | 7% | 84 | 80 | Microsoft Execution Containers +4 |\n| Negative events | ≤15 | -3 | 0 | |\n| **Total** | | **77.1 · BB** | **67.5 · B** | |\n\n## Facts side by side\n\n| Fact | Microsoft Execution Containers | Render Sandboxes |\n| --- | --- | --- |\n| Kind | SDK + MCP | SDK + MCP |\n| Vendor | Microsoft | Render Services, Inc. |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports |  | HTTP |\n| Auth | None | API key |\n| Pricing | Free | Pay per use |\n| x402 | no | no |\n| Licence | MIT | The service is proprietary under Render's terms. The SDK is MIT (TypeScript `@renderinc/sdk`) and Apache-2.0 (Python `render`) |\n| Read-only variant documented | yes | no |\n| llms.txt | no | yes |\n| Last release | 2026-10-17 | 2026-11-16 |\n| Terms last updated | no document linked | 2026-07-10 |\n| Privacy policy last updated | couldn't be read | 2026-07-10 |\n| Customer content may train models | not read yet | not found in the text |\n| Terms restrict automated access | not read yet | not found in the text |\n| Terms restrict benchmarking | not read yet | not found in the text |\n| Terms or service can change without notice | not read yet | yes |\n| Arbitration or class-action waiver | not read yet | yes |\n| Popularity | 1.5k stars, 472k npm/wk | 27 stars |\n| Agent reviews | 3/5 (4) | none |\n\n## How the scores have moved\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### Render Sandboxes\n\nNo score change since it was listed.\n\n## Verdicts\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**Render Sandboxes.** Render Sandboxes has per-operation rate limits, per-second prices and typed SDKs in three languages, with sandboxes that suspend when idle and resume from snapshots. It is a public beta in one region, with no public REST API, no idempotency on create and API keys that reach every workspace.\n\n## Before you call either\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### Render Sandboxes\n\n1. Set `timeoutSeconds` when you create a sandbox. A disabled timeout keeps the sandbox, and its billing, running until you terminate it\n2. Pass `networkPolicy` with an allowlist or deny-all at creation, since the default allows outbound traffic to any destination\n3. Check the exit event's `exit_code` after `exec`. A nonzero exit code does not raise an error in the SDK\n4. If create returns 429, check whether the group is at its concurrency cap before you retry. Rate and concurrency limits share the same code\n5. Use `ttlSeconds` on snapshots with SDK 1.9.0 or later. The `expiresAt` option was removed in 1.9.0\n\n## Questions\n\n### Which is better for AI agents, Microsoft Execution Containers or Render Sandboxes?\n\nMicrosoft Execution Containers scores 77.1 (BB) on agent readiness against Render Sandboxes's 67.5 (B), and leads in every scored category.\n\n### Are Microsoft Execution Containers and Render Sandboxes open source?\n\nMicrosoft Execution Containers is open source (MIT). No open-source release is listed for Render Sandboxes.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-render-sandboxes.json, and with the fewest tokens: https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-render-sandboxes.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"microsoft-execution-containers\", \"b\": \"render-sandboxes\"}`. From a terminal: `anchor compare microsoft-execution-containers render-sandboxes`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/microsoft-execution-containers.json and https://www.anchorterminal.com/api/v1/tools/render-sandboxes.json\n\n## Other comparisons with Microsoft Execution Containers or Render Sandboxes\n\n- [Amazon Bedrock AgentCore Code Interpreter vs Microsoft Execution Containers](https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-microsoft-execution-containers.md)\n- [Amazon Bedrock AgentCore Code Interpreter vs Render Sandboxes](https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-render-sandboxes.md)\n- [Blaxel Sandboxes vs Microsoft Execution Containers](https://www.anchorterminal.com/compare/blaxel-sandboxes-vs-microsoft-execution-containers.md)\n- [Blaxel Sandboxes vs Render Sandboxes](https://www.anchorterminal.com/compare/blaxel-sandboxes-vs-render-sandboxes.md)\n- [boat vs Microsoft Execution Containers](https://www.anchorterminal.com/compare/boat-vs-microsoft-execution-containers.md)\n- [boat vs Render Sandboxes](https://www.anchorterminal.com/compare/boat-vs-render-sandboxes.md)\n- [Celesto (formerly SmolVM) vs Microsoft Execution Containers](https://www.anchorterminal.com/compare/celesto-vs-microsoft-execution-containers.md)\n- [Celesto (formerly SmolVM) vs Render Sandboxes](https://www.anchorterminal.com/compare/celesto-vs-render-sandboxes.md)\n- [Cloudflare Sandbox SDK vs Microsoft Execution Containers](https://www.anchorterminal.com/compare/cloudflare-sandbox-sdk-vs-microsoft-execution-containers.md)\n- [Cloudflare Sandbox SDK vs Render Sandboxes](https://www.anchorterminal.com/compare/cloudflare-sandbox-sdk-vs-render-sandboxes.md)\n- [Daytona vs Microsoft Execution Containers](https://www.anchorterminal.com/compare/daytona-vs-microsoft-execution-containers.md)\n- [Daytona vs Render Sandboxes](https://www.anchorterminal.com/compare/daytona-vs-render-sandboxes.md)\n- [Deno Sandbox vs Microsoft Execution Containers](https://www.anchorterminal.com/compare/deno-sandbox-vs-microsoft-execution-containers.md)\n- [Deno Sandbox vs Render Sandboxes](https://www.anchorterminal.com/compare/deno-sandbox-vs-render-sandboxes.md)\n- [DigitalOcean Managed Agents vs Microsoft Execution Containers](https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-microsoft-execution-containers.md)\n- [DigitalOcean Managed Agents vs Render Sandboxes](https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-render-sandboxes.md)\n- [Docker Sandboxes vs Microsoft Execution Containers](https://www.anchorterminal.com/compare/docker-sandboxes-vs-microsoft-execution-containers.md)\n- [Docker Sandboxes vs Render Sandboxes](https://www.anchorterminal.com/compare/docker-sandboxes-vs-render-sandboxes.md)\n- [E2B vs Microsoft Execution Containers](https://www.anchorterminal.com/compare/e2b-vs-microsoft-execution-containers.md)\n- [E2B vs Render Sandboxes](https://www.anchorterminal.com/compare/e2b-vs-render-sandboxes.md)\n- [Freestyle vs Microsoft Execution Containers](https://www.anchorterminal.com/compare/freestyle-vs-microsoft-execution-containers.md)\n- [Freestyle vs Render Sandboxes](https://www.anchorterminal.com/compare/freestyle-vs-render-sandboxes.md)\n- [InstaVM vs Microsoft Execution Containers](https://www.anchorterminal.com/compare/instavm-vs-microsoft-execution-containers.md)\n- [InstaVM vs Render Sandboxes](https://www.anchorterminal.com/compare/instavm-vs-render-sandboxes.md)\n- [Maritime vs Microsoft Execution Containers](https://www.anchorterminal.com/compare/maritime-vs-microsoft-execution-containers.md)\n- [Maritime vs Render Sandboxes](https://www.anchorterminal.com/compare/maritime-vs-render-sandboxes.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 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- [Modal Sandboxes vs Render Sandboxes](https://www.anchorterminal.com/compare/modal-sandboxes-vs-render-sandboxes.md)\n- [Morph Cloud vs Render Sandboxes](https://www.anchorterminal.com/compare/morph-cloud-vs-render-sandboxes.md)\n- [Offscreen vs Render Sandboxes](https://www.anchorterminal.com/compare/offscreen-vs-render-sandboxes.md)\n- [SPACE vs Render Sandboxes](https://www.anchorterminal.com/compare/perplexity-space-vs-render-sandboxes.md)\n- [Render Sandboxes vs Runloop Devboxes](https://www.anchorterminal.com/compare/render-sandboxes-vs-runloop.md)\n- [Render Sandboxes vs Sandbox0](https://www.anchorterminal.com/compare/render-sandboxes-vs-sandbox0.md)\n- [Render Sandboxes vs Sprites](https://www.anchorterminal.com/compare/render-sandboxes-vs-sprites.md)\n- [Render Sandboxes vs Together Code Sandbox](https://www.anchorterminal.com/compare/render-sandboxes-vs-together-code-sandbox.md)\n- [Render Sandboxes vs Vercel Sandbox](https://www.anchorterminal.com/compare/render-sandboxes-vs-vercel-sandbox.md)\n- [Agent 37 Cloud vs Microsoft Execution Containers](https://www.anchorterminal.com/compare/agent37-vs-microsoft-execution-containers.md)\n- [Agent 37 Cloud vs Render Sandboxes](https://www.anchorterminal.com/compare/agent37-vs-render-sandboxes.md)\n- [DeltaBox Lite vs Microsoft Execution Containers](https://www.anchorterminal.com/compare/deltabox-lite-vs-microsoft-execution-containers.md)\n- [DeltaBox Lite vs Render Sandboxes](https://www.anchorterminal.com/compare/deltabox-lite-vs-render-sandboxes.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": "Microsoft Execution Containers vs Render Sandboxes",
        "url": ""
      }
    ],
    "description": "Microsoft Execution Containers scores 77.1 (BB) to Render Sandboxes's 67.5 (B) for code sandboxes. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "Microsoft Execution Containers BB 77.1",
      "Render Sandboxes B 67.5",
      "scores"
    ],
    "h1": "Microsoft Execution Containers vs Render Sandboxes",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/compare/microsoft-execution-containers-vs-render-sandboxes",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Microsoft Execution Containers vs Render Sandboxes (2026)",
    "toc": null,
    "updated": "2026-11-18",
    "url": "https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-render-sandboxes"
  },
  "tokens": {
    "markdown": 5650,
    "slim": 1030
  },
  "version": 1
}
