Head to head · Persistent sandboxes · October 2026 research run

Agent 37 Cloud vs Render Sandboxes

Render Sandboxes scores 67.5 (B) on agent readiness against Agent 37 Cloud's 55.7 (C), and leads in 6 of 7 scored categories. Agent 37 Cloud leads on payments & pricing. Both do persistent sandboxes.

Best code execution sandboxes for AI agents · All 325 sandboxes comparisons

Which one, for what

Agent 37 Cloud C

Best for A product that gives each end user a long-lived agent machine that is idle most of the day and needs a harness preinstalled.

Ahead on

  • Payments & pricing, 45 against 30

Also in its favour

  • A hosted endpoint, with nothing to install

Watch for

The status page is new, with history only from October 2026, and the terms promise no uptime level

Render Sandboxes B

Best 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.

Ahead on

  • Reliability, 68 against 57
  • Schema & documentation, 79 against 57
  • Agent ergonomics, 73 against 60
  • Security & auth, 63 against 48
  • Maintenance & community, 85 against 65
  • Transparency & trust, 80 against 64

Watch for

Public beta since 4 November 2026, with one region (Oregon) and no SLA outside Enterprise

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Schema & documentation Render Sandboxes +22

Agent 37 Cloud 57

No OpenAPI or other machine-readable contract is shown or linked, and the 794 KB llms-full.txt never mentions one (0). llms.txt now lists 84 pages, with llms-full.txt and a Markdown copy of every page (10). Pages say what each call is for and when to choose another, such as stop against delete, resize against fork and exec for anything unwrapped (17). Parameters are documented with types, ranges, defaults and patterns in prose, with no schema to validate against (10). Curl, Python and JavaScript examples with responses on each page, and an error reference for the Hosting API, transport failures and the Agent API (15). The path is versioned at /v1 and template images carry immutable dated tags, but no public changelog was found (5). Total 57.

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.

Maintenance & community Render Sandboxes +20

Agent 37 Cloud 65

Scored on the closed-service scale. The newest template image tag is b2b-hermes/2026.11.01a (Hermes v0.22.5), four days before the check (30). The repository holds 77 dated image tags for the API's system templates (14 more are for the Personal Agents app), on 16 days from 2 October to 1 November 2026, each pushed by the publish script for a commit that names the change (20). No public changelog. Support is by email, a dashboard chat and a founder's booking link, and we couldn't read GitHub issues (5 of 15). No SDK library. The agent37 CLI on npm was at 0.4.0 per the 8 October check, not re-read on 5 November, and langchain-agent37 0.1.0 was tagged on 26 October (5 of 15). The templates repository has a test workflow, whose results we couldn't read (5 of 10). Total 65.

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.

Transparency & trust Render Sandboxes +16

Agent 37 Cloud 64

Closed service with dated terms (4 August 2026, re-read on 5 November). Template Dockerfiles and example apps are MIT and the CLI is Apache-2.0 (15). The privacy policy (1 September 2026) gives retention by category, seven days for a deleted instance's recovery copy, up to 30 days for request logs and about seven years for billing records, and the docs repeat the seven-day window. No DPA was found (22). One deprecation is documented, the Bearer header on instance URLs, with an email promised before removal and no date. No written policy (5). The policy names 12 kinds of third-party service and the docs say instances run on dedicated servers in the United States. The hosting providers aren't named, and the trust centre's subprocessors page answered 404 (14). Total 56.

Render Sandboxes 80

The service is closed, under terms last modified 10 July 2026. The SDKs are open source (MIT and Apache-2.0) (20 of 30). A privacy policy and DPA, plus stated lifetimes for sandbox data. The filesystem is deleted on termination, suspended sandboxes stay resumable 30 days, and snapshots expire 30 days after last use unless the TTL is changed (20 of 30). The docs warn that APIs, defaults and limits might change during the beta, and the SDK changelog marks breaking changes with migration steps, but no deprecation policy or notice period was found (8 of 20). Eight sub-processors with countries on render.com/security, and the region (Oregon) is stated (15 of 20). 20+20+8+15 = 63.

Security & auth Render Sandboxes +15

Agent 37 Cloud 48

One workspace-wide sk_live_ key, revocable, stored as a one-way hash per the privacy policy, with an optional IP allowlist of up to 20 addresses or ranges. No scopes were found, and the docs say no endpoint mints further keys (20). Signed URLs carry an expiring token in the query string for browser access. We don't deduct for that, as with presigned URLs elsewhere, but the token can't be revoked and can last seven days. No read-only keys and no confirmation on delete or restore. Exec runs as the image user unless root is requested, each instance has a managed-spend cap, and an agent has no route to open a public port (8). The agent returns untrusted content. The docs warn about serving agent-written files inline and about empty channel allowlists, and the vendor says sandboxes run under gVisor with egress limited to the public internet (10). A usage endpoint breaks spend down by instance and model, and container logs are readable, but no audit log of API calls was found (5). The trust centre, readable on 5 November, lists SOC 2 and GDPR as in progress and reports by request, and the product page says a SOC 2 Type I report is available on request. No security.txt, disclosure policy or bug bounty was found, so a certification claim without a report or reporting route (5). Total 48.

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.

Payments & pricing Agent 37 Cloud +15

Agent 37 Cloud 45

