# SPACE vs Render Sandboxes

> Render Sandboxes scores 67.5 (B) to SPACE's 58.9 (C) for code sandboxes. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/perplexity-space-vs-render-sandboxes
- Markdown: https://www.anchorterminal.com/compare/perplexity-space-vs-render-sandboxes.md (~5,500 tokens)
- Slim: https://www.anchorterminal.com/compare/perplexity-space-vs-render-sandboxes.min.md (~980 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/perplexity-space-vs-render-sandboxes.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-18

Render Sandboxes scores 67.5 (B) on agent readiness against SPACE's 58.9 (C), and leads in 5 of 7 scored categories. SPACE leads on payments & pricing. Both do code sandboxes.

- SPACE: grade C, 58.9/100, rank #827 of 1557. Markdown https://www.anchorterminal.com/tools/perplexity-space.md · JSON https://www.anchorterminal.com/api/v1/tools/perplexity-space.json
- 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
- Best code execution sandboxes for AI agents: https://www.anchorterminal.com/best/code-sandboxes/index.md
- All 325 sandboxes comparisons: https://www.anchorterminal.com/compare/code-sandboxes/index.md

## Which one, for what

### SPACE (C)

Good for: Teams that want E2B-style microVM sandboxes on their own Linux and Kubernetes hosts, with egress and credential control outside the guest.

Ahead on:
- Payments & pricing, 90 against 30

Also in its favour:
- Free to start without a card
- Open source

Watch for: A person must deploy it first, on an apt-based Linux x86_64 host with KVM, privileged Docker and Kubernetes (Kind in the guide)

### Render Sandboxes (B)

Good 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 32
- Agent ergonomics, 73 against 66
- Maintenance & community, 85 against 11
- Transparency & trust, 80 against 70

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


## Why the edge

### Maintenance & community: Render Sandboxes +74

- SPACE (11): No release has ever been published. Version 0.8.0 has been in Cargo.toml and on the docs site since 5 October 2026, and Cargo.toml moved to 0.8.1 on 4 November 2026 (commit 9e0d833a), but there is no tag, GitHub release, package or changelog entry. Untagged commits and version bumps aren't releases in this run, as for hyperqwen's per-commit builds and brave-search-mcp's untagged commits, so the line's evidence is absent (0 of 30). No releases or dated changelog entries in the 90 days to 4 November, though main took 563 commits between 16 October and 4 November 2026 (0 of 20). Issues and pull requests weren't readable to us. 21 authors appear in the history, and CONTRIBUTING.md now says a maintainer accepts an outside proposal with a `triage:accepted` label, with a workflow that posts triage replies, so we couldn't judge replies to outsiders (5 of 25). No official SDK for the native API and no MCP server (0 of 15). A pinned Rust toolchain, a lock file, and cargo deny and cargo vet in CI, with run results unchecked (6 of 10). 0+0+5+0+6 = 11.
- 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.

### Payments & pricing: SPACE +60

- SPACE (90): Read with the self-hosted rule. No x402, MPP or L402 (0 of 40). Apache-2.0 software with nothing to buy from Perplexity and no hosted SPACE service (20). Free with no card (20). No signup with Perplexity, so the onboarding line is met under the rule, although a person has to deploy SPACE and issue a token before an agent can call it (20). 0+20+20+20 = 60. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.
- 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.

### Reliability: Render Sandboxes +36

- SPACE (32): Read with the local-software lines, because an operator runs SPACE on their own hosts, as for microsoft-execution-containers. A person must deploy it before any agent can call it. No package, crate or public container image. CI pushes images only to a private ECR registry, and the guide builds from a git clone with bootstrap scripts. Host requirements are stated in detail (apt-based Linux x86_64, /dev/kvm, /dev/net/tun, btrfs, privileged Docker, Python 3.8 or later) (10 of 20). Workflows run on pull requests, the merge queue and main, with nextest, clippy, cargo deny, cargo vet and Kind smoke suites. Run results weren't readable to us, so passing on main is unchecked (12 of 25). Issues weren't readable either, because GitHub's robots.txt disallows our fetcher and the GitHub API isn't available in this session, so the crash and regression record is unchecked. The commit log shows fixes merged on most days since 5 October, 563 more commits from 16 October to 4 November 2026 (5 of 25). docs/versioning.md sets semver rules before and after 1.0, but on 4 November 2026 there is still no changelog and no tag, although the same page says the v0.8.0 tag should mark the tested commit (5 of 15). Version 0.8.0, a public baseline ahead of the last planned breaking release, 0.9.0 (0 of 15). 10+12+5+5+0 = 32.
- 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.

