Head to head · Code sandboxes · October 2026 research run

boat vs Sandbox0

boat scores 71.8 (BB) on agent readiness against Sandbox0's 56.6 (C), and leads in 6 of 7 scored categories. Both do code sandboxes.

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

Which one, for what

boat BB

Best for Long-lived, full Ubuntu VMs with Docker, a desktop and Chrome for coding agents, evals and products that give each user a sandbox, hosted in the EU.

Ahead on

  • Reliability, 60 against 37
  • Schema & documentation, 90 against 77
  • Agent ergonomics, 93 against 74
  • Security & auth, 67 against 58
  • Payments & pricing, 45 against 30
  • Transparency & trust, 69 against 47

Also in its favour

  • Agent-ready, a grade of BB or better

Watch for

No security.txt or bug bounty, and SOC 2 is in progress

Sandbox0 C

Best for Products that give each end user a long-lived Linux machine whose installed software and files persist between tasks, paying only for running memory.

Also in its favour

  • A hosted endpoint, with nothing to install

Watch for

No status page, incident history or SLA found

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.

Reliability boat +23

boat 60

Hosted reading. A status page at status.ascii.dev, linked from the docs, draws its system status and metrics in a script our reader could not run, so component history was not confirmed (15 of 20). No readable incident history (5). Limits published per plan with numbers, from 12 starts a minute and 100 sandboxes at once on the $20 plan to 90 a minute and 2,000 on the $2,000 plan, plus 10,000 requests a minute per IP (15). Every 429 sends Retry-After, RateLimit headers carry the remaining starts, 503s carry retryAfterSeconds, the docs give a backoff example, and create and fork take an Idempotency-Key (15). No SLA found. The docs cite a measured 99.95% sandbox uptime, and the terms disclaim uptime warranties (0). The API is v1 with no beta label (10). 15+5+15+15+0+10 = 60.

Sandbox0 37

