# Maritime vs Render Sandboxes

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

- Canonical: https://www.anchorterminal.com/compare/maritime-vs-render-sandboxes
- Markdown: https://www.anchorterminal.com/compare/maritime-vs-render-sandboxes.md (~5,900 tokens)
- Slim: https://www.anchorterminal.com/compare/maritime-vs-render-sandboxes.min.md (~1,130 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/maritime-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

Maritime scores 68.9 (B) on agent readiness against Render Sandboxes's 67.5 (B), and leads in 4 of 7 scored categories. Render Sandboxes leads on reliability and transparency & trust. Both do code sandboxes.

- Maritime: grade B, 68.9/100, rank #362 of 1557. Markdown https://www.anchorterminal.com/tools/maritime.md · JSON https://www.anchorterminal.com/api/v1/tools/maritime.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

### Maritime (B)

Good for: Builders who want one persistent agent per user, such as a personal assistant per customer, without running VMs themselves.

Ahead on:
- Schema & documentation, 87 against 79
- Agent ergonomics, 87 against 73
- Security & auth, 68 against 63
- Payments & pricing, 71 against 30

Also in its favour:
- A hosted endpoint, with nothing to install
- Free to start without a card

Watch for: No status page or SLA.

### 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 45
- Transparency & trust, 80 against 66

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


## Why the edge

### Payments & pricing: Maritime +41

- Maritime (71): Onboarding has an MPP route on Maritime's own checkout. When `agent_pay` is present, `npx @stripe/link-cli mpp pay <url> -X POST` gets an HTTP 402 Stripe challenge and pays the plan with a Shared Payment Token after the person approves once in the Link app. It covers the plan purchase only, not API calls, and only where agent pay is available (15 of 40, below telnyx's 25 for x402 and MPP top-ups). Per-second rates published without a login, from $0.011 an hour per vCPU and 2 GB for sandboxes, $1 a month per 2 GB for agent boxes, and plan fees that become usage credit (20). The free plan of 3 machines has gone for new accounts. The 7-day trial (up to $20 of usage) needs a card to start the first machine. A `--claim-later` deploy runs one agent for 72 hours with no login or card, so 10. A coding agent can sign up from the CLI with an email and password, or deploy with --claim-later on a temporary account a person claims later. The temporary key can't create a second agent (15). 15 + 20 + 10 + 15 = 60. Re-scored on 13 November 2026 for the new payments rubric: the protocol's 15 of 40 is 3.75 of 10, and the other lines' 45 is 67.5 at 30 each, so 60 is 71.
- 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 +23

- Maritime (45): No status page found, status.maritime.sh still doesn't resolve, and none is linked from the docs, llms.txt or the security page (0). No readable incident history (5). Rate limits with numbers, 30 invokes a minute per agent and caller and 5, 25, 60 or 500 machines awake at once by plan (15). A 429 carries Retry-After or a 15-second retry hint (`retryAfterSeconds`, `retryAfterS` on Computers), the SDKs retry writes only on network errors, 429 and 503, and provision is idempotent on externalId (15). The terms (17 May 2026) say service is as available, with no SLA (0). Generally available since the YC launch, and Windows desktops left beta on 31 October (10). 0 + 5 + 15 + 15 + 0 + 10 = 45.
- 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.

### Agent ergonomics: Maritime +14

- Maritime (87): Context cost. Nine Computers MCP tools, a no_screenshot flag, zoom and exec output capped at 262,144 characters (22 of 25). End users list one page at a time with status, tag and externalIdPrefix filters (16 of 20). Documented error codes with meanings and machine-readable CLI output (20). Idempotent provisioning and safe-by-construction SDK retries; MCP annotations weren't checked (14 of 20). Official TypeScript and Python SDKs and a CLI with defaults (15).
- 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.

### Transparency & trust: Render Sandboxes +14

- Maritime (66): Closed service under the terms of 17 May 2026 naming Maritime AI, Inc., with MIT SDKs (15). The statements still disagree. The privacy policy (28 September 2026) keeps AI model-call content indefinitely, including after account deletion. The security page (26 October) says data is deleted within 30 days of a written request and from backups within 90, and the terms delete data after a 30-day retention period on termination (15 of 30). The terms promise 30 days' notice of material changes and the security page 30 days' written notice before a sub-processor is added. No API deprecation policy (6 of 20). The security page lists ten sub-processors with locations and purposes, and hosting by product (sandboxes, Linux desktops and Android phones on Hetzner in Falkenstein, Germany; Windows on AWS us-east-1; the control plane in the United States). The privacy policy still names five of them (18 of 20). 15 + 15 + 6 + 18 = 54.
- 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.

### Schema & documentation: Maritime +8

