Crusoe vs Jarvislabs

Both are GPU clouds that also rent plain CPU VMs. Crusoe is the bigger one, with the newest Nvidia and AMD GPUs, Kubernetes and Slurm in the US and EU. Jarvislabs rents Nvidia GPUs by the minute from a prepaid wallet in India, with ready GPU containers and model serving that scales 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.

Jarvislabs

Jarvislabs is an AI cloud from India that rents Nvidia GPUs by the minute for training and serving models.

You can rent a GPU VM with root and your own kernel, a Template (a GPU container with PyTorch, ComfyUI or similar ready, opened in JupyterLab, VS Code or SSH), a plain CPU VM, or a multi-node GPU cluster. Shared Filesystems attach to several instances and outlive any one of them. It also serves open models through Managed Endpoints, Serverless workers and a token-priced Model API. It is built for people who train, fine-tune and serve AI models. Its jl CLI and skill file let a coding agent on your own machine drive the GPUs.

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 workloadCrusoe: price rankJarvislabs: price rankboat: 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, the coding agents and copies of a machine yourself, so both are a compromise for a software factory. boat has a desktop, seven coding agents and fork of a running sandbox built in.
246th of 365, with limits
$2,996 a month
185th of 365, with limits
$1,406 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
234th of 361, with limits
$1,670 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
Both bill small CPU VMs with no plan fee, which suits short bursts. A Crusoe VM can spend up to a minute being created, and each Jarvislabs CPU VM bills at least 100 GB of disk. boat caps starts per plan.
131st of 336, with limits
$268 a month
107th of 336, with limits
$169 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 can run 300 user sandboxes once support raises your quota; you set up HTTPS URLs yourself. Jarvislabs does not publish how many instances can run at once. On boat the $100 plan runs 300 at once.
108th of 349, with limits
$951 a month
210th of 349, with limits
$539 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
47th of 349, with limits
$2,568 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
Crusoe fits agent evals fully at $811 a month. Jarvislabs is a compromise at $411, because it does not publish how many machines can run at once. boat fits at $200.
58th cheapest of 359
$811 a month
118th of 359, with limits
$411 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 make plain CI runners on CPU VMs: $395 a month on Crusoe and $253 on Jarvislabs. boat costs $86, billed per second, and the $20 plan includes 200 starts a day.
46th cheapest of 374
$395 a month
18th cheapest of 374
$253 a month
2nd cheapest of 374
$86 a month
24/7 dev boxes
1 machine 24/7 · 4 vCPU / 8 GB
A dev box that runs all month fits on all three: $121 a month on Crusoe, $68 on Jarvislabs and $26 on boat.
89th cheapest of 371
$121 a month
55th cheapest of 371
$68 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 Jarvislabs you install a VNC desktop on a root VM. boat ships a 60 fps desktop with Chrome.
253rd of 367, with limits
$811 a month
194th of 367, with limits
$377 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
261st of 356, with limits
$205 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
290th of 343, with limits
$247 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
156th of 327, with limits
$4,942 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
202nd of 351, with limits
$127 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
Jarvislabs fully fits GPU eval jobs at $876 a month, with Nvidia GPUs from L4 to H200 by the minute. Crusoe's H100 and H200 come only as 8-GPU machines, so small jobs are a compromise at $7,803. boat has no GPU.
89th of 102, with limits
$7,803 a month
10th cheapest of 102
$876 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 requirementNot ranked: misses a requirementNot ranked: misses a requirement

Key features

