{
  "data": {
    "a": {
      "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"
      }
    },
    "answer": "Vercel Sandbox scores 76.6 (BB) on agent readiness against Render Sandboxes's 67.5 (B), and leads in 4 of 7 scored categories.",
    "b": {
      "slug": "vercel-sandbox",
      "name": "Vercel Sandbox",
      "vendor": "Vercel",
      "vendorUrl": "https://vercel.com/docs/sandbox",
      "company": "vercel.com",
      "kind": "http-api",
      "category": "code-sandboxes",
      "summary": "Firecracker microVM sandboxes on Vercel, driven from the `@vercel/sandbox` JavaScript SDK, the Python `vercel` package, a CLI or the REST API.",
      "url": "https://www.anchorterminal.com/tools/vercel-sandbox",
      "markdownUrl": "https://www.anchorterminal.com/tools/vercel-sandbox.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/vercel-sandbox.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/vercel-sandbox.json",
      "dns": "vercel-sandbox.grade.anchorterminal.com",
      "repo": "https://github.com/vercel/sandbox",
      "license": "Apache-2.0",
      "transports": [
        "http"
      ],
      "remoteUrl": "https://api.vercel.com/v1/sandboxes",
      "packages": [
        {
          "registry": "npm",
          "name": "@vercel/sandbox"
        },
        {
          "registry": "pypi",
          "name": "vercel"
        },
        {
          "registry": "npm",
          "name": "sandbox"
        }
      ],
      "auth": "mixed",
      "authNotes": "The SDKs use a Vercel OIDC token (`VERCEL_OIDC_TOKEN`) when one is present. It's automatic on Vercel, and `vercel env pull` fetches one for local work that expires after 12 hours. Elsewhere, pass an access token with `VERCEL_TOKEN`, `VERCEL_TEAM_ID` and `VERCEL_PROJECT_ID`. The REST API takes the access token as a Bearer header.",
      "pricing": "freemium",
      "pricingNotes": "Hobby includes 5 hours of Active CPU, 420 GB-hours of memory, 5,000 sandbox creations, 20 GB of transfer, 15 GB of snapshot storage, 15 GB of drive storage and 30 GB each of drive reads and writes, after which creation pauses until the next cycle. Pro and Enterprise pay $0.128 an Active CPU hour, $0.0212 a GB-hour of provisioned memory, $0.60 per million creations, $0.08 a GB-month of snapshot storage, $0.05 a GB-month for drives, $0.0015 a GB of drive reads and $0.004 a GB of drive writes, at iad1 rates, with CPU, memory, transfer and drive rates varying by region. Pro usage draws first on the plan's $20 monthly credit. Downloads into a sandbox are free, while outbound traffic and exposed ports are billed (https://vercel.com/docs/sandbox/pricing, checked 2026-10-17).",
      "priceSummary": "$0.128 / vCPU-hr",
      "where": "hosted",
      "x402": {
        "level": "no",
        "endpoints": []
      },
      "toolCount": null,
      "popularity": {
        "githubStars": 168,
        "npmWeekly": 6482660,
        "pypiWeekly": 461527,
        "asOf": "2026-09-30"
      },
      "docsUrl": "https://vercel.com/docs/sandbox",
      "llmsTxt": "https://vercel.com/llms.txt",
      "openapi": "https://openapi.vercel.sh/",
      "capabilities": [
        "sandbox.code",
        "sandbox.fs",
        "sandbox.persist"
      ],
      "tags": [
        "hosted",
        "freemium",
        "free-tier",
        "typescript",
        "python",
        "llms-txt",
        "enterprise",
        "openapi"
      ],
      "lastRelease": "2026-10-28",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 76.6,
        "grade": "BB",
        "agentReady": true,
        "rank": 90,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 2,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 73,
          "maintenance": 82,
          "payments": 75,
          "reliability": 75,
          "schema": 88,
          "security": 86,
          "transparency": 78
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-01"
        },
        "negative": -3,
        "negativeNotes": [
          "April 2026. Vercel's security bulletin says an attacker took over an employee's account through a compromised third-party AI tool (Context.ai), reached internal systems and decrypted non-sensitive environment variables of a limited subset of customers, and a later review found a small number of further affected accounts. Vercel closed the incident on 16 October 2026 with all remediation complete, re-read on 1 November. @vercel/sandbox had been on npm since May 2025, and Sandbox runs under the same Vercel accounts, projects and tokens. A fixed and documented incident that reached customer secrets, about six months old, so 3 of a possible 15 is taken, the same deduction as vercel-connect. The 1 October check took none for it (https://vercel.com/kb/bulletin/vercel-april-2026-security-incident)."
        ],
        "verdict": "Active CPU billing means waiting on model responses costs only memory, and the REST API is in Vercel's public OpenAPI document. Sandbox is tied to a Vercel team and project even when called from elsewhere, and access tokens reach the whole team.",
        "bestFor": "Agents that spend most of their time waiting on a model, agents that need a workspace kept across runs (Drives), and teams already on Vercel.",
        "strengths": [
          "Active CPU billing, so waiting on model responses costs only memory",
          "Credential brokering proxy outside the sandbox that overwrites headers set by sandbox code",
          "Firecracker microVM with root access, and a firewall with deny-all, domain and CIDR rules",
          "Drives, generally available since 15 October 2026, keep files across sandboxes and can be forked for parallel workers",
          "Sandbox endpoints are in Vercel's public OpenAPI document, with paginated, filterable list calls"
        ],
        "weaknesses": [
          "Tied to a Vercel team and project even when called from elsewhere, and access tokens reach the whole team",
          "Hobby caps sessions at 45 minutes and pauses creation once the monthly allowance is spent",
          "Snapshots keep the filesystem, not memory or running processes",
          "Egress is allow-all until you set a policy",
          "No MCP server for Sandbox and no SLA found"
        ],
        "agentNotes": [
          "Call `sandbox.stop()` when the task is done. Memory bills until the session ends",
          "Use `Sandbox.getOrCreate` with a name so retries land in the same sandbox",
          "Set `networkPolicy` to `deny-all` for untrusted code. The default is allow-all",
          "Put API keys in credential brokering rules, not in the sandbox environment",
          "Calling `POST /v4/sandboxes` directly, snapshots expire after 7 days and only the latest is kept unless you set `keepLastSnapshots`. The SDK still uses v3, with 30 days"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 2,
        "avgRating": 3.5,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "BB",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 76.6
          }
        ],
        "editorialScores": {
          "ergonomics": 73,
          "maintenance": 82,
          "payments": 75,
          "reliability": 75,
          "schema": 88,
          "security": 86,
          "transparency": 57
        },
        "provenanceScore": 99,
        "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 i @vercel/sandbox  # or pip install vercel",
        "http": "curl -X POST \"https://api.vercel.com/v1/sandboxes?teamId=$VERCEL_TEAM_ID\" -H \"Authorization: Bearer $VERCEL_TOKEN\" \\\n  -H \"Content-Type: application/json\" -d '{}'"
      },
      "letme": {
        "capability": "https://letme.dev/sandbox.code",
        "tool": "https://letme.dev/vercel-sandbox"
      },
      "sameCompany": [
        "vercel-ai-gateway",
        "vercel-ai-sdk",
        "vercel-connect",
        "agent-browser"
      ],
      "area": "agent-runtime",
      "unitPrices": [
        {
          "item": "Active CPU (iad1)",
          "unit": "vcpu-hour",
          "usd": 0.128,
          "note": "Billed only while the CPU is busy. Memory extra at $0.0212 a GB-hour"
        },
        {
          "item": "Snapshot storage",
          "unit": "gb-month",
          "usd": 0.08
        },
        {
          "item": "Drive storage (iad1)",
          "unit": "gb-month",
          "usd": 0.05
        },
        {
          "item": "Drive reads (iad1)",
          "unit": "gb",
          "usd": 0.0015,
          "note": "Hobby includes 30 GB a month"
        },
        {
          "item": "Drive writes (iad1)",
          "unit": "gb",
          "usd": 0.004,
          "note": "Hobby includes 30 GB a month"
        },
        {
          "item": "Data transfer on Enterprise (iad1)",
          "unit": "gb",
          "usd": 0.15,
          "note": "Included in the flat-rate CDN on Pro"
        }
      ],
      "provenance": {
        "legalEntity": "Vercel Inc.",
        "domain": "vercel.com",
        "domainRegistered": "1999-10-04",
        "domainNote": "vercel.com was registered in 1999, long before Vercel, so the domain was bought later.",
        "endpointOnVendorDomain": true,
        "terms": "https://vercel.com/legal/terms",
        "privacy": "https://vercel.com/legal/privacy-policy",
        "statusPage": "https://www.vercel-status.com",
        "changelog": "https://vercel.com/changelog",
        "securityTxt": "valid",
        "checked": "2026-11-01",
        "notes": [
          "Terms (last updated 19 October 2026) name Vercel Inc., 440 N Barranca Ave #4133, Covina, California, read on 1 November 2026.",
          "security.txt points to HackerOne and responsible.disclosure@vercel.com and expires 2027-09-28, re-read on 1 November 2026.",
          "The status page lists Sandbox as its own component. Its history feed from 3 August to 1 November 2026 has a Sandbox API latency incident on 4 September and a 24-minute minor incident in cdg1 on 6 October.",
          "The DPA (effective 31 March 2026) names Vercel Inc., a Delaware corporation, and applies to Pro and Enterprise."
        ],
        "score": 99
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/vercel-sandbox.json",
      "live": {
        "slug": "vercel-sandbox",
        "probe": {
          "target": "https://api.vercel.com/v1/sandboxes",
          "method": "get",
          "lastAt": "2026-11-18T22:44:11.043385348Z",
          "lastOk": true,
          "lastStatus": 403,
          "lastMs": 115,
          "lastNote": "asks for credentials",
          "authRequired": true,
          "uptime24h": 100,
          "uptime30d": 99.97,
          "p50ms24h": 108,
          "p95ms24h": 236,
          "samples24h": 241,
          "samples30d": 7837,
          "days": [
            {
              "date": "2026-10-18",
              "probes": 256,
              "ok": 256
            },
            {
              "date": "2026-10-19",
              "probes": 255,
              "ok": 255
            },
            {
              "date": "2026-10-20",
              "probes": 252,
              "ok": 252
            },
            {
              "date": "2026-10-21",
              "probes": 253,
              "ok": 253
            },
            {
              "date": "2026-10-22",
              "probes": 253,
              "ok": 253
            },
            {
              "date": "2026-10-23",
              "probes": 248,
              "ok": 248
            },
            {
              "date": "2026-10-24",
              "probes": 251,
              "ok": 251
            },
            {
              "date": "2026-10-25",
              "probes": 250,
              "ok": 250
            },
            {
              "date": "2026-10-26",
              "probes": 252,
              "ok": 252
            },
            {
              "date": "2026-10-27",
              "probes": 249,
              "ok": 249
            },
            {
              "date": "2026-10-28",
              "probes": 250,
              "ok": 250
            },
            {
              "date": "2026-10-29",
              "probes": 249,
              "ok": 249
            },
            {
              "date": "2026-10-30",
              "probes": 249,
              "ok": 249
            },
            {
              "date": "2026-10-31",
              "probes": 251,
              "ok": 251
            },
            {
              "date": "2026-11-01",
              "probes": 249,
              "ok": 248
            },
            {
              "date": "2026-11-02",
              "probes": 250,
              "ok": 250
            },
            {
              "date": "2026-11-03",
              "probes": 248,
              "ok": 248
            },
            {
              "date": "2026-11-04",
              "probes": 246,
              "ok": 246
            },
            {
              "date": "2026-11-05",
              "probes": 185,
              "ok": 185
            },
            {
              "date": "2026-11-06",
              "probes": 241,
              "ok": 241
            },
            {
              "date": "2026-11-07",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-08",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-09",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-10",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-11",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-12",
              "probes": 245,
              "ok": 245
            },
            {
              "date": "2026-11-13",
              "probes": 238,
              "ok": 237
            },
            {
              "date": "2026-11-14",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-15",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-16",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-17",
              "probes": 242,
              "ok": 242
            },
            {
              "date": "2026-11-18",
              "probes": 228,
              "ok": 228
            }
          ],
          "since": "2026-10-08T00:00:00Z"
        },
        "vendorStatus": {
          "page": "https://www.vercel-status.com",
          "indicator": "minor",
          "summary": "Minor Service Outage",
          "checkedAt": "2026-11-18T22:38:59.211759738Z"
        },
        "versions": [
          {
            "registry": "github",
            "name": "vercel/sandbox",
            "version": "@vercel/sandbox-mock@4.0.0",
            "released": "2026-11-12",
            "seenAt": "2026-11-18T18:39:27.48123085Z"
          },
          {
            "registry": "npm",
            "name": "@vercel/sandbox",
            "version": "4.0.0",
            "seenAt": "2026-11-18T18:39:25.251585767Z"
          },
          {
            "registry": "npm",
            "name": "sandbox",
            "version": "4.12.0",
            "seenAt": "2026-11-18T18:39:26.33972742Z"
          },
          {
            "registry": "pypi",
            "name": "vercel",
            "version": "0.13.0",
            "released": "2026-11-13",
            "seenAt": "2026-11-18T18:39:26.069001497Z"
          }
        ],
        "githubStars": 225,
        "npmWeekly": 7873939,
        "pypiWeekly": 384694,
        "securityTxt": {
          "url": "https://vercel.com/.well-known/security.txt",
          "state": "valid",
          "expires": "2027-09-28T12:00:00.000Z",
          "checkedAt": "2026-11-18T16:31:08.733177415Z"
        },
        "llmsTxt": {
          "url": "https://vercel.com/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-11-18T16:16:41.392155504Z"
        },
        "domain": {
          "domain": "vercel.com",
          "registered": "1999-10-04",
          "source": "https://rdap.verisign.com/com/v1/domain/vercel.com",
          "checkedAt": "2026-11-15T15:15:18.264224016Z"
        },
        "pages": [
          {
            "url": "https://vercel.com/changelog",
            "kind": "changelog",
            "status": 200,
            "checkedAt": "2026-10-08T18:25:35.711588091Z",
            "changedAt": "2026-10-08T18:25:35.711588091Z",
            "fingerprint": "304566010012"
          },
          {
            "url": "https://vercel.com/docs/sandbox/pricing",
            "kind": "pricing",
            "status": 200,
            "checkedAt": "2026-11-18T21:57:40.855113403Z",
            "changedAt": "2026-11-18T21:57:40.855113403Z",
            "fingerprint": "f7d769ca2e21"
          },
          {
            "url": "https://vercel.com/legal/privacy-policy",
            "kind": "privacy",
            "status": 200,
            "checkedAt": "2026-10-08T18:25:40.648740851Z",
            "changedAt": "2026-10-06T16:13:29.92763016Z",
            "fingerprint": "7ab1f9d3393a"
          },
          {
            "url": "https://vercel.com/legal/terms",
            "kind": "terms",
            "status": 200,
            "checkedAt": "2026-10-08T18:25:41.831234474Z",
            "changedAt": "2026-10-06T16:13:31.349375221Z",
            "fingerprint": "35995712008a"
          }
        ],
        "github": {
          "repo": "vercel/sandbox",
          "checkedAt": "2026-11-16T13:24:25.142652544Z",
          "stars": 225,
          "archived": false,
          "issuesEnabled": true,
          "pushedAt": "2026-11-16T06:15:18Z",
          "openIssues": 11,
          "openPRs": 36,
          "issuesOpened90d": 15,
          "issuesClosed90d": 7,
          "prsMerged90d": 101,
          "ci": {
            "branch": "main",
            "runs": 50,
            "success": 46,
            "failure": 2,
            "other": 2,
            "latest": "success",
            "latestAt": "2026-11-13T15:21:14Z"
          },
          "replies": {
            "sampled": 25,
            "unanswered": 11,
            "medianDays": 11.5
          }
        },
        "updatedAt": "2026-11-18T22:44:11.043385348Z"
      },
      "streak": {
        "days": 41,
        "from": "2026-10-08",
        "sinceWatching": true,
        "best": 41
      }
    },
    "edges": [
      {
        "by": 45,
        "category": "payments",
        "leads": "vercel-sandbox",
        "name": "Payments \u0026 pricing",
        "reasons": {
          "a": "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.",
          "b": "No x402, MPP or L402 (0). Per-unit prices published by region, $0.128 an Active CPU hour and $0.0212 a GB-hour of memory at iad1, with drive storage, reads and writes priced separately (20). Hobby includes 5 Active CPU hours and 5,000 creations a month at no cost. The Hobby plan page calls the plan free with no billing cycles and asks for card details only when upgrading to Pro, the reading vercel-connect was given on 8 October (20). Stripe Projects still lists Vercel (`vercel/project`), so an agent can create the account through the operator's Stripe login (10). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 50 is 75."
        },
        "scores": {
          "a": 30,
          "b": 75
        }
      },
      {
        "by": 23,
        "category": "security",
        "leads": "vercel-sandbox",
        "name": "Security \u0026 auth",
        "reasons": {
          "a": "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.",
          "b": "Vercel OIDC tokens tied to one project, which `vercel env pull` hands out for 12 hours, or access tokens elsewhere. Access tokens reach a whole team rather than one sandbox (25). Each sandbox is a Firecracker microVM with its own kernel (10). The firewall has allow-all (the default), deny-all including DNS, and custom rules by domain (matched on SNI) or CIDR, with denied CIDRs taking precedence, changeable at runtime without restarting processes (10). Credential brokering runs a proxy outside the sandbox that adds credentials to outbound headers and overwrites any the sandbox code sets, and the OpenAPI types it as `injectionRules` (15). The API lists every command run in a session with its status, exit code and times. We found no team audit log entry for sandbox activity (8). Valid security.txt pointing to HackerOne and responsible.disclosure@vercel.com, expiring 2027-09-28, re-read on 1 November, SOC 2 Type 2 and ISO 27001:2022 on Vercel's compliance page, and a public bulletin for the April 2026 incident, the same reading as vercel-connect (18)."
        },
        "scores": {
          "a": 63,
          "b": 86
        }
      },
      {
        "by": 9,
        "category": "schema",
        "leads": "vercel-sandbox",
        "name": "Schema \u0026 documentation",
        "reasons": {
          "a": "No public REST API or OpenAPI document for sandboxes, and the SDK README lists the REST API as \"Soon\". The SDKs are typed and generated from Render's API schema, and the TypeScript and Python references document every method, which we count as 15 of 25 for an SDK, the reading modal-sandboxes was given (15). render.com/llms.txt, a Markdown twin of every page and a single sandboxes bundle at /docs/sandboxes/all (10). The guides say when to use idle suspension, runtime timeouts, filesystem or process snapshots and sandbox groups, and what a deleted snapshot breaks (15). Typed SDK inputs with a plan enum, a network policy type and documented bounds such as a 64-character snapshot name (12). Examples in CLI, TypeScript and both Python styles on every page, and 18 named error types with when each is thrown. No list of API error codes (14). Semver SDK changelog with dates and Render's product changelog. The 1.9.0 breaking change came in a minor version, called out in the changelog (13). 15+10+15+12+14+13 = 79.",
          "b": "Vercel's public OpenAPI 3.0.3 document, re-read on 1 November, has 27 Sandbox paths and 33 operations under `/v2/sandboxes` to `/v4/sandboxes`, covering sandboxes, sessions, commands, files, snapshots, drives and network policy. The 1 October check didn't find them (25). Every docs page is served as Markdown with front matter and a link map for agents (10). The docs explain when to use persistent or ephemeral sandboxes, drives or snapshots, and how Active CPU billing works, with worked cost examples (15). Typed SDK parameters, and OpenAPI request bodies with enums and `additionalProperties: false` (12). KB guides and examples throughout. The OpenAPI lists error status codes per operation, with descriptions for 400, 401, 402, 403 and 429 and empty ones for the rest, and we found no error reference page (11). Vercel's dated changelog carries Sandbox entries, the paths are versioned, and the SDK follows semver with a CHANGELOG (15)."
        },
        "scores": {
          "a": 79,
          "b": 88
        }
      },
      {
        "by": 7,
        "category": "reliability",
        "leads": "vercel-sandbox",
        "name": "Reliability",
        "reasons": {
          "a": "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.",
          "b": "Sandbox is its own component on www.vercel-status.com, with an incident history (20). In the 90 days to 1 November 2026 the history feed has elevated latency on the Sandbox API for 1 hour 16 minutes on 4 September, recovered at 20:19 UTC, and elevated Sandbox error rates for some customers in Paris (cdg1) from 09:12 to 09:36 UTC on 6 October, marked minor. Nothing for Sandbox since. The 23 July dashboard incident has left the window. A degradation and a short regional incident only (20). Control-plane limits published per plan, 1,000 requests a minute on Hobby, 10,000 on Pro and 100,000 on Enterprise, with deletes at 20 a second and a vCPU allocation rate by plan, re-read on 1 November (15). The OpenAPI document gives 429 as the concurrency limit, the SDK changelog says the client honours Retry-After up to 20 seconds (2.9.2), and `Sandbox.getOrCreate` with a name gives a safe retry. No backoff guidance for callers outside the SDK (10). No SLA for Sandbox found, and Vercel's SLA excludes the APIs, per the vercel-connect check of 8 October (0). GA (10)."
        },
        "scores": {
          "a": 68,
          "b": 75
        }
      }
    ],
    "facts": [
      {
        "a": "SDK + MCP",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "Render Services, Inc.",
        "b": "Vercel",
        "name": "Vendor"
      },
      {
        "a": "no (local only)",
        "b": "https://api.vercel.com/v1/sandboxes",
        "name": "Hosted endpoint"
      },
      {
        "a": "HTTP",
        "b": "HTTP",
        "name": "Transports"
      },
      {
        "a": "API key",
        "b": "OAuth or key",
        "name": "Auth"
      },
      {
        "a": "Pay per use",
        "b": "Freemium",
        "name": "Pricing"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "The service is proprietary under Render's terms. The SDK is MIT (TypeScript `@renderinc/sdk`) and Apache-2.0 (Python `render`)",
        "b": "Apache-2.0",
        "name": "Licence"
      },
      {
        "a": "no",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "2026-11-16",
        "b": "2026-10-28",
        "name": "Last release"
      },
      {
        "a": "2026-07-10",
        "b": "2026-06-01",
        "name": "Terms last updated"
      },
      {
        "a": "2026-07-10",
        "b": "2026-06-01",
        "name": "Privacy policy last updated"
      },
      {
        "a": "not found in the text",
        "b": "yes, with an opt-out",
        "name": "Customer content may train models"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Terms restrict automated access"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "yes",
        "b": "not found in the text",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "Arbitration or class-action waiver"
      },
      {
        "a": "27 stars",
        "b": "168 stars, 6.5M npm/wk, 462k PyPI/wk",
        "name": "Popularity"
      },
      {
        "a": "none",
        "b": "3.5/5 (2)",
        "name": "Agent reviews"
      }
    ],
    "faq": [
      {
        "answer": "Vercel Sandbox scores 76.6 (BB) on agent readiness against Render Sandboxes's 67.5 (B), and leads in 4 of 7 scored categories.",
        "question": "Which is better for AI agents, Render Sandboxes or Vercel Sandbox?"
      },
      {
        "answer": "No hosted endpoint is listed for Render Sandboxes. Vercel Sandbox has a hosted endpoint at https://api.vercel.com/v1/sandboxes.",
        "question": "Can an agent call Render Sandboxes and Vercel Sandbox without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": null,
        "also": [
          "No incidents deducted, where Vercel Sandbox 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"
      },
      {
        "aheadOn": [
          "Reliability, 75 against 68",
          "Schema \u0026 documentation, 88 against 79",
          "Security \u0026 auth, 86 against 63",
          "Payments \u0026 pricing, 75 against 30"
        ],
        "also": [
          "Agent-ready, a grade of BB or better",
          "A hosted endpoint, with nothing to install"
        ],
        "goodFor": "Agents that spend most of their time waiting on a model, agents that need a workspace kept across runs (Drives), and teams already on Vercel.",
        "slug": "vercel-sandbox",
        "watchFor": "Tied to a Vercel team and project even when called from elsewhere, and access tokens reach the whole team"
      }
    ],
    "history": {
      "render-sandboxes": null,
      "vercel-sandbox": [
        {
          "causes": [
            "method"
          ],
          "date": "2026-11-13",
          "delta": 3.1,
          "from": 73.5,
          "fromGrade": "BB",
          "to": 76.6,
          "toGrade": "BB"
        },
        {
          "causes": [
            "evidence",
            "correction",
            "event"
          ],
          "date": "2026-10-17",
          "delta": 3.9,
          "from": 69.6,
          "fromGrade": "B",
          "to": 73.5,
          "toGrade": "BB"
        }
      ]
    },
    "job": {
      "capability": "sandbox.code",
      "name": "Code sandboxes"
    },
    "others": [
      {
        "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/agentcore-code-interpreter-vs-vercel-sandbox.json",
        "title": "Amazon Bedrock AgentCore Code Interpreter vs Vercel Sandbox",
        "url": "https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-vercel-sandbox"
      },
      {
        "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/blaxel-sandboxes-vs-vercel-sandbox.json",
        "title": "Blaxel Sandboxes vs Vercel Sandbox",
        "url": "https://www.anchorterminal.com/compare/blaxel-sandboxes-vs-vercel-sandbox"
      },
      {
        "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/boat-vs-vercel-sandbox.json",
        "title": "boat vs Vercel Sandbox",
        "url": "https://www.anchorterminal.com/compare/boat-vs-vercel-sandbox"
      },
      {
        "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/celesto-vs-vercel-sandbox.json",
        "title": "Celesto (formerly SmolVM) vs Vercel Sandbox",
        "url": "https://www.anchorterminal.com/compare/celesto-vs-vercel-sandbox"
      },
      {
        "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/cloudflare-sandbox-sdk-vs-vercel-sandbox.json",
        "title": "Cloudflare Sandbox SDK vs Vercel Sandbox",
        "url": "https://www.anchorterminal.com/compare/cloudflare-sandbox-sdk-vs-vercel-sandbox"
      },
      {
        "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/daytona-vs-vercel-sandbox.json",
        "title": "Daytona vs Vercel Sandbox",
        "url": "https://www.anchorterminal.com/compare/daytona-vs-vercel-sandbox"
      },
      {
        "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/deno-sandbox-vs-vercel-sandbox.json",
        "title": "Deno Sandbox vs Vercel Sandbox",
        "url": "https://www.anchorterminal.com/compare/deno-sandbox-vs-vercel-sandbox"
      },
      {
        "json": "https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-render-sandboxes.json",
        "title": "DigitalOcean Managed Agents vs Render Sandboxes",
        "url": "https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-render-sandboxes"
      },
      {
        "json": "https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-vercel-sandbox.json",
        "title": "DigitalOcean Managed Agents vs Vercel Sandbox",
        "url": "https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-vercel-sandbox"
      },
      {
        "json": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-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-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-render-sandboxes.json",
        "title": "E2B vs Render Sandboxes",
        "url": "https://www.anchorterminal.com/compare/e2b-vs-render-sandboxes"
      },
      {
        "json": "https://www.anchorterminal.com/compare/e2b-vs-vercel-sandbox.json",
        "title": "E2B vs Vercel Sandbox",
        "url": "https://www.anchorterminal.com/compare/e2b-vs-vercel-sandbox"
      },
      {
        "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/freestyle-vs-vercel-sandbox.json",
        "title": "Freestyle vs Vercel Sandbox",
        "url": "https://www.anchorterminal.com/compare/freestyle-vs-vercel-sandbox"
      },
      {
        "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/instavm-vs-vercel-sandbox.json",
        "title": "InstaVM vs Vercel Sandbox",
        "url": "https://www.anchorterminal.com/compare/instavm-vs-vercel-sandbox"
      },
      {
        "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/maritime-vs-vercel-sandbox.json",
        "title": "Maritime vs Vercel Sandbox",
        "url": "https://www.anchorterminal.com/compare/maritime-vs-vercel-sandbox"
      },
      {
        "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-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/modal-sandboxes-vs-vercel-sandbox.json",
        "title": "Modal Sandboxes vs Vercel Sandbox",
        "url": "https://www.anchorterminal.com/compare/modal-sandboxes-vs-vercel-sandbox"
      },
      {
        "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/morph-cloud-vs-vercel-sandbox.json",
        "title": "Morph Cloud vs Vercel Sandbox",
        "url": "https://www.anchorterminal.com/compare/morph-cloud-vs-vercel-sandbox"
      },
      {
        "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/offscreen-vs-vercel-sandbox.json",
        "title": "Offscreen vs Vercel Sandbox",
        "url": "https://www.anchorterminal.com/compare/offscreen-vs-vercel-sandbox"
      },
      {
        "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/perplexity-space-vs-vercel-sandbox.json",
        "title": "SPACE vs Vercel Sandbox",
        "url": "https://www.anchorterminal.com/compare/perplexity-space-vs-vercel-sandbox"
      },
      {
        "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/runloop-vs-vercel-sandbox.json",
        "title": "Runloop Devboxes vs Vercel Sandbox",
        "url": "https://www.anchorterminal.com/compare/runloop-vs-vercel-sandbox"
      },
      {
        "json": "https://www.anchorterminal.com/compare/sandbox0-vs-vercel-sandbox.json",
        "title": "Sandbox0 vs Vercel Sandbox",
        "url": "https://www.anchorterminal.com/compare/sandbox0-vs-vercel-sandbox"
      },
      {
        "json": "https://www.anchorterminal.com/compare/sprites-vs-vercel-sandbox.json",
        "title": "Sprites vs Vercel Sandbox",
        "url": "https://www.anchorterminal.com/compare/sprites-vs-vercel-sandbox"
      },
      {
        "json": "https://www.anchorterminal.com/compare/together-code-sandbox-vs-vercel-sandbox.json",
        "title": "Together Code Sandbox vs Vercel Sandbox",
        "url": "https://www.anchorterminal.com/compare/together-code-sandbox-vs-vercel-sandbox"
      },
      {
        "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/agent37-vs-vercel-sandbox.json",
        "title": "Agent 37 Cloud vs Vercel Sandbox",
        "url": "https://www.anchorterminal.com/compare/agent37-vs-vercel-sandbox"
      },
      {
        "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"
      },
      {
        "json": "https://www.anchorterminal.com/compare/deltabox-lite-vs-vercel-sandbox.json",
        "title": "DeltaBox Lite vs Vercel Sandbox",
        "url": "https://www.anchorterminal.com/compare/deltabox-lite-vs-vercel-sandbox"
      }
    ],
    "panel": null,
    "scores": [
      {
        "by": 7,
        "edge": "vercel-sandbox",
        "key": "reliability",
        "name": "Reliability",
        "render-sandboxes": 68,
        "vercel-sandbox": 75,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 9,
        "edge": "vercel-sandbox",
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "render-sandboxes": 79,
        "vercel-sandbox": 88,
        "weight": 13
      },
      {
        "by": 0,
        "edge": "",
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "render-sandboxes": 73,
        "vercel-sandbox": 73,
        "weight": 13
      },
      {
        "by": 23,
        "edge": "vercel-sandbox",
        "key": "security",
        "name": "Security \u0026 auth",
        "render-sandboxes": 63,
        "vercel-sandbox": 86,
        "weight": 14
      },
      {
        "by": 45,
        "edge": "vercel-sandbox",
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "render-sandboxes": 30,
        "vercel-sandbox": 75,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 3,
        "edge": "render-sandboxes",
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "render-sandboxes": 85,
        "vercel-sandbox": 82,
        "weight": 7
      },
      {
        "by": 2,
        "edge": "render-sandboxes",
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "render-sandboxes": 80,
        "vercel-sandbox": 78,
        "weight": 7
      }
    ],
    "summary": "Vercel Sandbox scores 76.6 (BB) on agent readiness against Render Sandboxes's 67.5 (B), and leads in 4 of 7 scored categories. Both do code sandboxes.",
    "tasks": null,
    "tutorials": [],
    "verdicts": {
      "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.",
      "vercel-sandbox": "Active CPU billing means waiting on model responses costs only memory, and the REST API is in Vercel's public OpenAPI document. Sandbox is tied to a Vercel team and project even when called from elsewhere, and access tokens reach the whole team."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/render-sandboxes-vs-vercel-sandbox",
    "json": "https://www.anchorterminal.com/compare/render-sandboxes-vs-vercel-sandbox.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/render-sandboxes-vs-vercel-sandbox.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/render-sandboxes-vs-vercel-sandbox.min.md"
  },
  "markdown": "Vercel Sandbox scores 76.6 (BB) on agent readiness against Render Sandboxes's 67.5 (B), and leads in 4 of 7 scored categories. Both do code sandboxes.\n\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- Vercel Sandbox: grade BB, 76.6/100, rank #90 of 1557. Markdown https://www.anchorterminal.com/tools/vercel-sandbox.md · JSON https://www.anchorterminal.com/api/v1/tools/vercel-sandbox.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### 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 Vercel Sandbox 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### Vercel Sandbox (BB)\n\nGood for: Agents that spend most of their time waiting on a model, agents that need a workspace kept across runs (Drives), and teams already on Vercel.\n\nAhead on:\n- Reliability, 75 against 68\n- Schema \u0026 documentation, 88 against 79\n- Security \u0026 auth, 86 against 63\n- Payments \u0026 pricing, 75 against 30\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- A hosted endpoint, with nothing to install\n\nWatch for: Tied to a Vercel team and project even when called from elsewhere, and access tokens reach the whole team\n\n\n## Why the edge\n\n### Payments \u0026 pricing: Vercel Sandbox +45\n\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- Vercel Sandbox (75): No x402, MPP or L402 (0). Per-unit prices published by region, $0.128 an Active CPU hour and $0.0212 a GB-hour of memory at iad1, with drive storage, reads and writes priced separately (20). Hobby includes 5 Active CPU hours and 5,000 creations a month at no cost. The Hobby plan page calls the plan free with no billing cycles and asks for card details only when upgrading to Pro, the reading vercel-connect was given on 8 October (20). Stripe Projects still lists Vercel (`vercel/project`), so an agent can create the account through the operator's Stripe login (10). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 50 is 75.\n\n### Security \u0026 auth: Vercel Sandbox +23\n\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- Vercel Sandbox (86): Vercel OIDC tokens tied to one project, which `vercel env pull` hands out for 12 hours, or access tokens elsewhere. Access tokens reach a whole team rather than one sandbox (25). Each sandbox is a Firecracker microVM with its own kernel (10). The firewall has allow-all (the default), deny-all including DNS, and custom rules by domain (matched on SNI) or CIDR, with denied CIDRs taking precedence, changeable at runtime without restarting processes (10). Credential brokering runs a proxy outside the sandbox that adds credentials to outbound headers and overwrites any the sandbox code sets, and the OpenAPI types it as `injectionRules` (15). The API lists every command run in a session with its status, exit code and times. We found no team audit log entry for sandbox activity (8). Valid security.txt pointing to HackerOne and responsible.disclosure@vercel.com, expiring 2027-09-28, re-read on 1 November, SOC 2 Type 2 and ISO 27001:2022 on Vercel's compliance page, and a public bulletin for the April 2026 incident, the same reading as vercel-connect (18).\n\n### Schema \u0026 documentation: Vercel Sandbox +9\n\n- Render Sandboxes (79): No public REST API or OpenAPI document for sandboxes, and the SDK README lists the REST API as \"Soon\". The SDKs are typed and generated from Render's API schema, and the TypeScript and Python references document every method, which we count as 15 of 25 for an SDK, the reading modal-sandboxes was given (15). render.com/llms.txt, a Markdown twin of every page and a single sandboxes bundle at /docs/sandboxes/all (10). The guides say when to use idle suspension, runtime timeouts, filesystem or process snapshots and sandbox groups, and what a deleted snapshot breaks (15). Typed SDK inputs with a plan enum, a network policy type and documented bounds such as a 64-character snapshot name (12). Examples in CLI, TypeScript and both Python styles on every page, and 18 named error types with when each is thrown. No list of API error codes (14). Semver SDK changelog with dates and Render's product changelog. The 1.9.0 breaking change came in a minor version, called out in the changelog (13). 15+10+15+12+14+13 = 79.\n- Vercel Sandbox (88): Vercel's public OpenAPI 3.0.3 document, re-read on 1 November, has 27 Sandbox paths and 33 operations under `/v2/sandboxes` to `/v4/sandboxes`, covering sandboxes, sessions, commands, files, snapshots, drives and network policy. The 1 October check didn't find them (25). Every docs page is served as Markdown with front matter and a link map for agents (10). The docs explain when to use persistent or ephemeral sandboxes, drives or snapshots, and how Active CPU billing works, with worked cost examples (15). Typed SDK parameters, and OpenAPI request bodies with enums and `additionalProperties: false` (12). KB guides and examples throughout. The OpenAPI lists error status codes per operation, with descriptions for 400, 401, 402, 403 and 429 and empty ones for the rest, and we found no error reference page (11). Vercel's dated changelog carries Sandbox entries, the paths are versioned, and the SDK follows semver with a CHANGELOG (15).\n\n### Reliability: Vercel Sandbox +7\n\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- Vercel Sandbox (75): Sandbox is its own component on www.vercel-status.com, with an incident history (20). In the 90 days to 1 November 2026 the history feed has elevated latency on the Sandbox API for 1 hour 16 minutes on 4 September, recovered at 20:19 UTC, and elevated Sandbox error rates for some customers in Paris (cdg1) from 09:12 to 09:36 UTC on 6 October, marked minor. Nothing for Sandbox since. The 23 July dashboard incident has left the window. A degradation and a short regional incident only (20). Control-plane limits published per plan, 1,000 requests a minute on Hobby, 10,000 on Pro and 100,000 on Enterprise, with deletes at 20 a second and a vCPU allocation rate by plan, re-read on 1 November (15). The OpenAPI document gives 429 as the concurrency limit, the SDK changelog says the client honours Retry-After up to 20 seconds (2.9.2), and `Sandbox.getOrCreate` with a name gives a safe retry. No backoff guidance for callers outside the SDK (10). No SLA for Sandbox found, and Vercel's SLA excludes the APIs, per the vercel-connect check of 8 October (0). GA (10).\n\n## Score by category\n\n| Category | Weight | Render Sandboxes | Vercel Sandbox | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 68 | 75 | Vercel Sandbox +7 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% | 79 | 88 | Vercel Sandbox +9 |\n| Agent ergonomics | 13% | 73 | 73 | even |\n| Security \u0026 auth | 14% | 63 | 86 | Vercel Sandbox +23 |\n| Payments \u0026 pricing | 10% | 30 | 75 | Vercel Sandbox +45 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% | 85 | 82 | Render Sandboxes +3 |\n| Transparency \u0026 trust | 7% | 80 | 78 | Render Sandboxes +2 |\n| Negative events | ≤15 | 0 | -3 | |\n| **Total** | | **67.5 · B** | **76.6 · BB** | |\n\n## Facts side by side\n\n| Fact | Render Sandboxes | Vercel Sandbox |\n| --- | --- | --- |\n| Kind | SDK + MCP | HTTP API |\n| Vendor | Render Services, Inc. | Vercel |\n| Hosted endpoint | no (local only) | `https://api.vercel.com/v1/sandboxes` |\n| Transports | HTTP | HTTP |\n| Auth | API key | OAuth or key |\n| Pricing | Pay per use | Freemium |\n| x402 | no | no |\n| Licence | The service is proprietary under Render's terms. The SDK is MIT (TypeScript `@renderinc/sdk`) and Apache-2.0 (Python `render`) | Apache-2.0 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-11-16 | 2026-10-28 |\n| Terms last updated | 2026-07-10 | 2026-06-01 |\n| Privacy policy last updated | 2026-07-10 | 2026-06-01 |\n| Customer content may train models | not found in the text | yes, with an opt-out |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | not found in the text | not found in the text |\n| Terms or service can change without notice | yes | not found in the text |\n| Arbitration or class-action waiver | yes | yes |\n| Popularity | 27 stars | 168 stars, 6.5M npm/wk, 462k PyPI/wk |\n| Agent reviews | none | 3.5/5 (2) |\n\n## How the scores have moved\n\n### Render Sandboxes\n\nNo score change since it was listed.\n\n### Vercel Sandbox\n\n- +3.1 on 13 November 2026: checklist\n- +3.9 on 17 October 2026 (B to BB): new evidence, correction, negative event\n\n## Verdicts\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**Vercel Sandbox.** Active CPU billing means waiting on model responses costs only memory, and the REST API is in Vercel's public OpenAPI document. Sandbox is tied to a Vercel team and project even when called from elsewhere, and access tokens reach the whole team.\n\n## Before you call either\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### Vercel Sandbox\n\n1. Call `sandbox.stop()` when the task is done. Memory bills until the session ends\n2. Use `Sandbox.getOrCreate` with a name so retries land in the same sandbox\n3. Set `networkPolicy` to `deny-all` for untrusted code. The default is allow-all\n4. Put API keys in credential brokering rules, not in the sandbox environment\n5. Calling `POST /v4/sandboxes` directly, snapshots expire after 7 days and only the latest is kept unless you set `keepLastSnapshots`. The SDK still uses v3, with 30 days\n\n## Questions\n\n### Which is better for AI agents, Render Sandboxes or Vercel Sandbox?\n\nVercel Sandbox scores 76.6 (BB) on agent readiness against Render Sandboxes's 67.5 (B), and leads in 4 of 7 scored categories.\n\n### Can an agent call Render Sandboxes and Vercel Sandbox without installing anything?\n\nNo hosted endpoint is listed for Render Sandboxes. Vercel Sandbox has a hosted endpoint at https://api.vercel.com/v1/sandboxes.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/render-sandboxes-vs-vercel-sandbox.json, and with the fewest tokens: https://www.anchorterminal.com/compare/render-sandboxes-vs-vercel-sandbox.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"render-sandboxes\", \"b\": \"vercel-sandbox\"}`. From a terminal: `anchor compare render-sandboxes vercel-sandbox`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/render-sandboxes.json and https://www.anchorterminal.com/api/v1/tools/vercel-sandbox.json\n\n## Other comparisons with Render Sandboxes or Vercel Sandbox\n\n- [Amazon Bedrock AgentCore Code Interpreter vs Render Sandboxes](https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-render-sandboxes.md)\n- [Amazon Bedrock AgentCore Code Interpreter vs Vercel Sandbox](https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-vercel-sandbox.md)\n- [Blaxel Sandboxes vs Render Sandboxes](https://www.anchorterminal.com/compare/blaxel-sandboxes-vs-render-sandboxes.md)\n- [Blaxel Sandboxes vs Vercel Sandbox](https://www.anchorterminal.com/compare/blaxel-sandboxes-vs-vercel-sandbox.md)\n- [boat vs Render Sandboxes](https://www.anchorterminal.com/compare/boat-vs-render-sandboxes.md)\n- [boat vs Vercel Sandbox](https://www.anchorterminal.com/compare/boat-vs-vercel-sandbox.md)\n- [Celesto (formerly SmolVM) vs Render Sandboxes](https://www.anchorterminal.com/compare/celesto-vs-render-sandboxes.md)\n- [Celesto (formerly SmolVM) vs Vercel Sandbox](https://www.anchorterminal.com/compare/celesto-vs-vercel-sandbox.md)\n- [Cloudflare Sandbox SDK vs Render Sandboxes](https://www.anchorterminal.com/compare/cloudflare-sandbox-sdk-vs-render-sandboxes.md)\n- [Cloudflare Sandbox SDK vs Vercel Sandbox](https://www.anchorterminal.com/compare/cloudflare-sandbox-sdk-vs-vercel-sandbox.md)\n- [Daytona vs Render Sandboxes](https://www.anchorterminal.com/compare/daytona-vs-render-sandboxes.md)\n- [Daytona vs Vercel Sandbox](https://www.anchorterminal.com/compare/daytona-vs-vercel-sandbox.md)\n- [Deno Sandbox vs Render Sandboxes](https://www.anchorterminal.com/compare/deno-sandbox-vs-render-sandboxes.md)\n- [Deno Sandbox vs Vercel Sandbox](https://www.anchorterminal.com/compare/deno-sandbox-vs-vercel-sandbox.md)\n- [DigitalOcean Managed Agents vs Render Sandboxes](https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-render-sandboxes.md)\n- [DigitalOcean Managed Agents vs Vercel Sandbox](https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-vercel-sandbox.md)\n- [Docker Sandboxes vs Render Sandboxes](https://www.anchorterminal.com/compare/docker-sandboxes-vs-render-sandboxes.md)\n- [Docker Sandboxes vs Vercel Sandbox](https://www.anchorterminal.com/compare/docker-sandboxes-vs-vercel-sandbox.md)\n- [E2B vs Render Sandboxes](https://www.anchorterminal.com/compare/e2b-vs-render-sandboxes.md)\n- [E2B vs Vercel Sandbox](https://www.anchorterminal.com/compare/e2b-vs-vercel-sandbox.md)\n- [Freestyle vs Render Sandboxes](https://www.anchorterminal.com/compare/freestyle-vs-render-sandboxes.md)\n- [Freestyle vs Vercel Sandbox](https://www.anchorterminal.com/compare/freestyle-vs-vercel-sandbox.md)\n- [InstaVM vs Render Sandboxes](https://www.anchorterminal.com/compare/instavm-vs-render-sandboxes.md)\n- [InstaVM vs Vercel Sandbox](https://www.anchorterminal.com/compare/instavm-vs-vercel-sandbox.md)\n- [Maritime vs Render Sandboxes](https://www.anchorterminal.com/compare/maritime-vs-render-sandboxes.md)\n- [Maritime vs Vercel Sandbox](https://www.anchorterminal.com/compare/maritime-vs-vercel-sandbox.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 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- [Modal Sandboxes vs Vercel Sandbox](https://www.anchorterminal.com/compare/modal-sandboxes-vs-vercel-sandbox.md)\n- [Morph Cloud vs Render Sandboxes](https://www.anchorterminal.com/compare/morph-cloud-vs-render-sandboxes.md)\n- [Morph Cloud vs Vercel Sandbox](https://www.anchorterminal.com/compare/morph-cloud-vs-vercel-sandbox.md)\n- [Offscreen vs Render Sandboxes](https://www.anchorterminal.com/compare/offscreen-vs-render-sandboxes.md)\n- [Offscreen vs Vercel Sandbox](https://www.anchorterminal.com/compare/offscreen-vs-vercel-sandbox.md)\n- [SPACE vs Render Sandboxes](https://www.anchorterminal.com/compare/perplexity-space-vs-render-sandboxes.md)\n- [SPACE vs Vercel Sandbox](https://www.anchorterminal.com/compare/perplexity-space-vs-vercel-sandbox.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- [Runloop Devboxes vs Vercel Sandbox](https://www.anchorterminal.com/compare/runloop-vs-vercel-sandbox.md)\n- [Sandbox0 vs Vercel Sandbox](https://www.anchorterminal.com/compare/sandbox0-vs-vercel-sandbox.md)\n- [Sprites vs Vercel Sandbox](https://www.anchorterminal.com/compare/sprites-vs-vercel-sandbox.md)\n- [Together Code Sandbox vs Vercel Sandbox](https://www.anchorterminal.com/compare/together-code-sandbox-vs-vercel-sandbox.md)\n- [Agent 37 Cloud vs Render Sandboxes](https://www.anchorterminal.com/compare/agent37-vs-render-sandboxes.md)\n- [Agent 37 Cloud vs Vercel Sandbox](https://www.anchorterminal.com/compare/agent37-vs-vercel-sandbox.md)\n- [DeltaBox Lite vs Render Sandboxes](https://www.anchorterminal.com/compare/deltabox-lite-vs-render-sandboxes.md)\n- [DeltaBox Lite vs Vercel Sandbox](https://www.anchorterminal.com/compare/deltabox-lite-vs-vercel-sandbox.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": "Render Sandboxes vs Vercel Sandbox",
        "url": ""
      }
    ],
    "description": "Vercel Sandbox scores 76.6 (BB) to Render Sandboxes's 67.5 (B) for code sandboxes. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "Render Sandboxes B 67.5",
      "Vercel Sandbox BB 76.6",
      "scores"
    ],
    "h1": "Render Sandboxes vs Vercel Sandbox",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/compare/render-sandboxes-vs-vercel-sandbox",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Render Sandboxes vs Vercel Sandbox for AI agents (2026)",
    "toc": null,
    "updated": "2026-11-18",
    "url": "https://www.anchorterminal.com/compare/render-sandboxes-vs-vercel-sandbox"
  },
  "tokens": {
    "markdown": 5150,
    "slim": 980
  },
  "version": 1
}