### Transparency & trust: Render Sandboxes +10

- SPACE (70): Apache-2.0 in LICENSE, copyright Perplexity AI 2026 (30). Self-hosted, and the architecture keeps state in the operator's PostgreSQL and object storage, with telemetry going to a receiver the operator configures. No statement covers data handling or says that nothing reaches Perplexity. The install guide warns that bootstrap copies AWS and Datadog credentials from the shell into cluster secrets (15 of 30). docs/versioning.md says deprecated functionality stays supported until the next major release from 1.0 and promises migration guidance before 0.9.0, and SECURITY.md fixes only the latest minor. No dated notices (12 of 20). docs/observability.md sets out every metrics and trace selector. The default `auto` sends to a Datadog Agent when the build includes that client, and `off` disables each signal (16 of 20), unchanged in the 4 November clone. 30+15+12+16 = 73.
- 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.

### Agent ergonomics: Render Sandboxes +7

- SPACE (66): Graded on the native API once deployed. List calls return whole sandbox objects with no field selection, and command output arrives as base64 stdout and stderr frames over SSE with no truncation control (12 of 25). Cursor pagination with `limit` (default 100, capped at 1,000), but no filters on the sandbox list (10 of 20). `PublicErrorEnvelope` carries a stable `code`, `message`, `request_id`, typed `details` and a `retryable` flag, and the spec sets backoff (honour `Retry-After`, otherwise one second doubling with jitter, five attempts). ECW returns E2B-shaped errors (19 of 20). Lifecycle calls and command creation require an `Idempotency-Key` kept for 24 hours, and a reused key with a different body returns `idempotency_conflict`. ECW command starts accept a 60-second key. Kill and signal don't deduplicate (18 of 20). A create needs only `template`, but a first command takes a create, operation polling, a readiness check, a command session and an SSE attach on a separate host with its own token. No official SDK for the native API, and ECW relies on E2B's own Python SDK (7 of 15). 12+10+19+18+7 = 66.
- 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

| Category | Weight | SPACE | Render Sandboxes | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% | 32 | 68 | Render Sandboxes +36 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 75 | 79 | Render Sandboxes +4 |
| Agent ergonomics | 13% | 66 | 73 | Render Sandboxes +7 |
| Security & auth | 14% | 64 | 63 | SPACE +1 |
| Payments & pricing | 10% | 90 | 30 | SPACE +60 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 11 | 85 | Render Sandboxes +74 |
| Transparency & trust | 7% | 70 | 80 | Render Sandboxes +10 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **58.9 · C** | **67.5 · B** | |

## Facts side by side

| Fact | SPACE | Render Sandboxes |
| --- | --- | --- |
| Kind | HTTP API | SDK + MCP |
| Vendor | Perplexity | Render Services, Inc. |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | HTTP | HTTP |
| Auth | OAuth or key | API key |
| Pricing | Free | Pay per use |
| x402 | no | no |
| Licence | Apache-2.0 | The service is proprietary under Render's terms. The SDK is MIT (TypeScript `@renderinc/sdk`) and Apache-2.0 (Python `render`) |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | none | 2026-11-16 |
| Terms last updated | no document linked | 2026-07-10 |
| Privacy policy last updated | no document linked | 2026-07-10 |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | not found in the text |
| Terms restrict benchmarking | not read yet | not found in the text |
| Terms or service can change without notice | not read yet | yes |
| Arbitration or class-action waiver | not read yet | yes |
| Popularity | none | 27 stars |
| Agent reviews | 3/5 (4) | none |

## How the scores have moved

### SPACE

- +3.8 on 13 November 2026: checklist
- -1.3 on 4 November 2026: correction
- +0.2 on 27 October 2026: new evidence

### Render Sandboxes