FeatureCrusoeJarvislabsboat
Kind of productGPU and CPU cloud with managed Kubernetes, Slurm and managed inferenceGPU cloud: GPU VMs, GPU containers (Templates), CPU VMs, clusters and model servingSandboxes for AI agents: full VMs with agents, desktop and hosting installed
GPUsNvidia GB200, B300, B200, H200, H100, A100, L40S and AMD MI355X, MI300X; H100 and H200 sold as 8-GPU VMsNvidia L4 up to H200, 1 to 8 per instance, on-demand, spot (Templates) or reserved, plus clustersNone on any size
IsolationEvery VM is a full VM on cloud-hypervisorGPU and CPU VMs are KVM virtual machines; Templates are containersFull VM with its own kernel, on AMD Ryzen 7 9700X and Ryzen 9 9950X hosts dedicated to boat; vCPUs are shared
Root, Docker and nested virtualizationsudo user (root login deprecated); you install Docker yourself (only legacy GPU images ship it); nested virtualization not documentedRoot on VMs, so you can run your own Docker daemon and kernel modules; nested virtualization not documentedRoot, systemd, Docker and /dev/kvm on every sandbox
CPU VM sizes2 to 176 vCPU with 4 GB of memory per vCPU2 vCPU / 8 GB up to 32 vCPU / 128 GB, with 4 GB of RAM per vCPU2 vCPU / 4 GB up to 16 vCPU / 32 GB; 4 vCPU / 8 GB by default
Saving and copying a machineCustom image of the boot disk while the VM is shut off; no snapshots of running VMs documentedNo snapshot, clone or fork command; pause keeps the disk; shared filesystems attach to new GPU instances, and startup scripts rebuild the softwareDisk saved every minute and at each stop; fork a running sandbox (writes from the last minute or so can be missing)
Stopped machinesNo compute charge; the 128 GiB OS disk bills $10.24 a month until the VM is deletedNo compute charge; the disk keeps billing at $0.10/GB-month, with at least 100 GB on a VMNo compute charge; disk kept at least 14 days; saved snapshots beyond the plan allowance cost $0.056 a day each
Desktop and computer useYou set it up: install a desktop environment and a VNC or RDP server on the VMJupyterLab, VS Code in the browser and SSH; you set up a VNC desktop on a root VM yourself1920x1080, 60 fps desktop with Chrome, computer-use tools and browser control
Coding agentsYou install each agent on the VM over SSH; Crusoe's MCP server lets an assistant inspect your Crusoe infrastructureYou install the agent on the VM; a CLI and skill file let an agent on your own machine create GPUs, run jobs and read logsSeven harnesses installed, including Claude Code, Codex and OpenCode, with a prompt, steer and events API
Reaching the machinePublic IPv4, static or dynamic; SSH; TCP and UDP load balancers; you set up HTTPS and TLS yourselfVMs get a public IP with every port open by default, and a reserved IP keeps it fixed; Templates expose HTTP ports through proxy URLsUp to 50 HTTPS URLs, token-gated by default; public IPv6 and outbound IPv4; no static IP, and the IP changes at each resume
Keeping keys out of the machineYou set it up: put secrets on the VM as files or variables, or run your own proxyKeys go in as environment variables or uploaded files, or you run your own proxyOptional 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
Network rulesVPC firewall with allow rules by IP, port and protocol, in and outSecurity groups with inbound and outbound rules, VPCs and reserved IPsOpen internet on every plan; no provider-side allowlist
Model servingManaged inferenceManaged Endpoints and Serverless workers that scale to zero when idleNone; a sandbox does not wake on a request
RegionsUS (Texas, Virginia, Ohio, Nevada) and EU (Iceland, Norway), chosen per VMIndia only for new instances (IN1, IN2)Germany, Finland and France; you cannot pick a region; no US or Asia region
Every feature Battleships tracks (43)
FeatureCrusoeJarvislabsboat
Full VM (own kernel)YesYesYes
Docker insideYesYesYes
Nested virtualizationNo documented wayNot publishedYes
RootYesYesYes
SystemdNot publishedNot publishedYes
Desktop GUINo documented wayNo documented wayYes
BrowserNo documented wayNo documented wayYes
Computer-use APINo documented wayNo documented wayYes
SSHYesYesYes
Persistent diskYesYesYes
Pause/resumeYesYesYes
Automatic snapshotsNo documented wayNo documented wayYes
Fork/cloneYesNo documented wayYes
Live fork (no pause)No documented wayNo documented wayYes
Memory forkNo documented wayNo documented wayNo documented way
Custom image (Docker or snapshot)YesYesYes
≥24 h sessionsYesYesYes
Idle auto-stopNo documented wayYesNo documented way
Wake on requestNo documented wayYesNo documented way
HTTPS preview URLsNo documented wayYesYes
Raw TCP inboundYesYesYes
Public IPv4YesYesNo documented way
Egress allowlistYesYesNo documented way
Secret proxyNo documented wayNo documented wayYes
Secret proxy for any APINo documented wayNo documented wayYes
Preinstalled agentsNo documented wayNo documented wayYes
Agent harness APINo documented wayNo documented wayYes
MCP serverYesNo documented wayNo documented way
GPUYesYesNo documented way
WindowsNo documented wayNo documented wayNo documented way
Arm64YesNo documented wayNo documented way
Self-hostingNo documented wayNo documented wayNo documented way
BYOCNo documented wayNo documented wayNo documented way
Open sourceNo documented wayNo documented wayNo documented way
Scoped API keysNot publishedNot publishedYes
Spend limitsNo documented wayYesYes
Usage per sandbox (API)YesYesYes
Audit logsYesNot publishedNo documented way
SSOYesNo documented wayNo documented way
SOC 2YesNo documented wayNo documented way
HIPAANot publishedNo documented wayNo documented way
EU data residencyYesNo documented wayNo documented way
Zero data retentionNot publishedNot publishedYes

