boat vs Jarvislabs

Jarvislabs is a GPU cloud: you rent Nvidia GPUs, GPU containers and plain CPU virtual machines by the minute, in India. boat is built for agents: every VM comes with coding agents, a 60fps desktop and snapshots every minute, and a stopped VM has no compute charge. boat runs in Germany, Finland and France and has no GPUs.

Where boat stands out

Snapshots every minute, live fork, no compute charge when stopped

A stopped boat sandbox has no compute charge and keeps its disk for at least 14 days. Saved snapshots keep it longer; those beyond the plan allowance cost $0.056 a day each. boat saves the disk every minute while the sandbox runs and once more at each stop. You can fork a sandbox while it runs, so one set-up machine becomes many. Jarvislabs has no snapshot, clone or fork command. A paused instance keeps its disk and keeps paying for it.

Coding agents and a desktop built in

boat installs seven coding-agent harnesses, including Claude Code, Codex and OpenCode, in each sandbox. You drive them from outside with a prompt, steer and events API. Every sandbox also has a 60fps desktop with Chrome and computer use. A Jarvislabs CPU VM is a clean Linux machine with root. You set up the agent, a browser and any desktop yourself.

HTTPS ports and an optional credentials proxy

Each boat sandbox can serve HTTPS on up to 50 ports behind a token, with no certificates to set up. boat's optional credentials proxy ($1 a day it is on plus $1 per 1,000 requests) keeps the real keys of supported AI providers out of the sandbox. It also works with any HTTPS API you register. Other environment variables and secrets still enter the sandbox. A Jarvislabs VM gets a public IP with every port open until you add a security group. Your keys sit on the machine as environment variables, unless you run your own proxy.

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.

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. “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 workloadboat: price rankJarvislabs: price rank
Software factory
100 at once · 4 vCPU / 8 GB · 2,200 sessions of 8 h a month
A Jarvislabs CPU VM gives a coding agent root and Docker. You set up the agent and tooling yourself. Jarvislabs has no snapshot or fork command, so a second machine is a new VM plus your own setup steps.
5th cheapest of 365
$634 a month
185th of 365, with limits
$1,406 a month
Always-on AI employees
50 machines 24/7 · 2 vCPU / 4 GB
An always-on assistant fits on a Jarvislabs CPU VM. You set up the browser, a desktop and the agent yourself; boat ships them installed.
6th cheapest of 361
$657 a month
234th of 361, with limits
$1,670 a month
Code interpreter bursts
100 at once · 1 vCPU / 2 GB · 200,000 sessions of 1 min a month
Jarvislabs bills small CPU VMs by the minute with no plan fee, which suits short bursts. Each CPU VM bills at least 100 GB of disk. boat caps starts per plan (the $20 plan: 12 a minute, 60 an hour, 200 a day).
189th of 336, with limits
$2,000 a month
107th of 336, with limits
$169 a month
Sandboxes for your users
300 at once · 2 vCPU / 4 GB · 30,000 sessions of 23 min a month
Jarvislabs does not publish how many instances an account can run at once, so ask it before you plan 300 sandboxes for your users. On boat the $100 plan runs 300 at once with 30 included starts a minute.
3rd cheapest of 349
$209 a month
210th of 349, with limits
$539 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
47th of 349, with limits
$2,568 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
118th of 359, with limits
$411 a month
CI runners
40 at once · 8 vCPU / 16 GB · 6,000 sessions of 12 min a month
Both fit. A Jarvislabs CPU VM makes a plain CI runner billed per minute. boat bills per second, and a stopped sandbox has no compute charge; the $20 plan includes 200 starts a day.
2nd cheapest of 374
$86 a month
18th cheapest of 374
$253 a month
24/7 dev boxes
1 machine 24/7 · 4 vCPU / 8 GB
19th cheapest of 371
$26 a month
55th cheapest of 371
$68 a month
Computer-use agents
50 at once · 4 vCPU / 8 GB · 20,000 sessions of 15 min a month
Jarvislabs offers no desktop or computer-use API; access is JupyterLab, VS Code in the browser and SSH. You set it up: install a VNC desktop and a browser on a root VM and run your own computer-use loop. boat streams a 60fps desktop with computer use on every sandbox.
7th cheapest of 367
$200 a month
194th of 367, with limits
$377 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
261st of 356, with limits
$205 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
290th of 343, with limits
$247 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
156th of 327, with limits
$4,942 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
202nd of 351, with limits
$127 a month
GPU eval jobs
10 at once · 8 vCPU / 32 GB · 500 sessions of 30 min a month
Jarvislabs fits: it rents Nvidia GPUs from L4 to H200 by the minute. boat has no GPU on any size.
Not ranked: misses a requirement10th cheapest of 102
$876 a month
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 requirement

Key features