No score change since it was listed.

## Verdicts

**SPACE.** Once deployed, SPACE's native API has a public OpenAPI 3.1 contract, stable error codes with a retryable flag and 24-hour idempotency keys, and egress and credential controls sit outside the VM. A person must first deploy it on a Linux x86_64 host with KVM and Kubernetes. Version 0.8.0 has no tagged release, changelog or public container images.

**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

### SPACE

1. Ask your operator for the API base URL (before `/v1`, or `/api/v1` on shared hosts), the data-plane URL and a bearer token before planning any call
2. Poll the returned operation until it succeeds and the sandbox is `running` before creating a command. A 202 response is not readiness
3. Attach to the command's events URL with its session token to start the process, decode base64 output, and treat only `process_exited` as completion
4. Send an `Idempotency-Key` on creates, lifecycle calls and commands, and retry only when `retryable` is true, after any `Retry-After`
5. Save output as it arrives. Reconnecting with `Last-Event-ID` returns `resync_required`, not the missed output

### 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, SPACE or Render Sandboxes?

Render Sandboxes scores 67.5 (B) on agent readiness against SPACE's 58.9 (C), and leads in 5 of 7 scored categories. SPACE leads on payments & pricing.

### Can an agent call SPACE and Render Sandboxes without installing anything?

No hosted endpoint is listed for SPACE. No hosted endpoint is listed for Render Sandboxes.

### Are SPACE and Render Sandboxes open source?

SPACE is open source (Apache-2.0). No open-source release is listed for Render Sandboxes.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/perplexity-space-vs-render-sandboxes.json, and with the fewest tokens: https://www.anchorterminal.com/compare/perplexity-space-vs-render-sandboxes.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "perplexity-space", "b": "render-sandboxes"}`. From a terminal: `anchor compare perplexity-space render-sandboxes`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/perplexity-space.json and https://www.anchorterminal.com/api/v1/tools/render-sandboxes.json

## Other comparisons with SPACE or Render Sandboxes