Performance

CrusoeNot measured
JarvislabsNot measured
boat28.06 runs/s

Neither Crusoe nor Jarvislabs is in the CPU benchmark we use, so we cannot say which is faster. 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 Jarvislabs publishes GPU benchmarks but no CPU benchmark.

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 Jarvislabs 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.

ScenarioCrusoe, a monthJarvislabs, a monthboat, 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$21 · On-demand$20 · $20/mo
One agent that never stops
4 vCPU / 8 GB, 50 GB disk, running 24/7 all month
$121 · On-demand$71 · On-demand$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$892 · On-demand$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$231 · On-demand · with limits$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$514 · On-demand · with limits$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. Reservations bill for their whole term.

Jarvislabs: Jarvislabs bills per minute from a prepaid wallet with no plan fee. CPU VMs cost $0.012 per vCPU-hour plus $0.0032 per GB of RAM, so 4 vCPU / 16 GB costs $0.10 an hour. Disk is extra at $0.10 per GB-month, billed while running and while paused, with at least 100 GB on a VM. Data is deleted if the balance goes negative.

Jarvislabs: 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

Both sell CPU VMs with 4 GB of memory per vCPU, so the 4 vCPU rows use 16 GB machines on both, against boat's 8 GB. Crusoe sets CPU and GPU quotas per project that support can raise, so 300 user sandboxes or 1,000 jobs at once may need a ticket first. Jarvislabs publishes no limit on machines running at once, so those two scenarios are not confirmed until you ask. On boat the limits are a sandbox count by plan plus starts per minute, hour and day. boat never queues a start: the 1,000-job burst needs more starts than the $2,000 plan includes, and starts above 270 a minute fail with 429.

ScenarioCrusoeJarvislabsboat
One coding agent, workdaysNone for this scenarioNone for this scenarioNone for this scenario
One agent that never stopsNone for this scenarioNone for this scenarioNone for this scenario
50 agents in parallelNone for this scenario
  • how many machines can run at once: limit not published, probably fine at 50 (the typical published limit is 50)
None for this scenario
Sandboxes for your usersNone for this scenario
  • not confirmed: how many machines can run at once (you need 300; the typical published limit is 50)
None for this scenario
1,000 short jobs at onceNone for this scenario
  • not confirmed: how many machines can run at once (you need 1,000; the typical published limit is 50)
  • 2,400 starts/day included, paid above that (needs ~6,667)
  • 600 starts/hour included, paid above that (needs ~1,000)
  • starts above 90/min are paid, and starts above 270/min fail with 429

