boat vs Civo
A Civo Compute instance is a general Linux VM that you set up and run yourself. Civo bills it by the hour, also while it is stopped. boat gives an agent a full VM too, with disk snapshots every minute, no compute charge while stopped, fork, HTTPS ports, a desktop and coding agents already installed.
Where boat stands out
A disk saved every minute, and fork while running
boat saves a sandbox's disk every minute while it runs and once more at each stop. A stopped sandbox has no compute charge, and boat keeps its disk for at least 14 days. You can fork a running sandbox in one call. Memory and running programs are not saved, and a fork can miss the last minute of writes. A stopped Civo instance is billed the same as a running one, and its snapshot API is documented for CivoStack Enterprise private regions where it is enabled.
Coding agents and a desktop built in
Every boat sandbox has seven coding-agent harnesses installed, including Claude Code, Codex and OpenCode. You drive them from outside with a prompt, steer and events API. It also streams a 1920x1080, 60 fps desktop with Chrome for computer use. The optional paid credentials proxy keeps real AI keys out of the sandbox and can switch to another account when one runs out of credits.
HTTPS on up to 50 ports, no setup
Each boat sandbox can serve up to 50 ports on HTTPS URLs, token-gated by default. A Civo instance has a fixed public IPv4 and any port you open in its firewall. For HTTPS you run your own proxy and certificates or add a load balancer.
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
Civo
Civo is a general-purpose cloud, and Civo Compute is its service for Linux virtual machines, called instances.
A Civo instance is a Linux VM you rent by size, with root, NVMe storage, a public IP and free data transfer. Civo runs this compute layer next to its managed Kubernetes, load balancers, firewalls, block and object storage and GPU machines. It is a server host, not an agent sandbox, so this page compares the two where they overlap: giving an agent its own Linux machine.
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 | Civo: price rank |
|---|---|---|
| Software factory 100 at once · 4 vCPU / 8 GB · 2,200 sessions of 8 h a month Both give a full Linux VM with root and Docker. A Civo instance starts as a plain server and bills while stopped. A boat sandbox comes with agents and snapshots, and has no compute charge while stopped. | 5th cheapest of 365 $634 a month | 148th of 365, with limits $1,048 a month |
| Always-on AI employees 50 machines 24/7 · 2 vCPU / 4 GB A Civo instance can run an assistant around the clock. You set up the agent, the HTTPS endpoint and the backups yourself. boat has them built in, but you must turn auto-stop off (default 1 hour). | 6th cheapest of 361 $657 a month | 209th of 361, with limits $1,086 a month |
| Code interpreter bursts 100 at once · 1 vCPU / 2 GB · 200,000 sessions of 1 min a month Neither fits short runs well. Civo bills every started hour in full, so a one-minute job costs an hour. boat's $20 plan includes 12 starts a minute and 200 a day, and extra starts cost $0.03 to $0.07. | 189th of 336, with limits $2,000 a month | 174th of 336, with limits $1,086 a month |
| Sandboxes for your users 300 at once · 2 vCPU / 4 GB · 30,000 sessions of 23 min a month Civo accounts start at a basic quota that Civo raises on request after a period of use, so hundreds of user sandboxes need a quota review first. boat allows 100 to 2,000 sandboxes at once by plan, with start limits per minute, hour and day. | 3rd cheapest of 349 $209 a month | 102nd of 349, with limits $893 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 | 187th of 349, with limits $21,726 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 | 64th cheapest of 359 $893 a month |
| CI runners 40 at once · 8 vCPU / 16 GB · 6,000 sessions of 12 min a month Both run Docker builds on a full VM. On Civo each job is billed up to a full hour, and you set up the runner and the clean-up between jobs. On boat each job counts as a start against the plan's start limits. | 2nd cheapest of 374 $86 a month | 115th cheapest of 374 $1,161 a month |
| 24/7 dev boxes 1 machine 24/7 · 4 vCPU / 8 GB Both fit a 24/7 dev box. A Civo instance is a classic always-on server that keeps its public IP. A boat sandbox keeps its disk with snapshots every minute, but its IP changes at each resume. | 19th cheapest of 371 $26 a month | 36th cheapest of 371 $43 a month |
| Computer-use agents 50 at once · 4 vCPU / 8 GB · 20,000 sessions of 15 min a month boat streams a 1920x1080, 60 fps desktop with Chrome and computer-use tools. On Civo you set it up: install a desktop environment and a VNC or RDP server on the instance. | 7th cheapest of 367 $200 a month | 281st of 367, with limits $1,190 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 | 322nd of 356, with limits $893 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 | 243rd of 343, with limits $89 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 | 70th of 327, with limits $1,786 a month |
| Parallel red teaming 200 at once · 2 vCPU / 4 GB · 5,000 sessions of 30 min a month | 3rd cheapest of 351 $200 a month | 211th of 351, with limits $149 a month |
| GPU eval jobs 10 at once · 8 vCPU / 32 GB · 500 sessions of 30 min a month Civo fits: it rents Nvidia GPU machines by the hour. boat has no GPU on any size. | 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 | Not ranked: misses a requirement | Not ranked: misses a requirement |
Key features
| Feature | boat | Civo |
|---|---|---|
| What you get | A sandbox API for agents, on full VMs | A general Linux VM you set up and run yourself |
| Isolation | Every sandbox is a full VM with its own kernel | Every instance is a full VM |
| CPU | Shared vCPUs on AMD Ryzen 7 9700X and Ryzen 9 9950X hosts; 28.06 runs/s at 4 vCPU / 8 GB on a 9950X host (StarSling, 3 October 2026) | CPU model not published; not in the public benchmarks we use |
| Sizes and disk | 4 sizes, 2 to 16 vCPU and 4 to 32 GB; disk fixed per size, 51 to 251 GB | Sizes from 1 vCPU / 1 GB to 64 vCPU / 128 GB, plus block-storage volumes at $0.11 per GB a month |
| Docker and nested virtualization | Docker, root, systemd and /dev/kvm on every sandbox, documented | Root and Docker; Civo does not document nested virtualization |
| Stopping | No compute charge while stopped; disk kept at least 14 days, longer with a saved snapshot; extra saved snapshots and the AI proxy still bill | A stopped instance is charged the same as a running one; to stop paying you delete it, and you can keep data on a separate block-storage volume that you attach to a new instance |
| Snapshots | Automatic disk snapshot every minute while running and at each stop; memory and running programs are not saved | Disk snapshots by API, CLI or schedule, documented 'where configured on a CivoStack Enterprise private region' and when enabled for your organization |
| Fork | Fork a running sandbox in one call, from the last 1-minute snapshot (disk, no memory) | Restore a disk snapshot into a new instance, where snapshots are enabled (disk, no memory) |
| Reaching the machine | HTTPS URLs for up to 50 ports, token-gated by default; public IPv6; the IP changes at each resume | Public IPv4 that stays until you delete the instance, on any port; load balancers for HTTP or TCP; you set up TLS certificates yourself |
| Desktop and computer use | 1920x1080, 60 fps desktop with Chrome, computer-use tools, embeddable stream | You set it up: install a desktop environment and a VNC or RDP server on the instance |
| Coding agents | Seven harnesses installed, including Claude Code, Codex and OpenCode, with a prompt, steer and events API | You set it up: install each agent on the instance, for example with an init script, and supervise it yourself |
| Keeping keys out of the machine | Optional paid AI credentials proxy ($1 per day on, plus $1 per 1,000 requests); with it on, real keys of supported providers stay out of the sandbox; other secrets still enter | You set it up: put secrets on the instance yourself, for example with an init script, or run your own proxy |
| Outbound rules and transfer | Open internet on every plan; no provider-side allowlist; egress not billed | Firewalls with rules for ingress and egress by port and CIDR; data transfer is free with no limits |
| GPUs | No GPU on any size; graphics run on the CPU | Nvidia L40S, A100, H100, H200, B200 and B300 machines |
| Regions | Germany, Finland and France; you cannot pick a region; no US or Asia region | London, Frankfurt, New York and Mumbai, chosen per instance |
| Compliance and transparency | SOC 2 is in progress. We're open about where we stand: live status and data retention policy. | Not published |
Every feature Battleships tracks (43)
| Feature | boat | Civo |
|---|---|---|
| Full VM (own kernel) | Yes | Yes |
| Docker inside | Yes | Yes |
| Nested virtualization | Yes | No documented way |
| Root | Yes | Yes |
| Systemd | Yes | Yes |
| Desktop GUI | Yes | No documented way |
| Browser | Yes | No documented way |
| 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 | Yes |
| Live fork (no pause) | Yes | Yes |
| 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 | No documented way |
| Wake on request | No documented way | No documented way |
| HTTPS preview URLs | Yes | No documented way |
| Raw TCP inbound | Yes | Yes |
| Public IPv4 | No documented way | Yes |
| 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 | No documented way |
| Arm64 | No documented way | No documented way |
| Self-hosting | No documented way | No documented way |
| 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 | No documented way |
| SOC 2 | No documented way | Not published |
| HIPAA | No documented way | Not published |
| EU data residency | No documented way | Yes |
| Zero data retention | Yes | Not published |
Performance
Civo Compute is not in the public benchmarks we use, so we cannot say which is faster. Civo does not publish which CPU its standard instances run on. In StarSling's run of 3 October 2026 (run 37073680030), boat did 28.06 runs/s on the V8 Web Tooling Benchmark at 4 vCPU / 8 GB, second of 15. Every boat sandbox in that run ran on an AMD Ryzen 9 9950X host. boat also places sandboxes on Ryzen 7 9700X hosts, which that run did not measure.
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. Civo 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 | Civo, 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 | $10 · Usage account |
| One agent that never stops 4 vCPU / 8 GB, 50 GB disk, running 24/7 all month | $26 · $20/mo | $43 · Usage account |
| 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 | $524 · Usage account |
| 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 | $893 · Usage account |
| 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 | $5,952 · Usage account |
boat: Plans cost $20, $100, $500 or $2,000 a month, and the whole plan price comes back as VM time for that month. Included time expires at the end of the period. A default sandbox (4 vCPU / 8 GB) costs $0.036 an hour, billed per second while it runs, busy or idle. A stopped sandbox has no compute charge, but extra saved snapshots and the AI proxy still bill. Above 200 starts a day on the $20 plan, each extra start costs $0.03 to $0.07. A card is required, also for the 7-day trial.
Civo: Each instance size has a fixed hourly price: Large (4 vCPU / 8 GB) is $0.059524 an hour, or $43.45 for a 730-hour month. Every started hour is billed in full, so a one-minute job costs an hour. A stopped instance is billed the same as a running one. To pay only for working hours, you delete the instance, keep data on a block-storage volume ($0.11 per GB a month) and attach it to a new instance. Data transfer is free, there is no plan fee, and new accounts get $250 of credit for the first month.
Limits in those scenarios
Civo limits each account with one quota for instances, CPUs, RAM and disk across all regions. New accounts start at a basic level, and Civo raises it on request after a period of use, so 50 agents, 300 user sandboxes or 1,000 jobs at once need a quota increase first. Hourly rounding makes the short-job scenarios expensive there. On boat the limit is a sandbox count at once (100 to 2,000 by plan) plus starts per minute, hour and day (12 / 60 / 200 on $20, 90 / 600 / 2,400 on $2,000). boat never queues a start: above 3 times the per-minute number, a start fails with 429 and you send it again. 1,000 short jobs at once need about 6,667 starts a day, more than the $2,000 plan allows. Auto-stop defaults to 1 hour; you can set up to 30 days or turn it off on a paid plan. A stopped sandbox's disk is kept for at least 14 days unless you save a snapshot. If a machine fails, you lose what was written after the last 1-minute snapshot.
| Scenario | boat | Civo |
|---|---|---|
| One coding agent, workdays | None for this scenario | None for this scenario |
| One agent that never stops | None for this scenario | None for this scenario |
| 50 agents in parallel | None for this scenario | None for this scenario |
| Sandboxes for your users | None for this scenario | None for this scenario |
| 1,000 short jobs at once |
| None for this scenario |
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 Civo when
you need GPUs, a region in the UK, US or India, a size boat does not sell, a fixed public IPv4, or a long-lived server next to managed Kubernetes, load balancers and firewall rules in one cloud.
- GPUs by the hour. Useful if your agents train or serve models: Civo rents Nvidia GPUs from L40S to B300, on demand or committed.
- Regions in the UK, US and India. Useful if your users or data must stay in the UK, the US or India: Civo runs in London, New York and Mumbai as well as Frankfurt.
- Free transfer and network rules. Useful if the agent must only reach chosen IP ranges or sit on a private network: Civo firewalls filter egress.
- More sizes, a fixed IP and no plan fee. Useful if you need other machine sizes, a stable IPv4, or very little use a month.
Use boat when
you want each agent on its own full VM that is ready to work: coding agents, a desktop, HTTPS ports and disk snapshots every minute built in, and no compute charge while a sandbox is stopped.
- A disk saved every minute, and fork while running. Agents sit idle for hours between tasks. On Civo you keep paying for an idle instance, or you script delete and rebuild yourself and keep the data on a block-storage volume.
- Coding agents and a desktop built in. On a Civo instance you set these up: you install, update and supervise each agent, desktop and API key yourself, and the keys sit on the machine where the agent's code can read them.
- HTTPS on up to 50 ports, no setup. An agent that starts a dev server wants to share a working link at once. On Civo that link is a bare IP with no TLS and no access token until you set them up for each machine.
Questions people ask
Is boat cheaper than Civo?
It depends on how the machine runs. One coding agent on workdays costs $10 a month on Civo against $20 on boat, if you delete the Civo instance every evening and rebuild it. One agent that never stops costs $26 on boat against $43 on Civo. 50 agents in parallel cost $317 against $524, and sandboxes for your users cost $200 against $893. For 1,000 short jobs at once Civo costs $5,952 a month. boat's estimate is $8,800, and the job still passes the $2,000 plan's start limits. Below about $20 of use a month, Civo costs less: it has no plan fee and gives $250 of credit for the first month.
Do I pay for a Civo instance that is stopped?
Yes. Civo's billing docs say a stopped instance is charged exactly like an active one until you delete it. To keep data without paying for compute, put it on a block-storage volume ($0.11 per GB a month), delete the instance and attach the volume to a new one. On boat, a stopped sandbox has no compute charge and boat keeps its disk for at least 14 days. Extra saved snapshots and the AI proxy still bill while stopped.
Can I run Docker and nested VMs on Civo?
Docker works, since a Civo instance is a VM with root. Civo does not document nested virtualization or /dev/kvm for its instances. On boat, Docker, systemd and /dev/kvm are documented on every sandbox.
Does Civo have snapshots and fork?
Civo's API can snapshot an instance's disk and restore it over the original or into a new instance. The docs describe this 'where configured on a CivoStack Enterprise private region', and the guide says it must be enabled for your organization. boat snapshots every sandbox's disk every minute while it runs and at each stop, and can fork a running sandbox in one call. Neither saves memory, and a boat fork can miss the last minute of writes.
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. Civo has regions in London, Frankfurt, New York and Mumbai, and you pick one per instance.
Is boat SOC 2 compliant?
No. SOC 2 is in progress, and boat has no SOC 2 report today. Civo lists SOC 2 and ISO 27001. Live status is at status.ascii.dev and our data retention policy is at docs.boat.dev/data-retention.
Start a sandbox
Install the CLI, then run boat new.
7-day free trial