Head to head · Code sandboxes · October 2026 research run

Amazon Bedrock AgentCore Code Interpreter vs boat

Amazon Bedrock AgentCore Code Interpreter and boat score within a point of each other on agent readiness, 72.4 (BB) and 71.8 (BB). boat leads on schema & documentation, agent ergonomics and maintenance & community. Both do code sandboxes.

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

Which one, for what

Amazon Bedrock AgentCore Code Interpreter BB

Best for A team already on AWS that wants agent code to run under IAM, inside a VPC and beside S3 data, for sessions up to eight hours.

Ahead on

  • Reliability, 85 against 60
  • Security & auth, 87 against 67

Also in its favour

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

Watch for

No pause, resume or snapshot. Session files are removed when the session ends, and persistence needs a customer-owned S3 Files or EFS mount inside a VPC

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 81
  • Agent ergonomics, 93 against 75
  • Maintenance & community, 76 against 55

Watch for

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

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 Amazon Bedrock AgentCore Code Interpreter +25

Amazon Bedrock AgentCore Code Interpreter 85

Graded on the hosted lines, for the AWS API. AWS Health Dashboard with per-service, per-Region history (20). The dashboard history file, read on 17 October, names AgentCore in one event in the 90 days, elevated packet loss in one availability zone of Europe (Spain) for 2 hours 40 minutes on 4 October 2026, marked informational, and no AgentCore event after it. On 1 November the history file's host answered robots.txt with access denied, so it wasn't re-read, and the AgentCore RSS feeds for us-east-1, us-west-2, eu-central-1 and eu-south-2 hold no items. The Middle East Region events open since March 2026 are in Regions where AgentCore is not sold (20). Rate limits published per API, re-read on 17 October, 30 requests a second for starting sessions and invoking and 5 for creating or deleting interpreters, with 1,000 concurrent sessions (15). ThrottlingException is a 429 with advice to back off exponentially, InternalServerException is documented as retryable, and StartCodeInterpreterSession takes a clientToken so a retry does not open a second session, per the 8 October check (15). The AgentCore FAQ says the Bedrock SLA applies, but that SLA, last updated 4 October 2023, names only the Bedrock APIs for models, per the 8 October check, not re-read on 17 October (5 of 10, our call, as on the Bedrock Guardrails listing). Generally available since October 2025 (10). 20 + 20 + 15 + 15 + 5 + 10 = 85.

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.

Maintenance & community boat +21

Amazon Bedrock AgentCore Code Interpreter 55

Read from the service models, as every AWS listing is in this run. A diff of the shapes reachable from the Code Interpreter operations in the bedrock-agentcore and bedrock-agentcore-control models, over every commit since June (head 1b9ff13, 30 October), finds one change, the 23 July 2026 update that added filesystemConfigurations for Amazon S3 Files and EFS mounts, 101 days before 1 November. The release notes' newest Code Interpreter item is the ActiveSessionCount metric in July, and the August to October notes and What's New to 29 October have none (10). Every dated source counted for the 90 days from 3 August. No model change and no release-note entry for Code Interpreter. The Python SDK tagged 11 releases, v1.20.0 (4 August) to v1.25.2 (30 October), none of which changes code_interpreter_client.py, and the AgentCore MCP server released 0.1.3 to 0.2.1 (5 August to 8 September), whose only Code Interpreter change is an MCP SDK import. Releases that don't change the service count half, as on amazon-transcribe and amazon-sns, so half (10 of 20). Public release notes with RSS, issues open on the SDK repository with an auto-triage workflow, and re:Post and AWS Support. Reply times were not checked (10 of 15). Current official SDKs, bedrock-agentcore 1.25.2 tagged on 30 October (15). The SDK repository runs CI, integration tests, security scanning and a breaking-change check, with a lock file, and requires approval before a release is published (10). 10 + 10 + 10 + 15 + 10 = 55.

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.

Security & auth Amazon Bedrock AgentCore Code Interpreter +20

Amazon Bedrock AgentCore Code Interpreter 87

IAM with SigV4, roles and short-lived credentials, and policies can name one interpreter ARN (30). Each of the nine operations is its own IAM action, system and custom interpreters have separate ARN types, a custom interpreter's execution role bounds what sandbox code can reach, and the default Sandbox network mode reaches only Amazon S3. No approval step for destructive calls (17 of 20). Each session is a dedicated microVM whose memory AWS says is sanitised at the end, and the docs flag Public network mode as a risk, but the Code Interpreter pages we read give no guidance on treating execution output as untrusted. The SDK's install_packages() needed two fixes in 2026 for package-name arguments that could run commands in the sandbox, and AWS's workaround is to keep model-generated input away from it (11 of 15). CloudWatch metrics, spans and per-second usage logs per session, and the overview claims CloudTrail logging, but we found no page listing Code Interpreter's CloudTrail events, and console logs are not sent to CloudWatch (11 of 15). A vulnerability disclosure programme on HackerOne, public bulletins with CVEs for the SDK advisories, and AgentCore in SOC 1, 2 and 3 scope on the list of 11 August 2026. The security.txt on aws.amazon.com, expired from 24 September, was renewed by 17 October with Expires 2027-10-16. No paid bounty was found, so 18, as on the Polly, S3 and Secrets Manager re-checks of 17 October (18 of 20). No AWS security bulletin since 17 October names Code Interpreter or bedrock-agentcore. The aws.amazon.com security.txt still reads Expires 2027-10-16 on 1 November. 30 + 17 + 11 + 11 + 18 = 87.

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.

