boat vs Verda
Verda is a GPU cloud: you rent Nvidia GPUs and CPU virtual machines by the hour in Helsinki, and you set up the software yourself. boat is built for agents: each VM comes with a desktop and coding agents, saves its disk every minute, and has no compute charge while stopped.
Where boat stands out
No compute charge while stopped, disk saved every minute, live fork
A stopped boat sandbox has no compute charge, and boat keeps its disk for at least 14 days. A saved snapshot keeps it longer; extra saved snapshots cost $0.056 a day. boat saves the disk every minute while the sandbox runs and once more at each stop, and you can fork a running sandbox. Memory and running programs are not saved, so a resume is like a reboot. On Verda a shut-down instance keeps billing at its full rate, and you clone a volume after its instance is shut down.
Coding agents and a desktop installed
boat installs seven coding-agent harnesses, including Claude Code, Codex and OpenCode, in each sandbox, and you drive them with a prompt, steer and events API. Every sandbox also has a 1920x1080, 60 fps desktop with Chrome and computer tools. On a Verda instance you set these up yourself: install the agent and a browser, and add a VNC desktop with Verda's guide.
HTTPS URLs and an optional keys proxy
Each boat sandbox can serve up to 50 public HTTPS URLs, token-gated by default, with no certificates to set up. boat's optional AI credentials proxy costs $1 for each day it is on plus $1 per 1,000 requests. With it on, the real keys of supported providers never enter the sandbox; other environment variables and secrets still do. A Verda instance gets a free public IPv4, and you set up TLS, the firewall and key handling yourself.
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
Verda
Verda, called DataCrunch until 2025, is a European AI cloud that rents Nvidia GPUs, CPU machines and GPU clusters.
You create a GPU or CPU instance, add a disk and an SSH key, and get a full Linux VM with root and its own public IP. Verda also sells GPU clusters with InfiniBand, serverless containers that scale to zero, and a per-token inference API for open models. It is built for teams that train, fine-tune and serve AI models. It is not packaged as a sandbox for agents, so you install the agent tools yourself.
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 | Verda: price rank |
|---|---|---|
| Software factory 100 at once · 4 vCPU / 8 GB · 2,200 sessions of 8 h a month Verda gives you a raw VM: you install the agent and its tools yourself. A shut-down Verda instance keeps billing, so to pause an agent you delete the instance and keep its volume at $0.20/GiB-month. On boat a stopped sandbox has no compute charge and keeps its disk for at least 14 days. | 5th cheapest of 365 $634 a month | 119th of 365, with limits $788 a month |
| Always-on AI employees 50 machines 24/7 · 2 vCPU / 4 GB An always-on assistant fits on a Verda CPU VM. You set it up: install the agent, a browser and a desktop (Verda has a VNC guide). boat ships them installed, at $26 a month for one sandbox that runs all month against $45 on Verda. | 6th cheapest of 361 $657 a month | 193rd of 361, with limits $901 a month |
| Code interpreter bursts 100 at once · 1 vCPU / 2 GB · 200,000 sessions of 1 min a month Verda's serverless containers scale to zero and wake on a request, which suits short bursts. boat has no wake on request, and each create or resume counts against the plan's start limits. | 189th of 336, with limits $2,000 a month | 103rd of 336, with limits $165 a month |
| Sandboxes for your users 300 at once · 2 vCPU / 4 GB · 30,000 sessions of 23 min a month Verda does not publish how many instances an account can run at once, so confirm a quota for 300 sandboxes first. On boat, the $100 plan runs 300 at once with 840 starts a day included. | 3rd cheapest of 349 $209 a month | 77th of 349, with limits $629 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 | 23rd of 349, with limits $1,097 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 | 100th of 359, with limits $123 a month |
| CI runners 40 at once · 8 vCPU / 16 GB · 6,000 sessions of 12 min a month Both fit. Verda's dedicated EPYC cores suit CI runners that you create and delete per job. boat bills per second and has no compute charge between jobs, but each create, fork or resume counts as a start (200 a day included on the $20 plan). | 2nd cheapest of 374 $86 a month | 9th cheapest of 374 $142 a month |
| 24/7 dev boxes 1 machine 24/7 · 4 vCPU / 8 GB | 19th cheapest of 371 $26 a month | 37th cheapest of 371 $45 a month |
| Computer-use agents 50 at once · 4 vCPU / 8 GB · 20,000 sessions of 15 min a month On Verda you set it up: install XFCE and TigerVNC with Verda's guide, then add a computer-use agent. boat ships a 1920x1080, 60 fps desktop with computer tools for agents. | 7th cheapest of 367 $200 a month | 129th of 367, with limits $123 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 | 234th of 356, with limits $110 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 | 250th of 343, with limits $103 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 | 86th of 327, with limits $2,057 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 | 172nd of 351, with limits $66 a month |
| GPU eval jobs 10 at once · 8 vCPU / 32 GB · 500 sessions of 30 min a month Verda fits and boat does not: Verda rents Nvidia GPUs from V100 to GB300, and boat has no GPU on any size. | Not ranked: misses a requirement | 20th cheapest of 102 $1,241 a month |
| 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 |
Key features
| Feature | boat | Verda |
|---|---|---|
| Kind of product | Sandboxes for AI agents: VMs with coding agents, a desktop and HTTPS hosting installed | GPU and CPU cloud: raw VMs, GPU clusters, serverless containers, a per-token inference API for open models, and block, shared and object storage |
| Isolation and CPU | Every sandbox is a full VM with its own kernel, on a host dedicated to boat; vCPUs are shared, not dedicated cores | Every instance is a full VM on KVM/QEMU; CPU instances have dedicated AMD EPYC cores |
| Docker and nested virtualization | Docker with BuildKit and Compose, root, systemd and /dev/kvm installed on every sandbox | Root on your own VM: you install Docker yourself; Verda's docs do not cover nested virtualization |
| GPUs | No GPU on any size; graphics run on the CPU | Nvidia V100 up to GB300, on-demand or spot, plus clusters with InfiniBand |
| Biggest machine | 16 vCPU / 32 GB / 251 GB disk, on the $100 plan and up | CPU instances up to 360 vCPU / 1,440 GB |
| Stopping a machine | A stopped sandbox has no compute charge and keeps its disk for at least 14 days; extra saved snapshots bill $0.056/day | A shut-down instance keeps billing at its full rate; Delete stops the instance charge, and kept volumes bill at $0.20/GiB-month |
| Snapshots and fork | Disk saved every minute and at each stop; fork a running sandbox from its last 1-minute snapshot (the last minute of writes can be missing); memory is not saved | Clone a volume into a new volume, billed at $0.20/GiB-month, after you shut down its instance or detach it |
| Desktop and computer use | 1920x1080, 60 fps desktop and Chrome stream with computer tools for agents, embeddable | You set it up: Verda's guide installs XFCE and TigerVNC on the instance |
| Coding agents | Seven harnesses installed (Claude Code, Codex, OpenCode and more), with a prompt, steer and events API | You set it up: install the agent on the VM yourself; Verda's MCP server and CLI agent mode let an outside agent manage Verda machines |
| Reaching the machine | Up to 50 HTTPS URLs per sandbox, token-gated by default; public IPv6 and outbound IPv4; the IP changes at each resume | A free public IPv4 per instance and SSH; you set up TLS and the firewall (ufw) yourself |
| Keeping keys out of the machine | Optional AI credentials proxy ($1 per day on, plus $1 per 1,000 requests) for supported model providers and HTTPS APIs you register; other secrets still enter the sandbox | A secrets store for serverless containers; on instances you place keys yourself or run your own proxy |
| Scale to zero | No wake on request; you start a stopped sandbox through the API, and each start counts against the plan's start limits | Serverless containers scale to zero when idle and start again on the next request |
| Regions | Machines in Germany, Finland and France; you cannot pick a region; snapshot copies can be stored outside the EU | Three data centers in Helsinki, Finland; no region outside Finland is listed |
| 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 | Verda |
|---|---|---|
| Full VM (own kernel) | Yes | Yes |
| Docker inside | Yes | Yes |
| Nested virtualization | Yes | Not published |
| Root | Yes | Yes |
| Systemd | Yes | Not published |
| Desktop GUI | Yes | With your own setup |
| Browser | Yes | No documented way |
| Computer-use API | Yes | No documented way |
| SSH | Yes | Yes |
| Persistent disk | Yes | Yes |
| Pause/resume | Yes | No documented way |
| Automatic snapshots | Yes | No documented way |
| Fork/clone | Yes | Yes |
| 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 | Yes |
| Idle auto-stop | No documented way | No documented way |
| Wake on request | No documented way | Yes |
| HTTPS preview URLs | Yes | Yes |
| Raw TCP inbound | Yes | No documented way |
| Public IPv4 | No documented way | Yes |
| 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 | No documented way |
| Agent harness API | Yes | No documented way |
| MCP server | No documented way | Yes |
| GPU | No documented way | Yes |
| Windows | No documented way | No documented way |
| Arm64 | No documented way | No documented way |
| Self-hosting | No documented way | No documented way |
| BYOC | No documented way | No documented way |
| Open source | No documented way | No documented way |
| Scoped API keys | Yes | Not published |
| Spend limits | Yes | Yes |
| Usage per sandbox (API) | Yes | Yes |
| Audit logs | No documented way | Yes |
| SSO | No documented way | No documented way |
| 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
Verda 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 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. Verda says its CPU instances use dedicated AMD EPYC cores clocked at 3.3 GHz.
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. Verda 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 | Verda, 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 | $18 · Pay as you go |
| One agent that never stops 4 vCPU / 8 GB, 50 GB disk, running 24/7 all month | $26 · $20/mo | $45 · Pay as you go |
| 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 | $622 · Pay as you go |
| 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 | $254 · Pay as you go · 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 | $507 · Pay as you go · with limits |
boat: Plans cost $20, $100, $500 or $2,000 a month, and the whole plan price comes back as VM time for that month. Included VM time expires at the end of the billing period. A 4 vCPU / 8 GB sandbox costs $0.036 an hour, billed per second from when the machine is provisioned. A stopped sandbox has no compute charge and keeps its disk for at least 14 days. Extra saved snapshots ($0.056 a day each) and the AI credentials proxy still charge while sandboxes are stopped. Above the included starts (200 a day on $20), an extra start costs $0.03 to $0.07.
Verda: Verda charges a prepaid balance in 10-minute blocks and refunds the unused part when you delete early. CPU machines cost $0.012 per vCPU-hour with 4 GB of RAM each, so 4 vCPU / 16 GB is $0.048 an hour. Spot CPU machines cost 40% of that and can be taken back. The disk is extra at $0.20/GiB-month, a shut-down instance keeps billing until you delete it, and reservations of 1 month to 2 years cut 2% to 25%.
Limits in those scenarios
Verda 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 need a confirmed quota first. Verda's smallest CPU machine is 4 vCPU / 16 GB, so a 2 vCPU job pays for 4 vCPU there. If a Verda balance runs out, its instances are stopped and its volumes deleted, with 96 hours to restore them. On boat the limits are sandboxes at once and starts per minute, hour and day, by plan. The 1,000-job burst needs about 6,667 starts a day, against 2,400 included on the $2,000 plan; extra starts are paid, starts above 270 a minute fail with 429, and boat never queues a start. A stopped boat sandbox keeps its disk for at least 14 days; if a machine fails, you lose what was written after the last good snapshot. With an empty boat wallet you get a 24-hour grace period, then boat snapshots and stops the sandboxes.
| Scenario | boat | Verda |
|---|---|---|
| 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 Verda when
your work needs GPUs, a GPU cluster, a single very large CPU machine with dedicated cores, an inference endpoint that scales to zero, or the lowest hourly price on spot CPU machines that can be taken back.
- GPUs and GPU clusters. Useful if your work trains, fine-tunes or serves models: Verda rents Nvidia GPUs from V100 to GB300, on-demand or spot.
- Very large CPU machines with dedicated cores. Useful for one huge job: Verda CPU instances go up to 360 dedicated vCPU and 1,440 GB of RAM.
- Containers that scale to zero. Useful for inference endpoints: Verda's serverless containers sleep when idle and wake on the next request.
Use boat when
you run agents: VMs that come with coding agents, a desktop and HTTPS URLs, an optional keys proxy, and no compute charge while stopped (the disk is kept for at least 14 days).
- No compute charge while stopped, disk saved every minute, live fork. Agents sit idle between tasks. On Verda you pay the full rate for an idle instance, or you delete it, keep the volume at $0.20/GiB-month and start a new instance to resume.
- Coding agents and a desktop installed. On Verda you write and maintain the setup scripts, the agent runner and the desktop stream for each machine. Verda's MCP server lets an agent manage machines, not work inside one.
- HTTPS URLs and an optional keys proxy. An agent that holds a real API key can leak it in a log or a commit. Without a proxy the key lives on the machine, and each preview server needs its own TLS and firewall rules.
Questions people ask
Is boat cheaper than Verda?
It depends on the scenario. One coding agent on workdays costs $20 a month on boat and $18 on Verda. One agent that runs all month costs $26 against $45, and 50 agents in parallel cost $317 against $622. For 300 sandboxes for your users, boat is $200 and Verda $254, but Verda's quota for 300 at once is not confirmed. For 1,000 short jobs at once, Verda comes to $507 and boat to about $8,800 with paid starts, and neither fits without higher limits. Verda spot CPU machines cost less per hour than boat, but can be taken back.
Is Verda the same company as DataCrunch?
Yes. DataCrunch was founded in Helsinki in 2020 and became Verda in 2025. It runs GPU and CPU instances, GPU clusters, serverless containers and an inference API from data centers in Finland.
Does boat have GPUs like Verda?
No. boat runs Linux VMs on AMD Ryzen hosts and has no GPU on any size; graphics run on the CPU. If your agents need to train or serve models, rent the GPUs on Verda.
Does a stopped Verda instance cost money?
Yes. Verda's docs say shut-down instances continue to charge your account, and Delete stops the instance charge. Volumes you keep after a delete bill at $0.20/GiB-month. A stopped boat sandbox has no compute charge and keeps its disk for at least 14 days. Extra saved snapshots and the AI credentials proxy still charge on boat while sandboxes are stopped.
Where does my data run?
Verda has three data centers in Helsinki, Finland. boat runs sandboxes on machines in Germany, Finland and France, and you cannot pick a region. boat can store snapshot copies outside the EU.
Is boat SOC 2 compliant?
SOC 2 is in progress, so boat has no SOC 2 report today. Live status is at status.ascii.dev and the data retention policy is at docs.boat.dev/data-retention. Verda says on its homepage that it is SOC 2 Type II, ISO 27001 and C5 certified.
Start a sandbox
Install the CLI, then run boat new.
7-day free trial
More comparisons
- boat vs Nebius
- boat vs Jarvislabs
- boat vs Cerebrium
- boat vs Runpod
- boat vs Crusoe
- boat vs Paperspace
- boat vs Replicate
- boat vs SF Compute
- boat vs E2B
- boat vs Daytona
- boat vs Modal
- boat vs Vercel Sandbox
- Runpod vs Verda
- Nebius vs Verda
- Crusoe vs Verda
- Paperspace vs Verda
- Jarvislabs vs Verda
- Hyperstack vs Verda
- Verda vs Cerebrium
- Verda vs Baseten