Which one should you use?

Use Crusoe when

you need the newest Nvidia or AMD GPUs, machines in the US or Europe, or cluster tools like Kubernetes and Slurm.

  • The newest and biggest GPUs. For large training or serving jobs, Crusoe rents Nvidia GB200, B300 and B200 and AMD MI355X and MI300X GPUs.
  • US and EU regions. For teams that need machines in the US or Europe, Crusoe runs in Texas, Virginia, Ohio, Nevada, Iceland and Norway.
  • Cluster tools built in. For cluster jobs, Crusoe offers managed Kubernetes, Slurm, shared disks and much larger CPU and storage VMs.

Use Jarvislabs when

you want one Nvidia GPU at a time by the minute, model serving that scales to zero, or machines in India.

  • Small GPUs by the minute. For short GPU jobs, Jarvislabs rents one Nvidia GPU at a time, from L4 to H200, billed per minute.
  • Model serving that scales to zero. For inference, Jarvislabs Serverless workers stop after an idle timeout and start again on the next request.
  • Ready GPU containers in India. For teams in India, Jarvislabs Templates open PyTorch or ComfyUI in JupyterLab or VS Code.

Where boat fits

Crusoe and Jarvislabs are GPU clouds, and boat has no GPU, so model training and serving belong on one of them. For agents on CPU machines, both give you a plain Linux VM to build on. boat gives each agent a full VM with coding agents and a desktop installed.

Work that saves itself and forks live

Neither documents a snapshot or fork of a running machine. On Crusoe you shut the VM off to image it. On Jarvislabs you rebuild with startup scripts. boat saves the disk every minute while the sandbox runs and forks it in one call.

Agents and a desktop inside

Both start as a plain Linux server, and their agent tools manage machines from your own computer. On both you install each agent, a browser and a desktop stream yourself. boat ships seven coding agents you drive from outside and a 60 fps desktop.

boat's own limits

boat has no GPU, no static IP, no firewall rules and no US or Asia region. Starts are capped per plan, so 1,000 short jobs at once do not fit even the $2,000 plan. If a machine fails, you lose what was written after the last good snapshot.

Use boat when you run agents: full VMs with coding agents, a desktop and up to 50 HTTPS URLs installed, a disk saved every minute, forks while running, and no compute charge while stopped. Compare it one to one: boat vs Crusoe and boat vs Jarvislabs.

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 Jarvislabs?

For CPU VMs in our scenarios, no. One agent running all month comes to $121 on Crusoe and $71 on Jarvislabs, and 50 agents in parallel to $1,488 against $892. boat comes to $26 and $317 for the same two jobs, on 8 GB sandboxes against 16 GB VMs.

Which is faster, Crusoe or Jarvislabs?

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.

Can Crusoe and Jarvislabs run Docker?

Yes. Both give you a full VM where you install Docker yourself; on Crusoe only legacy GPU images ship it. Neither documents nested virtualization. Every boat sandbox has Docker, systemd and /dev/kvm.

Can I snapshot or fork a machine on Crusoe or Jarvislabs?

On Crusoe you make a custom image of the boot disk while the VM is shut off. Jarvislabs has no snapshot, clone or fork command; shared filesystems and startup scripts rebuild a new machine. boat saves every sandbox's disk every minute and can fork one while it runs, from its last 1-minute snapshot.

Where do Crusoe and Jarvislabs run?

Crusoe runs in the US (Texas, Virginia, Ohio, Nevada) and in Iceland and Norway. Jarvislabs creates new instances only in India. boat runs only in Germany, Finland and France, and you cannot pick a region.

Which has more GPUs?

Crusoe has the wider range, up to Nvidia GB200 and AMD MI355X. Jarvislabs rents Nvidia L4 to H200, 1 to 8 per instance, plus clusters. boat has no GPU.

Try boat

Install the CLI, then run boat new.

7-day free trial

More comparisons