Head to head · Code sandboxes · October 2026 research run

boat vs Sprites

boat scores 71.8 (BB) on agent readiness against Sprites's 68 (B), and leads in 4 of 7 scored categories. Sprites leads on reliability and payments & pricing. 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

  • Schema & documentation, 90 against 74
  • Agent ergonomics, 93 against 68
  • Security & auth, 67 against 61

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

Sprites B

Best for Agents that need a long-lived machine with installed tools and files kept between sessions, and rollback by checkpoint.

Ahead on

  • Reliability, 80 against 60
  • Payments & pricing, 60 against 45

Watch for

Five partial Sprites incidents on the status page since 30 August 2026, including 7 hours 28 minutes of intermittent API failures on 23 September and 75 minutes of unreachable Sprite URLs on 11 October

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.

Agent ergonomics boat +25

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.

Sprites 68

List calls take max_results, and service logs take lines and duration. Exec returns command output directly, with a WebSocket route for streaming (17). Sprite lists page with continuation_token and filter by prefix (16). Status codes are listed per operation and the SDKs raise typed errors with a machine code, but no code list is published (10). No idempotency keys. Service creation is a PUT by name and Sprite names are unique per organisation, and the hosted MCP server marks tools as read-only or destructive (10). Creating a Sprite needs only a name, and there are official SDKs in four languages and a CLI (15).

Reliability Sprites +20

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.

Sprites 80