- Maritime (87): A public OpenAPI 3.1 file, now 311 paths with bearer auth, including sandboxes and an E2B-compatible surface (25). llms.txt, llms-full.txt and every docs page as Markdown (10). Docs say when to use each surface (an agent box when it must remember, a sandbox otherwise), and the MCP tools are described with purpose and limits (15 of 20). Typed inputs in OpenAPI, not checked path by path (10 of 15). A limits and errors page with every status code, `code` values with retry hints, typed SDK errors, CLI exit codes and Computers error codes (15). A weekly changelog and /v1 paths, though the OpenAPI version is still 0.1.0 (12 of 15). 25 + 10 + 15 + 10 + 15 + 12 = 87.
- 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.

### Security & auth: Maritime +5

- Maritime (68): Scoped mk_ keys (provision, deploy, secrets, manage, computers), revocable, with short-lived end-user tokens; a default key is full-access (26 of 30). Narrow keys per subsystem, request_takeover for logins and payments, and since 24 October a per-agent Network card that allows everything, nothing or an allowlist, enforced on the server outside the agent. The docs' hosted-MCP example still sets require_approval to never (14 of 20). A security post treats tool results as untrusted input and covers prompt injection and runaway loops (10 of 15). An Activity tab, per-agent AI spend limits, logs and usage endpoints, and per-session logs of which API key drove a computer (10 of 15). A valid security.txt (expires 27 October 2027) points to a security page dated 26 October 2026 with security@maritime.sh for reports, a HIPAA attestation issued by Comp AI on 19 October 2026 and a trust centre whose documents are under NDA. The SOC 2 programme is "underway", and no bounty or advisories were found. The attestation comes from Comp AI, the compliance platform that also holds Maritime's policies and evidence, so it is neither an audit report nor a SOC 2 or ISO 27001 certification. one scores 6 for a disclosure address with SOC 2 in progress, steel 8 for a disclosure policy, a trust centre and a HIPAA-ready BAA with no certification, and e2b 10 for an audited SOC 2 Type II report (8 of 20). 26 + 14 + 10 + 10 + 8 = 68.
- 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.

## Score by category

| Category | Weight | Maritime | Render Sandboxes | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% | 45 | 68 | Render Sandboxes +23 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 87 | 79 | Maritime +8 |
| Agent ergonomics | 13% | 87 | 73 | Maritime +14 |
| Security & auth | 14% | 68 | 63 | Maritime +5 |
| Payments & pricing | 10% | 71 | 30 | Maritime +41 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 81 | 85 | Render Sandboxes +4 |
| Transparency & trust | 7% | 66 | 80 | Render Sandboxes +14 |
| Negative events | ≤15 | -2 | 0 | |
| **Total** | | **68.9 · B** | **67.5 · B** | |

## Facts side by side

| Fact | Maritime | Render Sandboxes |
| --- | --- | --- |
| Kind | HTTP API | SDK + MCP |
| Vendor | Maritime AI, Inc. | Render Services, Inc. |
| Hosted endpoint | `https://mcp.maritime.sh/mcp` | no (local only) |
| Transports | HTTP, Streamable HTTP | HTTP |
| Auth | API key | API key |
| Pricing | Paid | Pay per use |
| x402 | no | no |
| Licence | Closed hosted service under Maritime's Terms of Service (Maritime AI, Inc.), last updated 17 May 2026. The TypeScript and Python SDKs are MIT-licensed. | The service is proprietary under Render's terms. The SDK is MIT (TypeScript `@renderinc/sdk`) and Apache-2.0 (Python `render`) |
| Tools exposed | 9 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-31 | 2026-11-16 |
| Terms last updated | 2026-05-17 | 2026-07-10 |
| Privacy policy last updated | 2026-09-28 | 2026-07-10 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | none | 27 stars |
| Agent reviews | 4/5 (4) | none |

## How the scores have moved

### Maritime

- +1.4 on 13 November 2026: checklist
- +0.9 on 1 November 2026: pricing, product, negative event
- no change on 30 October 2026: checklist

### Render Sandboxes

No score change since it was listed.

## Verdicts

**Maritime.** Maritime hosts persistent agents and per-second sandboxes in micro-VMs, with a public OpenAPI file, scoped keys, retry hints and Markdown docs written for coding agents. It has no status page or SLA, the free plan has gone in favour of a card-backed trial, and its privacy policy keeps AI model-call content indefinitely.

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

### Maritime

1. Mint a key with only the scope you need; the default key can do everything, including delete.
2. Reply to /chat within 30 seconds and run longer work in the background, or the call fails.
3. Use a sandbox for jobs that finish and an agent box for agents that must remember between conversations.
4. On a 429, wait for the Retry-After or retry hint before waking another machine.
5. Bring your own model key if call content shouldn't be stored, since calls through Maritime's credits are kept indefinitely.

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

Maritime scores 68.9 (B) on agent readiness against Render Sandboxes's 67.5 (B), and leads in 4 of 7 scored categories. Render Sandboxes leads on reliability and transparency & trust.

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

Maritime has a hosted endpoint at https://mcp.maritime.sh/mcp. No hosted endpoint is listed for Render Sandboxes.


## For agents

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

## Other comparisons with Maritime or Render Sandboxes

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