Cube vs boat.dev
boat.dev is built for agent factories: many persistent VMs you fork and stop. Cube is built for a developer and their agents, on one computer.
Published
The short version
boat.dev (formerly ascii box) sells persistent Ubuntu VMs you drive from a CLI. boat fork clones a VM’s disk, boat stop snapshots and pauses it, and you pay per second while it runs. It’s aimed at running many agents as a fleet.
Cube is an always-on Linux computer in the cloud for your coding agents, with a Mac app, GitHub sign-in, a worktree per task and phone check-ins.
Side by side
| boat.dev | Cube | |
|---|---|---|
| Shape | Many VMs; fork and stop | One computer for your agents |
| Default size | 4 vCPU, 8 GB RAM, 50 GB disk | Pick the machine that suits you |
| Billing | Per second while running, $20/month minimum | Cube plan |
| Parallel attempts | Fork the VM | A worktree per task |
| Interface | CLI and SSH | Mac app, phone, and SSH |
| After a stop | Files persist; hand-started processes don’t resume | Always on |
When to choose boat.dev
- You run agents as a fleet and want a VM per attempt.
- Per-second billing and stopping machines between runs fits your usage.
When to choose Cube
- You want your agents to keep running without starting and stopping machines.
- You want a desktop app with every repo and session in one place.
- You want to check in from your phone.
Questions
How is boat.dev billed?
As of September 2026, per second while a VM runs, with a $20 monthly minimum. The default 4 vCPU, 8 GB sandbox is listed at $0.036 an hour.
What happens when I stop a boat.dev VM?
boat stop snapshots the VM and pauses billing. Files, installed packages and enabled services persist; processes you started by hand don’t resume on their own.
When should I choose boat.dev?
When you need many VMs, want to fork a machine’s disk for parallel attempts, and prefer a CLI with per-second billing.