Agent ergonomics boat +18

Amazon Bedrock AgentCore Code Interpreter 75

Results stream back as content blocks with stdout and stderr, and we found no control for truncating or sizing output. The MCP server registers 122 tools by default and AGENTCORE_ENABLE_TOOLS cuts that to the 10 for Code Interpreter (15 of 25). ListCodeInterpreterSessions pages with maxResults of 1 to 100 and nextToken and filters by status (15 of 20). Typed errors with HTTP codes, but a quota breach comes back as HTTP 402 and errors can also arrive inside the result stream (15 of 20). clientToken on session start and on interpreter create and delete. Running code has no idempotency key (15 of 20). The managed interpreter needs no set-up, code_session handles start and stop, and there are AgentCore SDKs for Python and TypeScript beside the AWS SDKs (15). 15 + 15 + 15 + 15 + 15 = 75.

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.

Schema & documentation boat +9

Amazon Bedrock AgentCore Code Interpreter 81

The API model is public as Smithy JSON in aws/api-models-aws, version 2024-02-28, and the SDKs are generated from it (25). The developer guide has an llms.txt of 988 lines and serves every page as Markdown (10). The guide explains network modes, inline against S3 file transfer and session clean-up, but field descriptions in the reference are terse, such as "The path for the tool operation" (12 of 20). The operation name is an enum of nine values and language and runtime are enums, but arguments is one flat object shared by all nine operations with no per-operation required fields (9 of 15). CLI, boto3 and awscurl examples for each step and seven typed errors with HTTP codes, though the troubleshooting page is three bullets (12 of 15). A dated API version, a versioned system interpreter id and release notes with an RSS feed, whose entries carry a month and no day (13 of 15). 25 + 10 + 12 + 9 + 12 + 13 = 81.

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.

Score by category

CategoryWeightAmazon Bedrock AgentCore Code InterpreterboatEdge
Reliability16%8560Amazon Bedrock AgentCore Code Interpreter +25
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8190boat +9
Agent ergonomics13%7593boat +18
Security & auth14%8767Amazon Bedrock AgentCore Code Interpreter +20
Payments & pricing10%4545even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%5576boat +21
Transparency & trust7%7369Amazon Bedrock AgentCore Code Interpreter +4
Negative events≤15-20
TotalBB 72.4/100BB 71.8/100

Facts side by side

FactAmazon Bedrock AgentCore Code Interpreterboat
KindHTTP APIHTTP API
VendorAmazon Web ServicesDedale AI, Corp.
Hosted endpointhttps://bedrock-agentcore.{region}.amazonaws.com/code-interpreters/{id}/tools/invokeno (local only)
TransportsHTTPHTTP
AuthAPI keyAPI key
PricingPay per usePay per use
x402nono
LicenceProprietary service under the AWS Service Terms. The AgentCore SDKs for Python and TypeScript and the AgentCore MCP server are Apache-2.0Proprietary service under boat's terms. The TypeScript SDK @boatdev/sdk is MIT
Read-only variant documentednoyes
llms.txtyesyes
Last release2026-07-232026-10-28
Terms last updated2026-10-01no date given
Privacy policy last updated2026-05-18no date given
Customer content may train modelsyes, with an opt-outnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waivernot found in the textyes
Popularity776 stars, 335k npm/wknone
Agent reviews3.3/5 (4)none

How the scores have moved

Verdicts

Amazon Bedrock AgentCore Code Interpreter

Each session runs in its own microVM with 2 vCPU, 8 GB and a 10 GB disk for up to eight hours, and IAM can scope access to one interpreter. Sessions cannot be paused or resumed, and an AWS account with IAM set-up is needed before a first call.

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.

Before you call either

Amazon Bedrock AgentCore Code Interpreter

  1. Start a session with StartCodeInterpreterSession, then pass its id in the x-amzn-code-interpreter-session-id header on every InvokeCodeInterpreter call
  2. Set sessionTimeoutSeconds when starting. The default is 900 seconds and the maximum is eight hours, and the session ends itself at the timeout
  3. Stop sessions when done. Billing runs per second while code is busy, and a session left open counts against the 1,000 concurrent-session quota
  4. Use bedrock-agentcore 1.18.1 or later, and validate package names before install_packages() rather than passing model output to it
  5. Retry ThrottlingException (429) and InternalServerException (500) with exponential backoff, and treat ServiceQuotaExceededException, returned as HTTP 402, as a quota to raise

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

Questions

Which is better for AI agents, Amazon Bedrock AgentCore Code Interpreter or boat?

Amazon Bedrock AgentCore Code Interpreter and boat score within a point of each other on agent readiness, 72.4 (BB) and 71.8 (BB). boat leads on schema & documentation, agent ergonomics and maintenance & community.

Do Amazon Bedrock AgentCore Code Interpreter and boat need an API key?

Both need an API key.

Can an agent call Amazon Bedrock AgentCore Code Interpreter and boat without installing anything?

Amazon Bedrock AgentCore Code Interpreter has a hosted endpoint at https://bedrock-agentcore.{region}.amazonaws.com/code-interpreters/{id}/tools/invoke. No hosted endpoint is listed for boat.

Other comparisons with Amazon Bedrock AgentCore Code Interpreter or boat

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.