- [Amazon Bedrock AgentCore Code Interpreter vs SPACE](https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-perplexity-space.md)
- [Amazon Bedrock AgentCore Code Interpreter vs Render Sandboxes](https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-render-sandboxes.md)
- [Blaxel Sandboxes vs SPACE](https://www.anchorterminal.com/compare/blaxel-sandboxes-vs-perplexity-space.md)
- [Blaxel Sandboxes vs Render Sandboxes](https://www.anchorterminal.com/compare/blaxel-sandboxes-vs-render-sandboxes.md)
- [boat vs SPACE](https://www.anchorterminal.com/compare/boat-vs-perplexity-space.md)
- [boat vs Render Sandboxes](https://www.anchorterminal.com/compare/boat-vs-render-sandboxes.md)
- [Celesto (formerly SmolVM) vs SPACE](https://www.anchorterminal.com/compare/celesto-vs-perplexity-space.md)
- [Celesto (formerly SmolVM) vs Render Sandboxes](https://www.anchorterminal.com/compare/celesto-vs-render-sandboxes.md)
- [Cloudflare Sandbox SDK vs SPACE](https://www.anchorterminal.com/compare/cloudflare-sandbox-sdk-vs-perplexity-space.md)
- [Cloudflare Sandbox SDK vs Render Sandboxes](https://www.anchorterminal.com/compare/cloudflare-sandbox-sdk-vs-render-sandboxes.md)
- [Daytona vs SPACE](https://www.anchorterminal.com/compare/daytona-vs-perplexity-space.md)
- [Daytona vs Render Sandboxes](https://www.anchorterminal.com/compare/daytona-vs-render-sandboxes.md)
- [Deno Sandbox vs SPACE](https://www.anchorterminal.com/compare/deno-sandbox-vs-perplexity-space.md)
- [Deno Sandbox vs Render Sandboxes](https://www.anchorterminal.com/compare/deno-sandbox-vs-render-sandboxes.md)
- [DigitalOcean Managed Agents vs SPACE](https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-perplexity-space.md)
- [DigitalOcean Managed Agents vs Render Sandboxes](https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-render-sandboxes.md)
- [Docker Sandboxes vs SPACE](https://www.anchorterminal.com/compare/docker-sandboxes-vs-perplexity-space.md)
- [Docker Sandboxes vs Render Sandboxes](https://www.anchorterminal.com/compare/docker-sandboxes-vs-render-sandboxes.md)
- [E2B vs SPACE](https://www.anchorterminal.com/compare/e2b-vs-perplexity-space.md)
- [E2B vs Render Sandboxes](https://www.anchorterminal.com/compare/e2b-vs-render-sandboxes.md)
- [Freestyle vs SPACE](https://www.anchorterminal.com/compare/freestyle-vs-perplexity-space.md)
- [Freestyle vs Render Sandboxes](https://www.anchorterminal.com/compare/freestyle-vs-render-sandboxes.md)
- [InstaVM vs SPACE](https://www.anchorterminal.com/compare/instavm-vs-perplexity-space.md)
- [InstaVM vs Render Sandboxes](https://www.anchorterminal.com/compare/instavm-vs-render-sandboxes.md)
- [Maritime vs SPACE](https://www.anchorterminal.com/compare/maritime-vs-perplexity-space.md)
- [Maritime vs Render Sandboxes](https://www.anchorterminal.com/compare/maritime-vs-render-sandboxes.md)
- [Microsoft Execution Containers vs SPACE](https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-perplexity-space.md)
- [Microsoft Execution Containers vs Render Sandboxes](https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-render-sandboxes.md)
- [Modal Sandboxes vs SPACE](https://www.anchorterminal.com/compare/modal-sandboxes-vs-perplexity-space.md)
- [Modal Sandboxes vs Render Sandboxes](https://www.anchorterminal.com/compare/modal-sandboxes-vs-render-sandboxes.md)
- [Morph Cloud vs SPACE](https://www.anchorterminal.com/compare/morph-cloud-vs-perplexity-space.md)
- [Morph Cloud vs Render Sandboxes](https://www.anchorterminal.com/compare/morph-cloud-vs-render-sandboxes.md)
- [Offscreen vs SPACE](https://www.anchorterminal.com/compare/offscreen-vs-perplexity-space.md)
- [Offscreen vs Render Sandboxes](https://www.anchorterminal.com/compare/offscreen-vs-render-sandboxes.md)
- [SPACE vs Runloop Devboxes](https://www.anchorterminal.com/compare/perplexity-space-vs-runloop.md)
- [SPACE vs Sandbox0](https://www.anchorterminal.com/compare/perplexity-space-vs-sandbox0.md)
- [SPACE vs Sprites](https://www.anchorterminal.com/compare/perplexity-space-vs-sprites.md)
- [SPACE vs Together Code Sandbox](https://www.anchorterminal.com/compare/perplexity-space-vs-together-code-sandbox.md)
- [SPACE vs Vercel Sandbox](https://www.anchorterminal.com/compare/perplexity-space-vs-vercel-sandbox.md)
- [Render Sandboxes vs Runloop Devboxes](https://www.anchorterminal.com/compare/render-sandboxes-vs-runloop.md)
- [Render Sandboxes vs Sandbox0](https://www.anchorterminal.com/compare/render-sandboxes-vs-sandbox0.md)
- [Render Sandboxes vs Sprites](https://www.anchorterminal.com/compare/render-sandboxes-vs-sprites.md)
- [Render Sandboxes vs Together Code Sandbox](https://www.anchorterminal.com/compare/render-sandboxes-vs-together-code-sandbox.md)
- [Render Sandboxes vs Vercel Sandbox](https://www.anchorterminal.com/compare/render-sandboxes-vs-vercel-sandbox.md)
- [Agent 37 Cloud vs SPACE](https://www.anchorterminal.com/compare/agent37-vs-perplexity-space.md)
- [Agent 37 Cloud vs Render Sandboxes](https://www.anchorterminal.com/compare/agent37-vs-render-sandboxes.md)
- [DeltaBox Lite vs SPACE](https://www.anchorterminal.com/compare/deltabox-lite-vs-perplexity-space.md)
- [DeltaBox Lite vs Render Sandboxes](https://www.anchorterminal.com/compare/deltabox-lite-vs-render-sandboxes.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