FeatureboatJarvislabs
Kind of productSandboxes for AI agents: VMs with agents, desktop and hosting readyGPU cloud: GPU VMs, GPU containers, CPU VMs, clusters and model serving
IsolationEvery sandbox is a full VM with its own kernelGPU VMs and CPU VMs are KVM virtual machines; Templates are containers
Docker and nested virtualizationDocker, root, systemd and /dev/kvm on every machineRoot on VMs, so you can run your own Docker daemon and kernel modules; nested virtualization is not documented
GPUsNone on any sizeNvidia L4 up to H200, 1 to 8 per instance, on-demand, spot (Templates) or reserved, plus clusters
Biggest CPU machine16 vCPU / 32 GB / 251 GB disk on the $100 plan and upCPU VMs up to 32 vCPU / 128 GB
Stopping a machineA stopped sandbox has no compute charge and keeps its disk for at least 14 days; saved snapshots beyond the plan allowance cost $0.056 a day eachPause stops compute billing; the disk keeps billing at $0.10/GB-month for as long as the balance stays positive, and VMs need at least 100 GB
Snapshots and forkDisk snapshots every minute and on stop; fork a running sandbox (writes from the last minute or so can be missing)No snapshot, clone or fork command; pause keeps the whole disk on VMs and /home on containers; shared filesystems survive pause and destroy and attach to new GPU instances, and startup scripts rebuild the software
Desktop and computer use1920x1080 60fps desktop and Chrome, computer use and browser control, embeddable streamNo desktop offered; JupyterLab, VS Code in the browser and SSH. You set it up: install a VNC desktop on a root VM
Coding agentsSeven harnesses installed, including Claude Code, Codex and OpenCode, with a prompt, steer and events APIYou install the agent on the VM yourself; a CLI and skill file let an agent on your own machine create GPUs, run jobs and read logs
Reaching the machineHTTPS URLs for up to 50 ports, token-gated by default; public IPv6 and outbound IPv4; the IP changes at each resume, no static IPVMs get a public IP with every port open by default, and a reserved IP keeps it fixed; Templates expose chosen HTTP ports through proxy URLs
Network rulesOpen internet on every plan; no provider-side allowlistSecurity groups with inbound and outbound rules by port and IPv4 range, VPCs and reserved IPs, on VMs in India
Keeping keys out of the machineOptional AI credentials proxy ($1 a day it is on plus $1 per 1,000 requests); with it on, real keys of supported providers stay out of the sandboxNo provider proxy; keys go in as environment variables or uploaded files, or you run your own proxy
Scale to zeroNo wake on request; you start a stopped sandbox through the APIServerless model workers stop after an idle timeout and start again on the next request
RegionsGermany, Finland and France; no US or Asia region; you cannot pick a regionIndia only for new instances (IN1, IN2)
Compliance and transparencySOC 2 is in progress. We're open about where we stand: live status and data retention policy.No SOC 2 report published
Every feature Battleships tracks (43)
FeatureboatJarvislabs
Full VM (own kernel)YesYes
Docker insideYesYes
Nested virtualizationYesNot published
RootYesYes
SystemdYesNot published
Desktop GUIYesNo documented way
BrowserYesNo documented way
Computer-use APIYesNo documented way
SSHYesYes
Persistent diskYesYes
Pause/resumeYesYes
Automatic snapshotsYesNo documented way
Fork/cloneYesNo documented way
Live fork (no pause)YesNo documented way
Memory forkNo documented wayNo documented way
Custom image (Docker or snapshot)YesYes
≥24 h sessionsYesYes
Idle auto-stopNo documented wayYes
Wake on requestNo documented wayYes
HTTPS preview URLsYesYes
Raw TCP inboundYesYes
Public IPv4No documented wayYes
Egress allowlistNo documented wayYes
Secret proxyYesNo documented way
Secret proxy for any APIYesNo documented way
Preinstalled agentsYesNo documented way
Agent harness APIYesNo documented way
MCP serverNo documented wayNo documented way
GPUNo documented wayYes
WindowsNo documented wayNo documented way
Arm64No documented wayNo documented way
Self-hostingNo documented wayNo documented way
BYOCNo documented wayNo documented way
Open sourceNo documented wayNo documented way
Scoped API keysYesNot published
Spend limitsYesYes
Usage per sandbox (API)YesYes
Audit logsNo documented wayNot published
SSONo documented wayNo documented way
SOC 2No documented wayNo documented way
HIPAANo documented wayNo documented way
EU data residencyNo documented wayNo documented way
Zero data retentionYesNot published

Performance

boat28.06 runs/s
JarvislabsNot measured

Jarvislabs is not in the public benchmarks we use, so we cannot say which is faster. In StarSling's run of 3 October 2026 (run 37073680030), boat did 28.06 V8 Web Tooling Benchmark runs per second 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. Jarvislabs publishes GPU benchmarks for its H200 VMs, but no CPU benchmark for its CPU VMs.

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

