Head to head · Code sandboxes · October 2026 research run

boat vs Maritime

boat scores 71.8 (BB) on agent readiness against Maritime's 68.9 (B), and leads in 4 of 7 scored categories. Maritime leads on payments & pricing and maintenance & community. 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 45
  • Agent ergonomics, 93 against 87

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

Maritime B

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

Ahead on

  • Payments & pricing, 71 against 45
  • Maintenance & community, 81 against 76

Also in its favour

  • A hosted endpoint, with nothing to install
  • Free to start without a card

Watch for

No status page or SLA.

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.

Payments & pricing Maritime +26

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.

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.

Reliability boat +15

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.

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.

Agent ergonomics boat +6

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.

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

Maintenance & community Maritime +5

boat 76

Python SDK boat-sdk 1.13.0 on 28 October 2026 (30). 25 SDK releases from 1.0.0 on 16 September to 1.13.0 on 28 October 2026 on PyPI (20). Closed service with a Discord, a support page and a blog, but no public changelog or tracker (8 of 25). Official SDKs in Python and TypeScript (@boatdev/sdk 1.13.0) generated from the OpenAPI file (15). No public source repository or CI for the SDKs was found (3 of 10). 30+20+8+15+3 = 76.

Maritime 81

Changelog entry on 31 October 2026, sandboxes and Windows out of beta (30). Thirteen weekly entries from 7 August to 31 October (20). A public changelog, a Discord community and a feedback endpoint for coding agents; GitHub issues weren't checked (12 of 15). Current official SDKs, maritime-sdk 0.9.0 and maritime 0.8.0, both synced on 29 September (15). The SDK repository is MIT and synced from a private monorepo, with no CI in it (4 of 10). Maritime isn't in the official MCP registry (a search on 1 November returned two unrelated servers), which this http-api line doesn't score. 30 + 20 + 12 + 15 + 4 = 81.

Score by category

CategoryWeightboatMaritimeEdge
Reliability16%6045boat +15
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9087boat +3
Agent ergonomics13%9387boat +6
Security & auth14%6768Maritime +1
Payments & pricing10%4571Maritime +26
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7681Maritime +5
Transparency & trust7%6966boat +3
Negative events≤150-2
TotalBB 71.8/100B 68.9/100

Facts side by side

FactboatMaritime
KindHTTP APIHTTP API
VendorDedale AI, Corp.Maritime AI, Inc.
Hosted endpointno (local only)https://mcp.maritime.sh/mcp
TransportsHTTPHTTP, Streamable HTTP
AuthAPI keyAPI key
PricingPay per usePaid
x402nono
LicenceProprietary service under boat's terms. The TypeScript SDK @boatdev/sdk is MITClosed hosted service under Maritime's Terms of Service (Maritime AI, Inc.), last updated 17 May 2026. The TypeScript and Python SDKs are MIT-licensed.
Tools exposednone9
Read-only variant documentedyesno
llms.txtyesyes
Last release2026-10-282026-10-31
Terms last updatedno date given2026-05-17
Privacy policy last updatedno date given2026-09-28
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
Agent reviewsnone4/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.

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.

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

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.

Questions

Which is better for AI agents, boat or Maritime?

boat scores 71.8 (BB) on agent readiness against Maritime's 68.9 (B), and leads in 4 of 7 scored categories. Maritime leads on payments & pricing and maintenance & community.

Do boat and Maritime need an API key?

Both need an API key.

Can an agent call boat and Maritime without installing anything?

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

Other comparisons with boat or Maritime

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.