Hosted lines. status.flyio.net runs on incident.io with history and a Sprites component (20). Five Sprites incidents since 6 August, each partial in its own text, so minor under this run's reading. Deletion jobs failed for 47 minutes on 30 August, "a subset of Sprites users" had API errors for 1 hour 38 minutes on 2 September, intermittent API failures starting near SJC ran 7 hours 28 minutes on 23 September, creates failed in regions outside Europe for 28 minutes on 8 October, and "some or all" Sprite URLs on sprites.app were unavailable for about 75 minutes on 11 October after a certificate error (20; was 5, which isn't a checklist value). The product page gives creation limits of 10 a minute on pay-as-you-go and 60 to 240 on plans, and 100 running Sprites on the Hero plan. No general request limits were found in the docs (10). The docs and the OpenAPI document list no 429 response and no idempotency keys; the Go SDK reads Retry-After and X-RateLimit headers on a 429 and names a sprite_creation_rate_limited code, so Retry-After handling alone (10; was 7). Fly.io's published Service Level Agreement applies to the Services for customers on an Enterprise plan, with 99.9 per cent monthly availability and service credits of 10 to 30 per cent, and excludes no product, so it is read as covering Sprites (10; was 5, which isn't a checklist value). No beta or preview label was found on Sprites, so the surface is read as generally available, though the API document is version 0.1.12 and the SDKs are 0.x (10; was 8, which isn't a checklist value). 20 + 20 + 10 + 10 + 10 + 10 = 80.

Schema & documentation boat +16

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.

Sprites 74

A public OpenAPI 3.1 document with 44 operations and 59 schemas, plus an AsyncAPI file for the WebSocket calls (25). llms.txt and a Markdown copy of every docs page (10). Concept pages say when to use Services, Tasks and checkpoints and when not to, while operation descriptions are one line each (15). Request bodies have required fields and examples, but the document has 6 enums and no schema for error bodies (10). 116 examples in the OpenAPI document. Error responses are a status code and a short phrase, and the product page's create and exec examples disagree with the OpenAPI document (8). Paths are versioned under /v1. No API changelog was found, and only the Python SDK keeps a changelog file (6).

Payments & pricing Sprites +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.

Sprites 60

No x402, MPP or L402 (0). Unit prices are public without a login, $0.0385 a CPU-hour, $0.021875 a GB-hour of memory, $0.000683 a GB-hour of hot storage and $0.000027 a GB-hour of cold storage (20). The product page and the pricing page now say every new user gets a $1 free trial with no credit card, invoices under $5 are waived, and new organisations get a $30 trial credit (20; was 10). A person signs up with a Fly.io account in a browser and creates the token (0). 0 + 20 + 20 + 0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Security & auth boat +6

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.

Sprites 61

Bearer tokens are created and removed at sprites.dev/account per organisation, with no scopes found. The MCP connector uses OAuth, and its default token can only create a capped number of Sprites under a name prefix (22). Sprite URLs are private by default, Connectors deny by default and can limit provider paths, and a privileges policy can drop capabilities. The network allowlist is opt-in, so egress is open by default (15). Connectors keep provider credentials out of the Sprite and the MCP page describes what its tools can destroy. No prompt-injection guidance was found (9). No audit log of API calls was found in the reviewed documentation (0). fly.io now publishes a security.txt (Contact security@fly.io, Expires 2027-10-22, Policy docs.fly.io/security), and the policy says reports are acknowledged within 3 business days. SOC 2 Type 2 and named third-party penetration testers. No bug bounty, which the policy confirms, and no advisories for the Sprites SDKs in OSV (15; was 13). 22 + 15 + 9 + 0 + 15 = 61.

Score by category

CategoryWeightboatSpritesEdge
Reliability16%6080Sprites +20
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9074boat +16
Agent ergonomics13%9368boat +25
Security & auth14%6761boat +6
Payments & pricing10%4560Sprites +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7680Sprites +4
Transparency & trust7%6966boat +3
Negative events≤150-2
TotalBB 71.8/100B 68/100

Facts side by side

FactboatSprites
KindHTTP APIHTTP API
VendorDedale AI, Corp.Fly.io
Hosted endpointno (local only)no (local only)
TransportsHTTPHTTP
AuthAPI keyAPI key
PricingPay per usePay per use
x402nono
LicenceProprietary service under boat's terms. The TypeScript SDK @boatdev/sdk is MITProprietary service under the Fly.io Terms of Service. The JavaScript, Go, Python and Elixir SDKs are MIT
Read-only variant documentedyesyes
llms.txtyesyes
Last release2026-10-282026-10-20
Terms last updatedno date given2026-04-29
Privacy policy last updatedno date given2026-09-24
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
Popularitynone158k npm/wk, 59k PyPI/wk

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.

Sprites

A Sprite keeps a 100 GB ext4 disk between runs, bills compute only while active and can be checkpointed and restored through a published OpenAPI contract. The status page records five partial Sprites incidents since August, one lasting over seven hours, and outbound network access is unrestricted until a policy is set.

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

Sprites

  1. Create a token at sprites.dev/account after a browser signup, and send it as Authorization: Bearer <token> to https://api.sprites.dev
  2. Follow the OpenAPI document, not the product page example. Create with POST /v1/sprites and a JSON name, and run commands with POST /v1/sprites/{name}/exec using cmd query parameters
  3. Set a network policy with POST /v1/sprites/{name}/policy/network before running untrusted code. Egress is open until one is set
  4. Processes started by exec stop on a cold wake. Define a Service for anything that must answer the request that wakes the Sprite
  5. Create a checkpoint before a restore. Restoring replaces the filesystem, ends active sessions and keeps no copy of the replaced state
  6. Sprite creation is limited to 10 a minute on pay-as-you-go. The Go SDK reads Retry-After and the error code sprite_creation_rate_limited on a 429
  7. Delete Sprites you no longer need. An idle Sprite still bills cold storage for the bytes it holds
  8. Set SPRITES_CLIENT_SIGNALS=0 before the first SDK call if your operator doesn't want client-signal headers sent

Questions

Which is better for AI agents, boat or Sprites?

boat scores 71.8 (BB) on agent readiness against Sprites's 68 (B), and leads in 4 of 7 scored categories. Sprites leads on reliability and payments & pricing.

Do boat and Sprites need an API key?

Both need an API key.

Can an agent call boat and Sprites without installing anything?

No hosted endpoint is listed for boat. No hosted endpoint is listed for Sprites.

Other comparisons with boat or Sprites

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.