Scenarioboat, a monthJarvislabs, 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$21 · On-demand
One agent that never stops
4 vCPU / 8 GB, 50 GB disk, running 24/7 all month
$26 · $20/mo$71 · On-demand
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$892 · On-demand
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$231 · On-demand · 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$514 · On-demand · 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, spent per second on running sandboxes; a 4 vCPU / 8 GB sandbox costs $0.036 an hour. Included VM time does not carry over. Each plan caps starts (the $20 plan: 12 a minute, 60 an hour, 200 a day); extra starts cost $0.03 to $0.07 each. A stopped sandbox has no compute charge and keeps its disk for at least 14 days. Saved snapshots beyond the plan allowance cost $0.056 a day each, also while stopped.

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, with 4 GB of RAM per vCPU, so 4 vCPU / 16 GB costs $0.10 an hour. The disk is extra at $0.10/GB-month, billed while running and while paused, with at least 100 GB on a VM. Jarvislabs publishes no start cap.

Limits in those scenarios

Jarvislabs does not publish how many instances an account can run at once, so 300 sandboxes for your users or 1,000 short jobs at once are not confirmed until you ask. A paused VM, including a CPU VM, keeps its whole disk; GPU containers (Templates) keep only /home. Its smallest CPU VM is 2 vCPU / 8 GB, with at least 100 GB of disk. On boat the limit is a sandbox count by plan plus starts per minute, hour and day. The 1,000-job burst hits the start limits of the $2,000 plan: 90 included starts a minute and 600 an hour. Extra starts cost $0.03 to $0.07 each, and above 270 a minute a start fails with 429, so 1,000 starts take about 4 minutes. boat never queues a start. A stopped boat sandbox keeps its disk for at least 14 days; after that boat can delete it unless you save a snapshot.

ScenarioboatJarvislabs
One coding agent, workdaysNone for this scenarioNone for this scenario
One agent that never stopsNone 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)
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)
1,000 short jobs at once
  • 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
  • not confirmed: how many machines can run at once (you need 1,000; the typical published limit is 50)
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 Jarvislabs when

your work needs Nvidia GPUs, model serving that scales to zero, provider-side firewall rules, or machines in India.

  • Nvidia GPUs by the minute. Useful if your work trains, fine-tunes or serves models: Jarvislabs rents Nvidia GPUs from L4 to H200 by the minute.
  • Model serving that scales to zero. Useful for inference: Jarvislabs serves open models on GPU workers that stop when idle and start on the next request.
  • Network rules, reserved IPs and India regions. Useful for teams in India, or who need firewall rules set by the provider: Jarvislabs has security groups, VPCs and reserved IPs.

Use boat when

you run agents on CPU: VMs that come with coding agents, a desktop and HTTPS ports, that snapshot every minute, fork while running and have no compute charge while stopped.

  • Snapshots every minute, live fork, no compute charge when stopped. Agents sit idle between tasks and often need to branch work. On Jarvislabs every paused VM still bills at least 100 GB of disk, and copying a set-up machine means a new instance plus a startup script or shared filesystem.
  • Coding agents and a desktop built in. Without these, you write and maintain the setup scripts, the agent runner and the desktop stream for every machine. Jarvislabs' CLI lets an agent on your laptop manage machines, not work inside one.
  • HTTPS ports and an optional credentials proxy. An agent that holds a real API key can leak it in a log or a commit. On Jarvislabs you set up TLS and firewall rules for each preview server yourself.

Questions people ask

Is boat cheaper than Jarvislabs?

It depends on the scenario. One coding agent on workdays comes to $20 a month on boat and $21 on Jarvislabs. One agent running all month is $26 versus $71, and 50 agents in parallel are $317 versus $892; the Jarvislabs 4 vCPU VM has 16 GB of RAM and at least 100 GB of disk. Sandboxes for your users come to $200 on boat and $231 on Jarvislabs, but Jarvislabs does not confirm 300 at once. For 1,000 short jobs at once Jarvislabs comes to $514 if it allows 1,000 machines. boat comes to $8,800 on the $2,000 plan with paid starts and still cannot start 1,000 in one minute. Below about $20 of use a month, Jarvislabs' no-fee wallet costs less.

Does boat have GPUs like Jarvislabs?

No. boat runs Linux VMs on AMD Ryzen 7 9700X and Ryzen 9 9950X hosts dedicated to boat, with no GPU on any size. If your agents need to train or serve models, rent the GPUs on Jarvislabs.

Does a paused Jarvislabs instance cost money?

Yes, for storage. Pausing stops compute billing, but the disk keeps billing at $0.00014 per GB-hour, and VMs need at least 100 GB. A stopped boat sandbox has no compute charge and keeps its disk for at least 14 days. Saved snapshots beyond the plan allowance cost $0.056 a day each.

What happens when the balance runs out?

Jarvislabs' FAQ says instances pause automatically when the balance reaches zero. If the balance goes negative, all data is permanently deleted and cannot be recovered. On boat an empty wallet gets a 24-hour grace period; then boat snapshots and stops the sandboxes.

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. Jarvislabs creates new instances only in its India regions; its old EU1 region no longer accepts new instances.

Is boat SOC 2 compliant?

SOC 2 is in progress, and boat has no SOC 2 report today. Jarvislabs publishes no SOC 2 report either. 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

More comparisons