boat vs Bitrise
Bitrise is a mobile CI/CD service. It runs iOS and Android builds on Apple silicon Macs and Linux VMs, and it also rents remote dev environments for developers and coding agents. boat is a sandbox for agents: a full Linux VM that saves its disk every minute, can run with no session cap once auto-stop is off, and lets you drive the agents inside by API.
Where boat stands out
A disk saved every minute
boat saves the disk every minute while the sandbox runs, and once more at each stop. A stopped sandbox has no compute charge, and boat keeps its disk for at least 14 days; a saved snapshot keeps it longer. Bitrise dev sessions keep one disk until you delete it, but Bitrise does not back it up.
Agents you drive by API
boat installs seven coding-agent harnesses in each sandbox, including Claude Code, Codex and OpenCode. You send prompts, steer the agents and read their events through an API. Bitrise starts Claude Code from its CLI and creates sessions and runs commands by API, CLI or MCP server. boat's optional, paid credentials proxy keeps the real AI keys of supported providers out of the VM.
Fork and public URLs
Every boat sandbox has root, systemd, Docker and /dev/kvm, and you can fork a running one into a copy from its last 1-minute snapshot. Each sandbox serves up to 50 token-gated HTTPS URLs. Bitrise Linux sessions also run Docker and Android emulators, and you reach sessions by SSH or VNC.
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
Bitrise
Bitrise is a mobile CI/CD platform that builds, tests and ships iOS and Android apps on its own Mac and Linux machines.
Bitrise is a different kind of product: a CI service. Each build runs in its own virtual machine from a Bitrise stack, and the machine is rolled back after the build. Since 2026 it also sells Remote Dev Environments: macOS and Linux sessions with a persistent disk. You create sessions by REST API, CLI or an open-source MCP server, start Claude Code from the CLI, and run commands in a session without a terminal. It is built for mobile teams.
- Funding
- $95M+ in total
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 | Bitrise: price rank |
|---|---|---|
| Software factory 100 at once · 4 vCPU / 8 GB · 2,200 sessions of 8 h a month Bitrise CI builds stop at a timeout and roll back, so a software factory there uses its remote dev environments. Each self-serve tier runs 1 to 5 VMs at once; more needs an Enterprise quote. | 5th cheapest of 365 $634 a month | 73rd of 365, with limits $3,403 a month |
| Always-on AI employees 50 machines 24/7 · 2 vCPU / 4 GB Bitrise dev sessions have no time cap; they stop after 5 days idle by default (up to 30 days or off) and now and then for maintenance. boat has no session cap once auto-stop is off (default 1 h). | 6th cheapest of 361 $657 a month | 122nd of 361, with limits $1,970 a month |
| Code interpreter bursts 100 at once · 1 vCPU / 2 GB · 200,000 sessions of 1 min a month | 189th of 336, with limits $2,000 a month | 284th of 336, with limits $658 a month |
| Sandboxes for your users 300 at once · 2 vCPU / 4 GB · 30,000 sessions of 23 min a month Self-serve Bitrise dev environment tiers run at most 5 VMs at once, so hundreds of user sandboxes need an Enterprise quote. boat runs 100 to 2,000 sandboxes at once by plan, within per-plan start limits. | 3rd cheapest of 349 $209 a month | 264th of 349, with limits $1,604 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 | 266th of 349, with limits $6,818 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 | 288th of 359, with limits $1,274 a month |
| CI runners 40 at once · 8 vCPU / 16 GB · 6,000 sessions of 12 min a month Bitrise is a real CI service, made for iOS and Android pipelines. boat fits generic Linux jobs an agent starts, with Docker; it has no build quota but limits starts per minute, hour and day by plan. | 2nd cheapest of 374 $86 a month | 182nd of 374, with limits $859 a month |
| 24/7 dev boxes 1 machine 24/7 · 4 vCPU / 8 GB Both keep a persistent disk. Bitrise keeps a session disk until you delete it, without backups, and its monthly cap makes cost predictable. boat saves the disk every minute and keeps it at least 14 days after a stop. | 19th cheapest of 371 $26 a month | 183rd of 371, with limits $119 a month |
| Computer-use agents 50 at once · 4 vCPU / 8 GB · 20,000 sessions of 15 min a month Bitrise lets an agent take screenshots of and control a macOS desktop through its MCP server. boat streams a Linux desktop and Chrome at 1920x1080, 60 fps, with computer-use tools. | 7th cheapest of 367 $200 a month | 109th of 367, with limits $1,186 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 | 190th of 356, with limits $746 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 | 199th of 343, with limits $862 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 | 256th of 327, with limits $13,088 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 | 124th of 351, with limits $537 a month |
| GPU eval jobs 10 at once · 8 vCPU / 32 GB · 500 sessions of 30 min a month Neither offers GPUs. | 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 Bitrise fits: it rents Apple silicon Macs with iOS simulators. boat has no macOS. | Not ranked: misses a requirement | 19th of 35, with limits $400 a month |
Key features
| Feature | boat | Bitrise |
|---|---|---|
| Kind of product | Sandbox for AI agents: a Linux VM you create, run, stop and fork by API | Mobile CI/CD service, plus Remote Dev Environments for developers and agents |
| Isolation | Every sandbox is a full VM with its own kernel, on a physical host dedicated to boat (AMD Ryzen 7 9700X and Ryzen 9 9950X hosts); vCPUs are shared | Every build or session is its own VM; CI VMs are rolled back after each build |
| Operating systems | Linux only (Ubuntu 24.04); Windows programs run through Wine | macOS on Apple silicon with iOS simulators, and Linux with Android emulators |
| Docker and nested virtualization | Docker, root, systemd and /dev/kvm on every sandbox | Docker and nested virtualization on Linux machines, so Android emulators run there; Bitrise says Docker and emulators do not run in macOS sessions, because Apple's virtualization has no nested virtualization |
| How long a machine runs | Auto-stop defaults to 1 hour; set up to 30 days, or turn it off on a paid plan for no session cap | CI builds time out at 210 minutes (up to 4 hours on Enterprise); dev sessions have no time cap but stop after 5 days idle by default (up to 30 days or off), and maintenance can stop them now and then |
| Sandboxes at once | 100 to 2,000 by plan, with included starts per minute, hour and day; extra starts cost $0.03 to $0.07 | Self-serve dev environment tiers run 1, 3 or 5 VMs at once; CI Pro runs at most 10 macOS or 30 Linux builds at once; more needs Enterprise |
| Files after a stop | Snapshots every minute and on stop, kept at least 14 days after a stop (saved snapshots have no expiry); a stopped sandbox has no compute charge | A terminated dev session keeps its disk until you delete it, but the disk is not backed up; CI machines keep nothing |
| Fork | Fork a running sandbox into an independent copy, from its last 1-minute snapshot | No fork action documented; warm pools hand out new sessions booted from a template |
| Coding agents | Seven harnesses installed, including Claude Code, Codex and OpenCode, driven by a prompt, steer and events API | Claude Code started from the CLI; sessions created by API, CLI or MCP server, commands run headless with session exec, and an event list for agent stops and permission prompts; no prompt or steer API for the agent |
| Desktop and computer use | Linux desktop and Chrome streamed at 1920x1080, 60 fps, with computer-use tools and an embeddable stream | VNC desktop on macOS sessions; an open-source MCP server takes screenshots and controls it |
| Keeping keys out of the sandbox | Optional AI credentials proxy ($1 per day on plus $1 per 1,000 requests): the real keys of supported model providers never enter the VM; other secrets and environment variables still do | Secrets are environment variables, so the value enters the machine |
| Reaching the machine | SSH and up to 50 token-gated HTTPS URLs per sandbox; public IPv6 and outbound IPv4; no static IP | SSH, VNC and a web terminal; device preview links stream a simulator; for a public URL to a port, you set it up: SSH port forwarding or your own tunnel |
| Mobile build pipeline | None built in; you install the tools you need | Workflows, code signing, build cache, release management and over-the-air updates |
| Regions | Germany, Finland and France; you cannot pick a region, and there is no US or Asia region | US, Ireland, Frankfurt, Singapore and Sydney |
| Self-hosting | Managed only | Bitrise on AWS in your own account, or fully self-hosted Bitrise Runners |
| 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 | Bitrise |
|---|---|---|
| Full VM (own kernel) | Yes | Yes |
| Docker inside | Yes | Yes |
| Nested virtualization | Yes | Yes |
| Root | Yes | Yes |
| Systemd | Yes | No documented way |
| Desktop GUI | Yes | Yes |
| Browser | Yes | Yes |
| Computer-use API | Yes | Yes |
| SSH | Yes | Yes |
| Persistent disk | Yes | Yes |
| Pause/resume | Yes | Yes |
| 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 | No documented way |
| 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 | No documented way |
| Secret proxy | Yes | No documented way |
| Secret proxy for any API | Yes | No documented way |
| Preinstalled agents | Yes | Yes |
| Agent harness API | Yes | Yes |
| MCP server | No documented way | Yes |
| GPU | No documented way | No documented way |
| Windows | No documented way | No documented way |
| Arm64 | No documented way | Yes |
| Self-hosting | No documented way | Yes |
| BYOC | No documented way | Yes |
| Open source | No documented way | No documented way |
| Scoped API keys | Yes | Not published |
| Spend limits | Yes | Not published |
| Usage per sandbox (API) | Yes | No documented way |
| Audit logs | No documented way | Not published |
| SSO | No documented way | Yes |
| SOC 2 | No documented way | Yes |
| HIPAA | No documented way | No documented way |
| EU data residency | No documented way | Yes |
| Zero data retention | Yes | Not published |
Performance
Bitrise is not in the public benchmarks we use, so we cannot say which is faster. For reference, boat did 28.06 runs/s on the V8 Web Tooling Benchmark at 4 vCPU / 8 GB, second of 15 in StarSling's run of 3 October 2026 (run 37073680030). 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.
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. Bitrise 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 | Bitrise, 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 | $260 · Pro · with limits |
| One agent that never stops 4 vCPU / 8 GB, 50 GB disk, running 24/7 all month | $26 · $20/mo | $119 · RDE Pro · 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 | $2,309 · Pro · 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 | $812 · Pro · 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 | $1,538 · Pro · 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, and unused time expires at the end of the period. A default sandbox (4 vCPU / 8 GB) costs $0.036 an hour, billed per second, so 730 hours cost $26. Above the included starts, an extra start costs $0.03 to $0.07. A stopped sandbox has no compute charge, but saved snapshots above the included count and the AI credentials proxy still charge.
Bitrise: Bitrise CI is sold by plan: Starter is a flat fee with unlimited minutes on Medium machines, and Pro adds per-minute machine time and a monthly build allowance on top of its fee. Remote Dev Environments Basic costs $20, $40 or $60 a month for 1, 3 or 5 VMs, with included minutes. Linux then costs $0.0044 a minute up to a monthly cap of $39, $117 or $195, after which Linux is free for the rest of the month. Pro tiers cost twice as much.
Limits in those scenarios
Bitrise limits machines by plan. Self-serve dev environment tiers run 1 to 5 VMs at once, and CI Pro runs at most 10 macOS or 30 Linux builds at once, so 50 agents in parallel and 300 user sandboxes need an Enterprise quote. CI builds stop at the build timeout. Dev sessions have no such timeout; they stop after a stretch of inactivity you can set, and now and then for maintenance. On boat the limit is 100 to 2,000 sandboxes at once by plan, plus included starts per minute, hour and day. Extra starts cost $0.03 to $0.07, and starts above 3 times the per-minute number fail with 429; boat never queues a start. The 1,000-job burst needs about 6,667 starts a day, and the $2,000 plan includes 2,400, so it does not fit without a custom plan. Auto-stop defaults to 1 hour, and boat keeps a stopped sandbox's disk for at least 14 days unless you save a snapshot.
| Scenario | boat | Bitrise |
|---|---|---|
| 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 Bitrise when
you build and ship iOS or Android apps, need macOS on Apple silicon, or must run in the US, Asia Pacific or your own AWS account.
- Macs and iOS simulators. Useful if your agents build or test iOS apps: Bitrise rents Apple silicon Macs with iOS simulators and a desktop.
- A full mobile CI/CD pipeline. Useful if you ship mobile apps: Bitrise handles builds, code signing, caching, store releases and over-the-air updates.
- More regions, self-hosting and SOC 2. Useful if you need machines in the US or Asia Pacific, inside your own AWS account, or a compliance report today.
Use boat when
your agents need a full Linux VM with Docker that can run for days, saves its disk every minute, forks, serves public HTTPS URLs and runs coding agents you drive by API.
- A disk saved every minute. If a Bitrise session disk is lost, there is no restore point. On boat you lose only what was written after the last good snapshot.
- Agents you drive by API. Bitrise can create sessions and run commands by API, but it has no API to prompt or steer the agent inside. On Bitrise, secrets are environment variables, so a key sits inside a machine the agent controls.
- Fork and public URLs. An agent that builds a web app must show it at a URL. On Bitrise you set it up yourself with SSH port forwarding or your own tunnel. Bitrise documents no way to copy a session, so two ideas side by side need two new sessions.
Questions people ask
Is boat cheaper than Bitrise?
In the scenarios we priced, boat costs less. One coding agent on workdays or all month comes to $20 to $26 a month on boat and about $59 on a Bitrise Basic dev environment (Linux, $20 base plus a $39 monthly cap, 4 vCPU / 16 GB). 50 agents in parallel come to $317 on boat; Bitrise dev environment tiers run at most 5 VMs, so 50 needs an Enterprise quote. For 1,000 short jobs at once, neither fits without higher limits.
Can I run AI coding agents on Bitrise?
Yes, in Remote Dev Environments. bitrise-cli rde claude creates a session, clones your branch and starts Claude Code. You can install other agents with a warmup script, create sessions by REST API or MCP server, and run commands headless with session exec. On boat seven agent harnesses come installed, and an API lets you prompt and steer the agent itself.
Does boat run macOS or iOS simulators?
No. boat runs Linux VMs only, so iOS builds and simulators need a Mac service like Bitrise. boat does run Docker and /dev/kvm, so Linux tools and Android emulators work inside a sandbox.
Is Bitrise a sandbox for agents?
Not at its core. Bitrise is a mobile CI/CD service whose build machines are reset after each build. Its Remote Dev Environments are cloud machines for developers and agents, created by API, CLI or MCP server, with 1 to 5 VMs per self-serve tier. boat is built to create, stop and fork many agent sandboxes by API, within per-plan start limits.
Where does my data run?
boat sandboxes run on machines in Germany, Finland and France. You cannot pick a region, and snapshot copies can be stored outside the EU. Bitrise runs in the US, Ireland, Frankfurt, Singapore and Sydney, and can also run in your own AWS account.
Is boat SOC 2 compliant?
SOC 2 is in progress, so boat has no SOC 2 report today. boat measures 99.95% sandbox uptime and publishes no SLA; live status is at status.ascii.dev. Bitrise lists SOC 2 Type II and PCI DSS on its security page.
Start a sandbox
Install the CLI, then run boat new.
7-day free trial
More comparisons
- boat vs Buildkite
- boat vs Blacksmith
- boat vs CircleCI
- boat vs GitHub Actions
- boat vs Codemagic
- boat vs Depot
- boat vs GitLab.com hosted runners
- boat vs WarpBuild
- boat vs E2B
- boat vs Daytona
- boat vs Modal
- boat vs Vercel Sandbox
- GitHub Actions vs Bitrise
- CircleCI vs Bitrise
- Blacksmith vs Bitrise
- Depot vs Bitrise
- WarpBuild vs Bitrise
- Buildkite vs Bitrise
- GitLab.com hosted runners vs Bitrise
- Bitrise vs Codemagic