Graded with the hosted lines, on Sandbox0 Cloud only. No status page found. sandbox0.ai/status answers 404, status.sandbox0.ai doesn't resolve, and none is linked from the site, llms.txt or docs (0, re-read 4 November). No readable incident history (5). Default quotas are published with numbers, 20 running sandboxes, unlimited paused sandboxes, 5 claims a second and 100 API requests a second per team, burst 200 (15). Quota failures return 429 with error.code quota_exceeded, claims carry Retry-After, and the OpenAPI file documents Idempotency-Key on pause, resume, restart, fork, snapshot capture and restore, sessions and template creation, with the docs saying to retry the same resize on 503. The core write, POST /api/v1/sandboxes (claim), which starts a billed sandbox and is the listing's own example call, takes no key, and the keys on pause and resume apply only to their conditional memory forms. That is safe-retry guidance without idempotency keys on the core write (12; the 21 October 13 isn't a checklist value). The terms provide the service as is and no SLA is published (0). The core sandbox API carries no beta label, but memory checkpoints and live migration are called experimental, the OpenAPI file is version 0.1.0 and the SDKs are 0.10.x (5 of 10, the 21 October partial kept). 0 + 5 + 15 + 12 + 0 + 5 = 37.

Transparency & trust boat +22

boat 69

Closed service under terms of 12 October 2026 from Dedale AI, Corp., a Delaware corporation (15). The terms, privacy policy and docs agree on retention. A stopped sandbox's disk is kept at least 14 days, saved snapshots have no scheduled expiry, and zero data retention can be turned on. The terms say the cleanup job does not yet delete in production. A DPA is available on request (25 of 30). The Box to boat rename on 15 September 2026 put Deprecation and Sunset headers on old surfaces with a dated sunset of 31 October 2026, and deprecated endpoints are marked in the reference (18 of 20). Infrastructure hosts (OVH, Hetzner) and other processors are named, sandboxes run in Germany, Finland and France, and snapshot copies can be stored outside the EU (16 of 20). 15+25+18+16 = 74.

Sandbox0 47

The hosted service is closed under clear, dated terms naming Lougao, LLC and Delaware law. The SDKs and CLI are Apache-2.0, and the earlier runtime stays Apache-2.0 as an unmaintained archive that no longer matches the service (18 of 30). The privacy policy (effective 17 June 2026, re-read 4 November) says what is collected, that customer content is processed only to run the service and that no advertising cookies are used, but retention is "as long as needed" with no periods, and no DPA was found (12 of 30). No deprecation policy. The terms say parts of the service may be changed or discontinued, and self-hosting ended on 16 October 2026 with no notice found before that day. The deployment page now dates the end clearly (3 of 20). Data location is stated (U.S. infrastructure, one U.S. East region), but service providers are described by kind only and not named (8 of 20).

Agent ergonomics boat +19

boat 93

Lists take limit from 1 to 200, commands can stream or detach, and a file read above 5 MiB returns 413 with a pointer to a signed download URL (20). Cursor pagination with hasMore and filters by name, name prefix, label and state (20). A stable error envelope with code, message, details and requestId, and a per-status table of what to do (20). Idempotency-Key on create and fork, kept 24 hours, with 409 idempotency_in_progress and 409 idempotency_key_reused, and per-code guidance on whether a command may have run (18). ttlSeconds defaults to one hour, the body of a create can be empty, and SDKs exist in Python and TypeScript beside the CLI with --json on every command (15). 20+20+20+18+15 = 93.

Sandbox0 74

Graded on the REST API and SDKs. Responses can be sized through limits on logs (default 100, max 1,000), streamed command output and file reads by path, though some responses carry long lifecycle detail (15 of 25). Cursors on logs, contexts and sessions, and limits on lists (14 of 20). Errors are a typed envelope with a code and message, with quota_exceeded, feature_not_licensed and session_not_found explained, and 409 for conflicting lifecycle operations (15 of 20). Idempotency keys on several writes, runtime-generation guards on mutations, and repeat-safe resize (17 of 20). SDKs in Go, Python and TypeScript plus the CLI, and claims need only a template name, but ttl and hard_ttl default to 0 so an idle sandbox keeps billing until told otherwise (13 of 15).

Payments & pricing boat +15

boat 45

No x402, MPP or L402 (0). Per-hour prices for each size published without login, from $0.018 an hour for small to $0.20 for xlarge, with overage and start prices (30). The 7-day trial (25 compute hours) needs a card in Stripe Checkout (0). An agent can register itself through the auth.md agent registration protocol or AgentID, but a person has to claim the agent or verify the AgentMail organisation and enter a card before a sandbox can start (15 of 30). 0+30+0+15 = 45.

Sandbox0 30

No x402, MPP or L402 in the docs, llms.txt or the OpenAPI file (0 of 40). Per-unit prices published without a login, $0.015 per GiB-hour of compute billed by the second and $0.02 per GiB-month of retained incremental storage, with network and object-store requests at $0.00 for now (20). The one-time $5 welcome credit now needs a saved card. The pricing page asks whether a card is needed for the welcome credit, answers yes and says the credit follows Stripe confirming a saved card, where on 21 October it needed none (0). Signup and the first s0 auth login are a device login a person approves in a browser. Keys can be minted by API afterwards, but only from an existing session or key (0). 0 + 20 + 0 + 0 = 20. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Schema & documentation boat +13

boat 90

A public OpenAPI 3.1 file, docs.boat.dev/openapi/boat-v1.yaml, with 123 operations, each with an operationId and a summary (25). llms.txt indexing every page and a Markdown copy of each (10). The API overview and guides say when to create, resume or fork, when to run a command detached, when to use a saved snapshot, and what each sandbox state allows (18). 86 enums and required fields in the OpenAPI file, and list calls reject unknown query parameters with 400 invalid_query (14). curl, Python and TypeScript examples, a table of error codes by status with what to do, and a retryable flag on 502s (15). Paths versioned under /v1, but no changelog was found (8 of 15). 25+10+18+14+15+8 = 90.

Sandbox0 77

OpenAPI 3.0.3 file with 106 paths and 145 operations, the same file in each SDK repository and the archived runtime. It isn't linked from the docs or served on sandbox0.ai, so an agent has to find it on GitHub (20 of 25). llms.txt and every docs page as raw Markdown at a .md address (10). Docs say when to use each lifecycle and context type, and 884 descriptions in the spec explain fields, but the pages are long and mix in internal architecture such as ctld, Nomad and PostgreSQL leases (16 of 20). 106 enums and 386 required lists in the spec; the error details field is free-form (13 of 15). Examples in Go, Python, TypeScript and CLI on every guide, but only two examples in the spec. Error responses are typed as a {code, message, details} envelope per status, with a few codes named in the docs (11 of 15). API paths are /api/v1 and the SDKs and CLI publish GitHub releases with commit lists, but there's no public changelog page; /changelog answers 404 (7 of 15).

Security & auth boat +9

boat 67

Scoped API keys with presets (read-only, full-sandbox, ci, admin), a TTL, per-sandbox limits, and documented rotation and revocation (30). Read-only and per-sandbox keys exist, but outbound traffic is open by default, the API has no network rule setting, and delete has no confirmation step (14 of 20). Each sandbox is its own VM. An AI credentials proxy keeps real model keys out of sandboxes, and a "Safe for third parties" environment strips the owner's secrets before an end user gets a sandbox (10 of 15). Per-key usage, command history and logs, and signed webhooks (9 of 15). Security reports go to support with "security" in the subject. No security.txt (404), no bug bounty, and SOC 2 is listed as in progress (4 of 20). 30+14+10+9+4 = 67.

Sandbox0 58

Bearer API keys scoped to a team, with roles admin, developer, builder and viewer that can't exceed the caller's, expiry of 30 to 365 days or never, deactivation and an introspection route. No OAuth for API clients found (25 of 30). The viewer role gives a read-only key. Network policy can block all egress, allow and deny by rule, and allow or deny named MCP tool calls, and cloud metadata endpoints are blocked under any policy. No confirmation step for destructive calls (14 of 20). Sandboxes return output of code the agent runs. Credential sources are injected by the egress proxy so raw secrets stay out of the sandbox, but no guidance on treating sandbox output as untrusted was found (8 of 15). Historical logs and runtime metrics per sandbox; the signed audit event ledger needs the enterprise sandbox_audit feature, and network audit is optional (8 of 15). No security.txt (404), no security page (404), no bug bounty, no certification and no published advisories (OSV lists none for sandbox0 on 4 November). Security reports go to contact@sandbox0.ai per the archived runtime's SUPPORT.md, and the s0 install script downloads a release without verifying a checksum (2 of 20).

Score by category

CategoryWeightboatSandbox0Edge
Reliability16%6037boat +23
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9077boat +13
Agent ergonomics13%9374boat +19
Security & auth14%6758boat +9
Payments & pricing10%4530boat +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7676even
Transparency & trust7%6947boat +22
Negative events≤1500
TotalBB 71.8/100C 56.6/100

Facts side by side

FactboatSandbox0
KindHTTP APIHTTP API
VendorDedale AI, Corp.Lougao, LLC (Sandbox0)
Hosted endpointno (local only)https://api.sandbox0.ai
TransportsHTTPHTTP
AuthAPI keyAPI key
PricingPay per usePay per use
x402nono
LicenceProprietary service under boat's terms. The TypeScript SDK @boatdev/sdk is MITProprietary hosted service under Sandbox0's terms of service (Lougao, LLC, Delaware law); the runtime is closed source since 16 October 2026. The s0 CLI and the Go, Python and TypeScript SDKs are Apache-2.0 on GitHub. The earlier Apache-2.0 runtime is an archived, unmaintained repository
Read-only variant documentedyesno
llms.txtyesyes
Last release2026-10-282026-10-30
Terms last updatedno date given2026-06-17
Privacy policy last updatedno date given2026-06-17
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 textnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularitynone88 stars, 268 npm/wk
Agent reviewsnone3/5 (4)

How the scores have moved

Verdicts

boat

boat publishes an OpenAPI 3.1 contract with 123 operations, per-hour prices, scoped expiring keys and idempotent creates for full Ubuntu VMs in the EU. It has no security.txt, SLA or readable incident history, SOC 2 is in progress, and the trial needs a card.

Sandbox0

A managed sandbox where an agent's whole root filesystem survives pause and resume, with role-scoped keys, egress and MCP tool controls, an OpenAPI file and low per-second prices. It is young and run by two contributors, with no status page, SLA or security programme, and the $5 welcome credit now needs a saved card.

Before you call either

boat

  1. Send an Idempotency-Key on every create and fork, and resend the same key and body after a timeout or 5xx
  2. Check GET /limits before a batch of starts. A retry loop does not help once the hour or day start limit is full
  3. Set detached: true for any command that may run past 30 seconds, then attach to its stream
  4. If a 502 sandbox_direct_failed has retryable false, check the command's effect before you run it again
  5. Use a read-only or per-sandbox key with a short TTL for anything that does not create sandboxes

Sandbox0

  1. Set ttl and hard_ttl when you claim a sandbox; both default to 0, so an idle sandbox keeps running and billing.
  2. Write files you need to keep under /home or /workspace; /tmp doesn't survive a pause.
  3. Back off on 429 quota_exceeded and honour Retry-After on claims. A claim has no idempotency key, so check for the sandbox before retrying one that timed out.
  4. Ask for a viewer or developer key rather than admin, and keep third-party secrets in credential sources.
  5. Ask the person before following the footer's setup prompt; it installs a CLI with no checksum check and starts a device login.

Questions

Which is better for AI agents, boat or Sandbox0?

boat scores 71.8 (BB) on agent readiness against Sandbox0's 56.6 (C), and leads in 6 of 7 scored categories.

Do boat and Sandbox0 need an API key?

Both need an API key.

Can an agent call boat and Sandbox0 without installing anything?

No hosted endpoint is listed for boat. Sandbox0 has a hosted endpoint at https://api.sandbox0.ai.

Other comparisons with boat or Sandbox0

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.