boat vs AWS CodeBuild
AWS CodeBuild is a CI service: each build or debug sandbox starts fresh, runs your commands and ends within 36 hours. boat gives each agent its own VM that keeps its disk, can be reached from the internet and comes with coding agents installed.
Where boat stands out
A machine that stays, not a build that ends
A boat sandbox is a full VM with its own kernel. It saves its disk every minute and at each stop, and it runs without a session cap once you turn auto-stop off. Memory and running programs are not saved, and a machine failure loses the writes after the last good snapshot. A CodeBuild build or sandbox starts from a fresh container and ends within 36 hours.
Reachable from the internet
boat gives every sandbox HTTPS URLs for up to 50 ports and raw TCP, so an agent can run an app and you or your users can open it. Every sandbox has a public IPv6 address; some have no IPv4 of their own, and the address changes on resume. CodeBuild gives builds no public IP; you reach a sandbox through SSH or Session Manager.
Coding agents installed, keys kept out
boat installs seven coding-agent harnesses in each sandbox, including Claude Code, Codex and OpenCode, and you drive them from outside with a prompt, steer and events API. Its optional AI credentials proxy ($1 a day plus $1 per 1,000 requests) keeps the real keys of supported providers out of the sandbox, and a credential can switch to another account when one runs out of credits. CodeBuild runs shell commands and passes secrets in as environment variables.
The companies and products
boat
boat.dev runs sandboxes for AI agents: each one is a full Linux VM with its own kernel.
You start a machine with one command or one API call, then SSH in, run Docker, open a desktop, or let a built-in agent (Claude Code, Codex, OpenCode and others) work in it. The disk stays between sessions, and a stopped sandbox costs nothing.
- Isolation
- Full VM per sandbox, own kernel
- Regions
- EU: Germany, Finland, France
AWS CodeBuild
AWS CodeBuild is Amazon's managed CI service: it compiles code, runs tests and builds packages inside your AWS account.
You define a build project, and each build runs in a fresh environment: by default a Linux container on hosts that CodeBuild manages, or on Lambda or reserved EC2 fleets. A debug sandbox mode lets you open an SSH session or run shell commands inside a build environment. It is built for teams that already use AWS and want builds wired into IAM, VPCs and CodePipeline. It is a different kind of product from boat, so this page compares the parts that overlap: running code an agent wrote on a remote machine.
- Kind of product
- Managed continuous integration service
Which use cases each one fits
For each use case, Battleships prices every sandbox provider on the same workload and sorts them from the cheapest monthly bill up. “5th cheapest of 365” means 4 of the other 364 providers run that workload, with every feature it needs, for less. “With limits” means the provider runs it but misses something, so it is listed after every full match. Open a use case for its whole ranking and what each provider misses.
| Use case and its workload | boat: price rank | AWS CodeBuild: price rank |
|---|---|---|
| Software factory 100 at once · 4 vCPU / 8 GB · 2,200 sessions of 8 h a month A software factory needs a machine that keeps its work between sessions. CodeBuild starts every build fresh; you set persistence up yourself with an EFS mount in a VPC or with build caches. | 5th cheapest of 365 $634 a month | 210th of 365, with limits $2,170 a month |
| Always-on AI employees 50 machines 24/7 · 2 vCPU / 4 GB Always-on assistants hit CodeBuild's 36-hour cap on every build, so they restart on a fresh machine at least every 36 hours. On boat they run without a cap once you turn auto-stop off (default 1 hour). | 6th cheapest of 361 $657 a month | 264th of 361, with limits $2,628 a month |
| Code interpreter bursts 100 at once · 1 vCPU / 2 GB · 200,000 sessions of 1 min a month CodeBuild's Lambda compute starts fast and bills per second, which suits short code runs better than boat's start limits do (the $20 plan includes 12 starts a minute and 200 a day). | 189th of 336, with limits $2,000 a month | 122nd of 336, with limits $236 a month |
| Sandboxes for your users 300 at once · 2 vCPU / 4 GB · 30,000 sessions of 23 min a month CodeBuild gives builds no public IP and its docs advise no inbound rules. To let your users open an app in a build, you set it up yourself: run a tunnel client such as cloudflared inside the build. | 3rd cheapest of 349 $209 a month | 223rd of 349, with limits $741 a month |
| RL rollouts 1,000 at once · 2 vCPU / 4 GB · 1,000,000 sessions of 3 min a month | 39th of 349, with limits $2,000 a month | 124th of 349, with limits $7,160 a month |
| Agent evals 250 at once · 4 vCPU / 8 GB · 15,000 sessions of 20 min a month | 10th cheapest of 359 $200 a month | 183rd of 359, with limits $1,680 a month |
| CI runners 40 at once · 8 vCPU / 16 GB · 6,000 sessions of 12 min a month Both fit CI: CodeBuild is a CI service with webhooks, AWS wiring and the Docker daemon on by default, and boat runs CI jobs on a full VM with Docker and /dev/kvm. | 2nd cheapest of 374 $86 a month | 44th cheapest of 374 $389 a month |
| 24/7 dev boxes 1 machine 24/7 · 4 vCPU / 8 GB | 19th cheapest of 371 $26 a month | 187th of 371, with limits $131 a month |
| Computer-use agents 50 at once · 4 vCPU / 8 GB · 20,000 sessions of 15 min a month CodeBuild's Ubuntu standard image runs headless Chrome and Firefox under Xvfb. There is no built-in desktop stream to watch or embed. boat streams a 60 fps desktop with Chrome for computer use. | 7th cheapest of 367 $200 a month | 232nd of 367, with limits $648 a month |
| Browser-use agents 50 at once · 2 vCPU / 4 GB · 30,000 sessions of 10 min a month | 7th cheapest of 356 $200 a month | 107th of 356, with limits $518 a month |
| Scraping & bots (startup scale) 50 at once · 1 vCPU / 2 GB · 100,000 sessions of 3 min a month | 6th cheapest of 343 $90 a month | 136th of 343, with limits $351 a month |
| Mass scraping & bots (undetectable) 1,000 at once · 1 vCPU / 2 GB · 3,000,000 sessions of 2 min a month | 73rd of 327, with limits $1,800 a month | 191st of 327, with limits $7,020 a month |
| Parallel red teaming 200 at once · 2 vCPU / 4 GB · 5,000 sessions of 30 min a month CodeBuild runs many builds in parallel, each from a fresh container or a cache; its API has no fork of a running build. boat forks a running sandbox from its last 1-minute snapshot. | 3rd cheapest of 351 $200 a month | 224th of 351, with limits $171 a month |
| GPU eval jobs 10 at once · 8 vCPU / 32 GB · 500 sessions of 30 min a month | Not ranked: misses a requirement | Not ranked: misses a requirement |
| macOS agents 5 at once · 4 vCPU / 8 GB · 1,000 sessions of 20 min a month CodeBuild fits and boat does not: CodeBuild rents Apple M2 Macs through reserved fleets (24-hour minimum), and boat has no macOS. | Not ranked: misses a requirement | 35th of 35, with limits $4,380 a month |
Key features
| Feature | boat | AWS CodeBuild |
|---|---|---|
| Kind of product | Cloud VMs for agents: each one keeps its disk, runs as long as you set and can host services | CI builds and short debug sandboxes inside your AWS account |
| Isolation | Every sandbox is a full VM with its own kernel | Linux container on CodeBuild-managed hosts by default; EC2 instances in reserved fleets (60-minute minimum) |
| Docker and nested virtualization | Docker, root, systemd and /dev/kvm on every sandbox | Docker daemon on by default (privileged mode for VPC builds; not on Windows or Lambda); no /dev/kvm documented |
| How long one session runs | No session cap once auto-stop is off (default 1 hour; up to 30 days or off on paid plans) | 36 hours at most per build or sandbox |
| Files after a stop | Disk saved every minute and at each stop, kept at least 14 days; memory and running programs are not saved | Each build starts fresh. You set it up: an EFS mount in a VPC (billed by EFS), or S3 and local build caches for chosen paths |
| Pause, resume and fork | Stop and resume from disk; fork a running sandbox from its last 1-minute snapshot | Start and stop builds and sandboxes; the API documents no resume or fork |
| Reaching the sandbox | HTTPS URLs for up to 50 ports, token-protected; raw TCP to a public IPv6, or IPv4 where the sandbox has one (the address changes on resume) | SSH or Session Manager into a sandbox; builds get no public IP. You set it up: a tunnel client such as cloudflared in the build |
| Outbound internet | Open internet on every plan; no provider-side allowlist | Open by default; domain or IP allow and deny rules on reserved fleets, or VPC security groups |
| Keeping keys out of the sandbox | Optional AI credentials proxy ($1 a day it is on, plus $1 per 1,000 requests): real keys of supported model providers and registered HTTPS APIs stay outside; other secrets still enter as environment variables | Secrets Manager and Parameter Store values are put into the build as environment variables |
| Coding agents | Seven harnesses installed, including Claude Code, Codex and OpenCode, with a prompt, steer and events API | None built in. You set it up: install an agent CLI and run it through the sandbox's shell commands |
| Desktop and computer use | 1920x1080, 60 fps desktop and Chrome stream, computer tools for agents, embeddable stream | Ubuntu standard images include Chrome, Firefox and Xvfb for headless browser runs. No built-in desktop stream to watch or embed: access is a shell over SSH or Session Manager |
| Custom images | Start from boat's image or a saved snapshot; you cannot boot your own Docker or OCI image | Any Docker image from Amazon ECR, Docker Hub or another registry |
| Windows, macOS and GPUs | Linux only; Windows programs run through Wine; no GPU on any size | Windows builds, Apple M2 Macs and Linux GPU machines |
| Regions | Machines in Germany, Finland and France; no US or Asia region, and you cannot pick one | Most AWS regions worldwide, eight of them in Europe |
| Compliance and transparency | SOC 2 is in progress. We're open about where we stand: live status and data retention policy. | SOC 2 |
Every feature Battleships tracks (43)
| Feature | boat | AWS CodeBuild |
|---|---|---|
| Full VM (own kernel) | Yes | No documented way |
| Docker inside | Yes | Yes |
| Nested virtualization | Yes | No documented way |
| Root | Yes | Yes |
| Systemd | Yes | Not published |
| Desktop GUI | Yes | No documented way |
| Browser | Yes | Yes |
| Computer-use API | Yes | No documented way |
| SSH | Yes | Yes |
| Persistent disk | Yes | Yes |
| Pause/resume | Yes | No documented way |
| Automatic snapshots | Yes | No documented way |
| Fork/clone | Yes | No documented way |
| Live fork (no pause) | Yes | No documented way |
| Memory fork | No documented way | No documented way |
| Custom image (Docker or snapshot) | Yes | Yes |
| ≥24 h sessions | Yes | Yes |
| Idle auto-stop | No documented way | Yes |
| Wake on request | No documented way | No documented way |
| HTTPS preview URLs | Yes | No documented way |
| Raw TCP inbound | Yes | No documented way |
| Public IPv4 | No documented way | No documented way |
| Egress allowlist | No documented way | Yes |
| Secret proxy | Yes | No documented way |
| Secret proxy for any API | Yes | No documented way |
| Preinstalled agents | Yes | No documented way |
| Agent harness API | Yes | No documented way |
| MCP server | No documented way | No documented way |
| GPU | No documented way | Yes |
| Windows | No documented way | Yes |
| Arm64 | No documented way | Yes |
| Self-hosting | No documented way | Yes |
| BYOC | No documented way | No documented way |
| Open source | No documented way | No documented way |
| Scoped API keys | Yes | Not published |
| Spend limits | Yes | Not published |
| Usage per sandbox (API) | Yes | Yes |
| Audit logs | No documented way | Not published |
| SSO | No documented way | Yes |
| SOC 2 | No documented way | Yes |
| HIPAA | No documented way | Yes |
| EU data residency | No documented way | Yes |
| Zero data retention | Yes | Not published |
Performance
AWS CodeBuild is not in the public benchmarks we use, so we cannot say which is faster. In StarSling's run of 3 October 2026 (run 37073680030), a 4 vCPU / 8 GB boat sandbox did 28.06 runs/s on the V8 Web Tooling Benchmark, second of 15. That sandbox ran on an AMD Ryzen 9 9950X host; boat also places sandboxes on Ryzen 7 9700X hosts and does not promise a CPU model.
V8 Web Tooling Benchmark at a 4 vCPU / 8 GB target, runs per second, higher is better. Source: StarSling's run of 3 October 2026 (run 37073680030), median of 5 sandboxes. Providers ran on different hardware in different regions. StarSling gives a shared rank when the run cannot separate two providers. Every boat sandbox in this run ran on an AMD Ryzen 9 9950X host. boat also places some sandboxes on AMD Ryzen 7 9700X hosts, which this run did not measure. AWS CodeBuild is not in the public benchmarks we use, so we cannot say which is faster.
Pricing in five scenarios
Each bill is priced from the providers' public price lists by the open Battleships engine, with the cheapest plan that runs the scenario. Start limits, per-start fees and plan minimums are in the price, boat's included.
| Scenario | boat, a month | AWS CodeBuild, a month |
|---|---|---|
| One coding agent, workdays 4 vCPU / 8 GB, 50 GB disk, 8 hours a day, 22 days a month, files kept between days | $20 · $20/mo | $29 · Pay as you go · with limits |
| One agent that never stops 4 vCPU / 8 GB, 50 GB disk, running 24/7 all month | $26 · $20/mo | $131 · Pay as you go · with limits |
| 50 agents in parallel 50 machines of 4 vCPU / 8 GB at once, 8-hour sessions, 1,100 sessions a month, Docker inside | $317 · $20/mo × 3 seats | $1,426 · Pay as you go · with limits |
| Sandboxes for your users 2 vCPU / 4 GB, 30,000 sessions of 10 minutes a month, up to 300 at once | $200 · $100/mo × 2 seats | $324 · Pay as you go · with limits |
| 1,000 short jobs at once 2 vCPU / 4 GB, 1,000 at once, 3 minutes each, 200,000 jobs a month | $8,800 · $2000/mo · with limits | $716 · Pay as you go · with limits |
boat: Plans cost $20, $100, $500 or $2,000 a month. The whole plan price comes back as VM time for that month, billed per second while a sandbox runs, busy or idle: $0.036 an hour for 4 vCPU / 8 GB. Included time expires at the end of the month; money you add to the wallet does not. A card is required, also for the 7-day trial. A stopped sandbox has no compute charge, but saved snapshots above the plan's count and the AI credentials proxy still charge. Starts above the plan's included number cost $0.03 to $0.07 each.
AWS CodeBuild: CodeBuild has no plan fee. Builds bill per minute, rounded up, from submission to end; debug sandboxes and Lambda builds bill per second; reserved fleets bill per instance-minute with a 60-minute minimum, and a Mac has a 24-hour minimum. Logs in CloudWatch, artifacts in S3, EFS storage and data transfer are billed on top. A free tier that does not expire gives 100 build minutes and 6,000 Lambda build seconds a month; sandboxes and reserved fleets are not included.
Limits in those scenarios
CodeBuild is a CI runner, so we mark every scenario as not a clean fit: files survive only in an EFS mount or a cache you set up, and anything installed elsewhere resets on the next run. Egress has no published price, so our bills leave it out. The agent that never stops also hits the 36-hour cap on each build. AWS's quota table lists one running build for most compute types, with a note that some start at 20, so 50 agents in parallel need a Service Quotas increase first. On boat, the 1,000-job burst needs about 6,667 starts a day and 1,000 an hour; the $2,000 plan includes 2,400 a day, 600 an hour and 90 a minute, extra starts are paid, and starts above 270 a minute fail with 429. boat never queues a start. A stopped boat sandbox keeps its disk for at least 14 days; after that only a saved snapshot keeps it. If a machine fails, you lose what was written after the last good snapshot.
| Scenario | boat | AWS CodeBuild |
|---|---|---|
| One coding agent, workdays | None for this scenario |
|
| One agent that never stops | None for this scenario |
|
| 50 agents in parallel | None for this scenario |
|
| Sandboxes for your users | None for this scenario |
|
| 1,000 short jobs at once |
|
|
boat's own limits
- Plans start at $20 a month. The plan price comes back as VM time for that month. Unused time does not carry over. Source
- Starts (create, fork, resume): the $20 plan includes 12 a minute, 60 an hour and 200 a day. The $2,000 plan includes 90 a minute, 600 an hour and 2,400 a day. Extra starts cost $0.03 to $0.07. A start fails with 429 above 3 times the included starts per minute, or 6 times per hour or per day. Source
- A stopped sandbox has no compute charge. boat keeps its disk for at least 14 days. A saved snapshot keeps it longer; extra saved snapshots and the AI credentials proxy are paid. Source
- Auto-stop defaults to 1 hour. You can turn it off on a paid plan. The trial allows 2 hours at most. Source
- boat saves the disk every minute and at each stop. Memory, running programs and /tmp are not saved: a resume is like a reboot. A machine failure loses writes after the last good snapshot. Source
- Machines run in Germany, Finland and France only. Snapshot copies can be stored outside the EU. Source
- Public IPv6 and outbound IPv4. No dedicated IPv4. The IP changes at each resume. Source
- Hosts are AMD Ryzen 7 9700X and Ryzen 9 9950X. vCPUs are shared. No GPU. You cannot boot your own Docker image. Source
Which one should you use?
Use AWS CodeBuild when
you need CI builds inside your AWS account, builds on Windows, macOS or GPUs, or a region outside the EU.
- Windows, macOS and GPU builds. Useful if you build for Windows, iOS or macOS, or need a GPU: CodeBuild runs Windows, Apple M2 and Linux GPU machines.
- Part of your AWS account. Useful if your stack lives on AWS: builds reach private VPC resources and use IAM, CodePipeline and many regions worldwide.
- Network rules for builds. Useful if builds must reach only approved hosts: reserved fleets can deny all traffic and allow chosen domains or IPs.
- A free tier and no plan fee. Useful for light or occasional builds: CodeBuild has no plan fee and a free tier with no end date.
Use boat when
your agents need a machine of their own: a full VM that saves its disk every minute, runs as long as you set, serves apps to the internet and comes with coding agents installed.
- A machine that stays, not a build that ends. An agent installs tools and edits a repo. On CodeBuild you set persistence up yourself: an EFS mount in a VPC keeps one folder, and build caches keep chosen paths. Everything else resets on the next run.
- Reachable from the internet. An agent that builds a web app needs someone to open it. CodeBuild gives builds no public IP, so previews and webhooks need a tunnel or another service in front.
- Coding agents installed, keys kept out. With secrets as environment variables, code an agent wrote can read and leak the key. Without a driving API you write and maintain the code that starts, prompts and watches each agent yourself.
Questions people ask
Is boat cheaper than AWS CodeBuild?
In 4 of the 5 scenarios we priced, yes; CodeBuild is a CI runner and fits none of them cleanly. One coding agent on workdays comes to $20 a month on boat and $29 on CodeBuild, one agent running all month to $26 versus $131, and 50 agents in parallel to $317 versus $1,426. Sandboxes for your users come to $200 versus $324. For 1,000 short jobs at once, boat costs more: $8,800 versus $716, because the job needs more starts than the $2,000 plan includes. Egress is not in CodeBuild's bills because it has no published price.
Can I run an AI coding agent in a CodeBuild sandbox?
Yes, you set it up: install the agent and run it with shell commands. The sandbox is made for debugging builds. It starts fresh, ends within 36 hours and gets no public IP, and it keeps files only in an EFS mount or a cache you configure. boat installs the agents and lets you drive them with a prompt, steer and events API.
Do CodeBuild builds run in a VM or a container?
By default a CodeBuild build runs as a Linux container on hosts CodeBuild manages. Reserved fleets run on EC2 instances, and Lambda compute runs without root or Docker. On boat, every sandbox is a full VM with its own kernel, root, systemd, Docker and /dev/kvm.
Does boat run Windows, macOS or GPU builds like CodeBuild?
No. boat runs Linux VMs, with Wine for Windows programs and no GPU on any size. For Windows, Apple M2 or GPU builds, use CodeBuild.
Where does my data run?
boat sandboxes run on machines in Germany, Finland and France, and you cannot pick a region. Snapshot copies can be stored outside the EU. CodeBuild runs in the AWS region you choose, which includes eight regions in Europe and many more worldwide.
Is boat SOC 2 compliant?
No, SOC 2 is in progress, and boat documents no HIPAA BAA. boat measures 99.95% sandbox uptime and publishes no SLA. Live status is at status.ascii.dev and the data retention policy at docs.boat.dev/data-retention. AWS publishes CodeBuild's compliance programs and audit reports through AWS Artifact.
Start a sandbox
Install the CLI, then run boat new.
7-day free trial