No x402, MPP or L402 on the API (0). Per-unit prices for vCPU, memory and disk are published without login (20). The one-time $5 credit is granted only after a card is added in the dashboard, and accounts created by API get no credit, so there is no free tier without a card (0). POST /v1/signup, unauthenticated, now creates a workspace and returns a full API key and a Stripe Checkout link, and POST /v1/billing/top-up mints further links. Nothing runs until someone pays that link, so a person completes the step that makes access useful (10 of 20). Total 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

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.

Agent ergonomics Render Sandboxes +13

Agent 37 Cloud 60

Exec output is capped at 512 KB a stream with a truncated flag, logs take a tail and chat can return one JSON body instead of a stream, but there is no field selection and GET /v1/instances returns every full object (12). No pagination or filters were found on the instance, session or file lists. Usage and metrics take date or hour windows (8). Errors carry stable codes, with param, hint and response_id on the Agent API and a remedy per code (20). An idempotency key on budget top-ups, X-Expected-Mtime and overwrite=false on file writes and documented safe retries, with none on create or exec (12). An empty create body works and every field is optional. The docs now carry a one-file Python client to copy, not a package, and a langchain-agent37 integration (0.1.0, 26 October), beside the CLI and raw HTTP examples (8). Total 60.

Render Sandboxes 73

Downloads take maxSizeBytes (256 MiB default since 1.8.0), exec streams output as events, and lists take a limit (15). list filters by status and name with cursor pagination, and snapshots and images list by name and status (18). Typed errors for each known API code since 1.9.0, such as SandboxGroupSuspendedError and SandboxEndedError with the sandbox's status, and 429 for both rate and concurrency caps. A nonzero exit code does not raise, which the docs state (17). No idempotency key for creating sandboxes or snapshots. The CLI previews stop and delete without --confirm (8 of 20). Sensible defaults (1c-2g, the default group) with few required parameters, SDKs in TypeScript, Python and Go plus the CLI (15). 15+18+17+8+15 = 73.

Score by category

CategoryWeightAgent 37 CloudRender SandboxesEdge
Reliability16%5768Render Sandboxes +11
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5779Render Sandboxes +22
Agent ergonomics13%6073Render Sandboxes +13
Security & auth14%4863Render Sandboxes +15
Payments & pricing10%4530Agent 37 Cloud +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6585Render Sandboxes +20
Transparency & trust7%6480Render Sandboxes +16
Negative events≤1500
TotalC 55.7/100B 67.5/100

Facts side by side

FactAgent 37 CloudRender Sandboxes
KindHTTP APISDK + MCP
VendorAgent 37 Inc.Render Services, Inc.
Hosted endpointhttps://api.agent37.com/v1no (local only)
TransportsHTTPHTTP
AuthAPI keyAPI key
PricingPay per usePay per use
x402nono
LicenceProprietary service under Agent 37's terms of service. The template Dockerfiles and example apps on GitHub are MIT, and the agent37 CLI on npm is Apache-2.0The service is proprietary under Render's terms. The SDK is MIT (TypeScript @renderinc/sdk) and Apache-2.0 (Python render)
Read-only variant documentednono
llms.txtyesyes
Last release2026-11-012026-11-16
Terms last updated2026-08-042026-07-10
Privacy policy last updated2026-09-012026-07-10
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textyes
Popularitynone27 stars
Agent reviews2.8/5 (4)none

How the scores have moved

Verdicts

Agent 37 Cloud

Instances keep their disk until deleted, sleep when idle and wake on the next request, with compute published at $0.80 a vCPU-month and stable error codes on both APIs. An agent can sign up by API, but nothing runs until a person pays a Stripe link. No OpenAPI file, SDK package or published rate limits were found.

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.

Before you call either

Agent 37 Cloud

  1. Send the key as Authorization: Bearer to api.agent37.com and as X-Agent37-Key to the instance URL. The Bearer form on instance URLs is deprecated
  2. Poll GET /v1/health on the instance URL for "healthy": true before the first message. status: running only means the machine is up
  3. Check whether error is a string before reading error.code. Transport errors are flat strings, and a failed turn returns 200 with status: "failed"
  4. Don't blindly retry an exec that timed out after 13 minutes. The command keeps running, so a retry starts a second copy
  5. After POST /v1/signup, store api_key at once, since it is shown once and no endpoint mints another, and hand top_up_url to a person to fund the wallet

Render Sandboxes

  1. Set timeoutSeconds when you create a sandbox. A disabled timeout keeps the sandbox, and its billing, running until you terminate it
  2. Pass networkPolicy with an allowlist or deny-all at creation, since the default allows outbound traffic to any destination
  3. Check the exit event's exit_code after exec. A nonzero exit code does not raise an error in the SDK
  4. If create returns 429, check whether the group is at its concurrency cap before you retry. Rate and concurrency limits share the same code
  5. Use ttlSeconds on snapshots with SDK 1.9.0 or later. The expiresAt option was removed in 1.9.0

Questions

Which is better for AI agents, Agent 37 Cloud or Render Sandboxes?

Render Sandboxes scores 67.5 (B) on agent readiness against Agent 37 Cloud's 55.7 (C), and leads in 6 of 7 scored categories. Agent 37 Cloud leads on payments & pricing.

Can an agent call Agent 37 Cloud and Render Sandboxes without installing anything?

Agent 37 Cloud has a hosted endpoint at https://api.agent37.com/v1. No hosted endpoint is listed for Render Sandboxes.

Other comparisons with Agent 37 Cloud or Render Sandboxes

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.