Crusoe vs Cerebrium
Crusoe rents you GPU and CPU virtual machines that run until you stop them, and you set up everything on them yourself. Cerebrium takes your code or Dockerfile and serves it as GPU containers that start on a request and scale back to zero.
The companies and products
Crusoe
Crusoe calls itself "the AI factory company": it builds energy-first data centers and rents GPU and CPU machines on Crusoe Cloud.
Crusoe Cloud is infrastructure for training and serving models: Nvidia and AMD GPU VMs, general-purpose and storage CPU VMs, disks, object storage, managed Kubernetes and Slurm, and managed inference. You create Ubuntu VMs through a console, CLI, Terraform or API, log in over SSH and install what you need. It is not a sandbox product, so this page compares the CPU VMs where they overlap with boat.
Cerebrium
Cerebrium is a serverless GPU cloud for real-time AI: voice agents, video models, LLMs and other ML apps.
You describe an app in a cerebrium.toml file, with your Python code or your own Dockerfile. Cerebrium builds it and serves it as HTTP or WebSocket endpoints. The Cerebrium Run API also runs an uploaded Python file or function without an endpoint. Cerebrium starts containers when requests arrive, scales them across GPUs and regions, and scales them to zero when traffic stops. It is built for teams that serve models in production, not for agents that need a machine of their own. This page compares the places where the two overlap.
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. “58th cheapest of 359” means 57 of the other 358 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 | Crusoe: price rank | Cerebrium: price rank | boat: price rank |
|---|---|---|---|
| Software factory 100 at once · 4 vCPU / 8 GB · 2,200 sessions of 8 h a month On both you set up the desktop and coding agents yourself. On Cerebrium you also bake packages into the image and keep files in /persistent-storage. boat has a desktop, Docker and seven coding agents installed. | 246th of 365, with limits $2,996 a month | 205th of 365, with limits $2,008 a month | 5th cheapest of 365 $634 a month |
| Always-on AI employees 50 machines 24/7 · 2 vCPU / 4 GB | 271st of 361, with limits $3,000 a month | 261st of 361, with limits $2,534 a month | 6th cheapest of 361 $657 a month |
| Code interpreter bursts 100 at once · 1 vCPU / 2 GB · 200,000 sessions of 1 min a month Short code runs suit Cerebrium's scale-to-zero containers and Cerebrium Run, at $131 a month here against $268 on Crusoe. boat's start limits make big bursts a compromise. | 131st of 336, with limits $268 a month | 222nd of 336, with limits $131 a month | 189th of 336, with limits $2,000 a month |
| Sandboxes for your users 300 at once · 2 vCPU / 4 GB · 30,000 sessions of 23 min a month Crusoe gives each VM a public IPv4; you set up HTTPS URLs and TLS yourself. Cerebrium gives each app one endpoint that scales with traffic. boat gives up to 50 token-gated HTTPS URLs per sandbox. | 108th of 349, with limits $951 a month | 226th of 349, with limits $821 a month | 3rd cheapest of 349 $209 a month |
| RL rollouts 1,000 at once · 2 vCPU / 4 GB · 1,000,000 sessions of 3 min a month | 77th of 349, with limits $4,055 a month | 78th of 349, with limits $4,068 a month | 39th of 349, with limits $2,000 a month |
| Agent evals 250 at once · 4 vCPU / 8 GB · 15,000 sessions of 20 min a month Both fit agent evals: Cerebrium at $639 a month and Crusoe at $811. boat fits at $200. | 58th cheapest of 359 $811 a month | 45th cheapest of 359 $639 a month | 10th cheapest of 359 $200 a month |
| CI runners 40 at once · 8 vCPU / 16 GB · 6,000 sessions of 12 min a month Both fit CI. Crusoe costs $395 a month and Cerebrium $766. On Crusoe you install Docker on the VM; Cerebrium does not document Docker inside an app. boat fits at $86, with Docker and /dev/kvm on every sandbox. | 46th cheapest of 374 $395 a month | 88th cheapest of 374 $766 a month | 2nd cheapest of 374 $86 a month |
| 24/7 dev boxes 1 machine 24/7 · 4 vCPU / 8 GB A dev box needs SSH and a disk that keeps your installs. A Crusoe VM has both. Cerebrium documents no SSH, and files outside /persistent-storage reset at a stop. boat fits at $26 a month for 730 hours. | 89th cheapest of 371 $121 a month | 272nd of 371, with limits $102 a month | 19th cheapest of 371 $26 a month |
| Computer-use agents 50 at once · 4 vCPU / 8 GB · 20,000 sessions of 15 min a month Neither ships a desktop. On Crusoe you install a desktop and a VNC or RDP server on the VM. On Cerebrium you can install a headless browser in your image, with no display stream. boat ships a 60 fps desktop with Chrome. | 253rd of 367, with limits $811 a month | 217th of 367, with limits $575 a month | 7th cheapest of 367 $200 a month |
| Browser-use agents 50 at once · 2 vCPU / 4 GB · 30,000 sessions of 10 min a month | 289th of 356, with limits $405 a month | 109th of 356, with limits $572 a month | 7th cheapest of 356 $200 a month |
| Scraping & bots (startup scale) 50 at once · 1 vCPU / 2 GB · 100,000 sessions of 3 min a month | 303rd of 343, with limits $403 a month | 105th cheapest of 343 $387 a month | 6th cheapest of 343 $90 a month |
| Mass scraping & bots (undetectable) 1,000 at once · 1 vCPU / 2 GB · 3,000,000 sessions of 2 min a month | 202nd of 327, with limits $8,055 a month | 134th of 327, with limits $3,991 a month | 73rd of 327, with limits $1,800 a month |
| Parallel red teaming 200 at once · 2 vCPU / 4 GB · 5,000 sessions of 30 min a month | 237th of 351, with limits $207 a month | 234th of 351, with limits $191 a month | 3rd cheapest of 351 $200 a month |
| GPU eval jobs 10 at once · 8 vCPU / 32 GB · 500 sessions of 30 min a month Cerebrium fits GPU eval jobs fully at $1,975 a month. Crusoe is a compromise at $7,803, because it sells H100s only as 8-GPU machines. boat has no GPU. | 89th of 102, with limits $7,803 a month | 28th cheapest of 102 $1,975 a month | 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 | Not ranked: misses a requirement |
Key features
| Feature | Crusoe | Cerebrium | boat |
|---|---|---|---|
| What you get | Plain Ubuntu VMs with GPUs or CPUs, plus managed Kubernetes and Slurm, that you set up yourself | Your app, built from code or a Dockerfile, served as autoscaling containers behind endpoints | A sandbox for agents: a full VM with tools, desktop and coding agents installed; you cannot boot your own Docker image |
| Isolation | Every VM is a full VM on cloud-hypervisor | Containers; the docs do not name the isolation layer | Full VM with its own kernel, on AMD Ryzen 7 9700X and Ryzen 9 9950X hosts dedicated to boat; vCPUs are shared |
| Shell, root and Docker | SSH with a sudo user; you install Docker yourself (only legacy GPU images ship it); nested virtualization not documented | No SSH documented; Docker inside and /dev/kvm are not documented | SSH, root, systemd, Docker and /dev/kvm on every sandbox |
| Files after a stop | OS disk and attached disks survive; local NVMe is erased; the 128 GiB OS disk bills $10.24 a month until the VM is deleted | Files in the shared /persistent-storage volume stay (100 GB free, then $0.05 per GB a month); you bake packages into the image; other changes reset | Disk saved every minute and at each stop, kept at least 14 days; memory and running programs are not saved |
| Fork and templates | Boot new VMs from a custom image of a stopped VM's boot disk | No fork; an early-beta memory checkpoint speeds up new containers of the same build | Fork a running sandbox from its last 1-minute snapshot; saved snapshots as templates |
| Scale to zero and wake | No; you start and stop VMs yourself | Yes; apps scale to zero and start again on the next request | No; a stopped sandbox is started by API, and auto-stop is a timer that does not watch for idle |
| Run time | No maximum; a VM runs until you stop or delete it | No container cap, but a request times out at response_grace_period (15 minutes by default, 12 hours at most for async runs) | Auto-stop defaults to 1 hour; set up to 30 days, or turn it off on a paid plan for no session cap |
| GPUs | Nvidia GB200, B300, B200, H200, H100, A100, L40S and AMD MI355X, MI300X; on-demand, spot or reserved | T4 to B200 and RTX PRO 6000, up to 8 per container, plus Inferentia2 and Trainium | None on any size; graphics run on the CPU |
| Inbound access | Public IPv4, static or dynamic; TCP and UDP load balancers; you set up HTTPS and TLS yourself | One endpoint per app on one port; custom domains on Standard | Up to 50 HTTPS URLs, token-gated by default; public IPv6 on every sandbox; raw ports over IPv6 on sandboxes with no IPv4 of their own; no static IP |
| Network rules | VPC firewall with allow rules by IP, port and protocol, in and out | No egress allowlist in the docs | Open internet on every plan; no provider-side allowlist |
| Desktop and computer use | You set it up: install a desktop environment and a VNC or RDP server on the VM | No desktop or computer-use product; you can install a headless browser in your own image | 1920x1080, 60 fps desktop with Chrome, computer-use tools and browser control |
| Coding agents | You install each agent on the VM over SSH; Crusoe's MCP server lets an assistant inspect your Crusoe infrastructure | You install one in your own image; an Agent Skill and a docs MCP server help your agent deploy to Cerebrium | Seven harnesses installed, including Claude Code, Codex and OpenCode, with a prompt, steer and events API |
| Keeping keys out of the machine | You set it up: put secrets on the VM as files or variables, or run your own proxy | Secrets reach the app as environment variables | Optional paid AI credentials proxy ($1 a day on, plus $1 per 1,000 requests); real keys of supported providers stay out; other secrets still enter |
| Compliance | SOC 2 Type II attestation; ISO 27001 and ISO 42001 | SOC 2, HIPAA, GDPR and ISO 27001 listed | SOC 2 in progress; no SOC 2 report today; no HIPAA BAA |
| Regions | US (Texas, Virginia, Ohio, Nevada) and EU (Iceland, Norway), chosen per VM | US and EU generally available; Asia, South America, Canada and the Middle East on request | Germany, Finland and France; no US or Asia region, and you cannot pick one |
Every feature Battleships tracks (43)
| Feature | Crusoe | Cerebrium | boat |
|---|---|---|---|
| Full VM (own kernel) | Yes | No documented way | Yes |
| Docker inside | Yes | Not published | Yes |
| Nested virtualization | No documented way | No documented way | Yes |
| Root | Yes | Not published | Yes |
| Systemd | Not published | Not published | Yes |
| Desktop GUI | No documented way | No documented way | Yes |
| Browser | No documented way | With your own setup | Yes |
| Computer-use API | No documented way | No documented way | Yes |
| SSH | Yes | No documented way | Yes |
| Persistent disk | Yes | Yes | Yes |
| Pause/resume | Yes | No documented way | Yes |
| Automatic snapshots | No documented way | No documented way | Yes |
| Fork/clone | Yes | No documented way | Yes |
| Live fork (no pause) | No documented way | No documented way | Yes |
| Memory fork | No documented way | No documented way | No documented way |
| Custom image (Docker or snapshot) | Yes | Yes | Yes |
| ≥24 h sessions | Yes | Yes | Yes |
| Idle auto-stop | No documented way | Yes | No documented way |
| Wake on request | No documented way | Yes | No documented way |
| HTTPS preview URLs | No documented way | Yes | Yes |
| Raw TCP inbound | Yes | Not published | Yes |
| Public IPv4 | Yes | No documented way | No documented way |
| Egress allowlist | Yes | No documented way | No documented way |
| Secret proxy | No documented way | No documented way | Yes |
| Secret proxy for any API | No documented way | No documented way | Yes |
| Preinstalled agents | No documented way | No documented way | Yes |
| Agent harness API | No documented way | No documented way | Yes |
| MCP server | Yes | No documented way | No documented way |
| GPU | Yes | Yes | No documented way |
| Windows | No documented way | No documented way | No documented way |
| Arm64 | Yes | No documented way | No documented way |
| Self-hosting | No documented way | No documented way | No documented way |
| BYOC | No documented way | No documented way | No documented way |
| Open source | No documented way | No documented way | No documented way |
| Scoped API keys | Not published | Not published | Yes |
| Spend limits | No documented way | Not published | Yes |
| Usage per sandbox (API) | Yes | Yes | Yes |
| Audit logs | Yes | Yes | No documented way |
| SSO | Yes | No documented way | No documented way |
| SOC 2 | Yes | Yes | No documented way |
| HIPAA | Not published | Yes | No documented way |
| EU data residency | Yes | Yes | No documented way |
| Zero data retention | Not published | Not published | Yes |
Performance
Neither Crusoe nor Cerebrium is in the CPU benchmark we use, so we cannot say which is faster at CPU work. 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 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. Crusoe's CPU VMs run on AMD Genoa or Turin processors, and Cerebrium's speed claims are about GPU inference and cold starts, which this test does not cover.
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. Crusoe and Cerebrium are 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 | Crusoe, a month | Cerebrium, a month | boat, 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 | $32 · On-demand | $53 · Hobby · with limits | $20 · $20/mo |
| One agent that never stops 4 vCPU / 8 GB, 50 GB disk, running 24/7 all month | $121 · On-demand | $210 · Hobby · with limits | $26 · $20/mo |
| 50 agents in parallel 50 machines of 4 vCPU / 8 GB at once, 8-hour sessions, 1,100 sessions a month, Docker inside | $1,488 · On-demand | $2,557 · Hobby · with limits | $317 · $20/mo × 3 seats |
| Sandboxes for your users 2 vCPU / 4 GB, 30,000 sessions of 10 minutes a month, up to 300 at once | $405 · On-demand | $715 · Hobby | $200 · $100/mo × 2 seats |
| 1,000 short jobs at once 2 vCPU / 4 GB, 1,000 at once, 3 minutes each, 200,000 jobs a month | $811 · On-demand | $1,681 · Standard | $8,800 · $2000/mo · with limits |
Crusoe: Crusoe bills each VM per second while it runs, at $0.04 per vCPU-hour with 4 GB of memory per vCPU, so a 4 vCPU / 16 GB VM costs $0.16 an hour. Every VM also has a fixed 128 GiB OS disk at $10.24 a month, billed running or stopped. There is no plan fee and no data transfer charge today.
Cerebrium: Cerebrium bills per second for each vCPU, GB of memory and GPU while a container runs: $0.00000655 per vCPU-second and $0.00000222 per GB-second on the default tier, which can be interrupted. The protected tier costs 2x on all compute. Hobby is free plus compute. Standard is $100 a month on top of compute, with no usage credit.
Cerebrium: Plans cost $20, $100, $500 or $2,000 a month, and the whole plan price comes back as VM time for that month. Unused VM time expires at the end of the period. A 4 vCPU / 8 GB sandbox costs $0.036 an hour, billed per second while it runs, busy or idle. The $20 plan includes 12 starts a minute and 200 a day; extra starts cost $0.03 to $0.07. A stopped sandbox has no compute charge and keeps its disk for at least 14 days. Saved snapshots above the included count and the optional credentials proxy still charge while it is stopped.
Limits in those scenarios
Crusoe fits every scenario, but it sells 4 GB of memory per vCPU, so the 4 vCPU rows use a 16 GB machine, and 50 agents or 300 user sandboxes may need a support ticket to raise project quotas. In the coding agent, always-on and 50-agent rows, Cerebrium needs your own setup: packages go into the image and files into /persistent-storage. The fleet also needs Docker inside, which Cerebrium does not document. Cerebrium publishes no egress price, so its scenarios count none. boat never queues a start: at 1,000 short jobs at once, the $2,000 plan charges for starts above 90 a minute and refuses starts above 270 a minute with 429. Crusoe and Cerebrium's Standard plan both fit that burst.
| Scenario | Crusoe | Cerebrium | boat |
|---|---|---|---|
| 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 |
|
|
Which one should you use?
Use Crusoe when
you want full GPU or CPU VMs you run yourself, the newest Nvidia or AMD chips for training, clusters with Kubernetes and Slurm, or firewall control in and out.
- Full machines you control. Crusoe gives you a full VM with SSH and sudo that runs until you stop it, so long jobs need no endpoint wrapper.
- The newest training chips. For training, Crusoe rents Nvidia GB200 and B300 and AMD MI300X and MI355X, which Cerebrium does not list.
- Cluster tools and network control. Teams running clusters get managed Kubernetes, Slurm, shared disks and VPC firewall rules for traffic in and out.
Use Cerebrium when
you want to serve a model or app as an endpoint that scales with traffic and down to zero, without managing machines, or need regions outside the US and EU.
- Endpoints that scale to zero. Apps that wait for traffic scale to zero, start on the next request and grow to many replicas, billed per second.
- No machines to manage. You hand over code or a Dockerfile and a cerebrium.toml, and Cerebrium builds it and serves it as HTTP or WebSocket endpoints.
- More regions. It runs in the US and the EU by default, with Asia, South America, Canada and the Middle East on request.
Where boat fits
Crusoe and Cerebrium are both GPU clouds, and neither is built as a machine for an agent to work inside. boat fits agents that write code, use a browser or host previews, on a full VM with a desktop and coding agents installed. Keep model training or serving on Crusoe or Cerebrium, since boat has no GPU.
A disk that saves itself and forks
On Cerebrium, installs outside /persistent-storage reset after a stop. On Crusoe, a copy means shutting the VM off to image its boot disk. boat saves the disk every minute and forks a running sandbox. A fork can miss the last minute of writes.
Docker, /dev/kvm and a shell
Cerebrium documents no SSH and no Docker inside an app. Crusoe does not document nested virtualization. Every boat sandbox has root, systemd, Docker and /dev/kvm, so builds, emulators and VMs run inside it.
boat's own limits
boat has no GPU, no wake on request, no outbound allowlist and no US or Asia region. It has no SOC 2 report today. Starts are capped per plan, so 1,000 short jobs at once do not fit even the $2,000 plan.
Use boat when you run agents that need a machine of their own: a full VM with Docker and /dev/kvm, a disk saved every minute, forks of a running sandbox, and a desktop and coding agents installed. Compare it one to one: boat vs Crusoe and boat vs Cerebrium.
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
Questions people ask
Is Crusoe cheaper than Cerebrium?
In every scenario we priced, Crusoe comes out lower: $121 against $210 a month for one agent that never stops, and $811 against $1,681 for 1,000 short jobs at once. Cerebrium bills nothing while an app is scaled to zero, which can matter for spiky traffic. boat comes to $26 a month for the always-on agent, and does not fit the 1,000-job burst because of its start limits.
Which is faster, Crusoe or Cerebrium?
Neither is in the CPU benchmark we use, so we cannot say. In StarSling's run of 3 October 2026, boat did 28.06 runs/s on the V8 Web Tooling Benchmark at 4 vCPU / 8 GB, on an AMD Ryzen 9 9950X host. For GPU work, speed depends on the chip you pick on either one.
Can Crusoe run Docker? Can Cerebrium?
A Crusoe VM is a full Ubuntu machine with a sudo user, so you can install Docker yourself; only legacy GPU images ship it. Cerebrium builds your app from a Dockerfile, but running Docker inside the app is not documented. boat runs Docker, systemd and /dev/kvm in every sandbox.
What happens to files when they stop?
On Crusoe the OS disk and attached disks survive a stop, but local NVMe is erased and the OS disk keeps billing. On Cerebrium the /persistent-storage volume is kept and the rest resets. boat saves the disk every minute and at each stop, and keeps it for at least 14 days with no compute charge. Saved snapshots above the included count and the optional AI proxy still charge.
Which runs in more regions?
Cerebrium runs in the US and the EU, with Asia, South America, Canada and the Middle East on request. Crusoe runs in Texas, Virginia, Ohio and Nevada, plus Iceland and Norway. boat runs only in Germany, Finland and France, and you cannot pick a region.
Is Crusoe or Cerebrium a sandbox for AI agents?
Neither is built as one. Crusoe gives you a plain VM to set up, and Cerebrium serves your app as endpoints, with no documented SSH. A boat sandbox is a full VM with a desktop and coding agents installed.
Try boat
Install the CLI, then run boat new.
7-day free trial