Sprites vs Unikraft Cloud

Both run each workload in its own Firecracker microVM that sleeps when idle. Sprites gives each agent a ready Ubuntu computer with a 100 GB disk and bills the CPU and memory it really uses. Unikraft Cloud turns your Dockerfile into a small VM that wakes in milliseconds, sold as flat plans that cap how much can run at once.

The companies and products

Sprites

Sprites is Fly.io's product for agents: persistent Linux computers you create by API or CLI, which sleep when idle and wake on the next request.

Each Sprite is a Firecracker microVM with 8 vCPU, memory that scales from 2 GB to 16 GB as needed, and a 100 GB ext4 disk backed by object storage. It runs one managed Ubuntu image with Claude Code, Codex, Gemini CLI and Cursor preinstalled. It gets an HTTPS URL that wakes it, and it bills only for the CPU and memory it uses while awake. It is built for coding agents, dev environments and user code that sit idle most of the time.

Unikraft Cloud

Unikraft Cloud is a microVM cloud from Unikraft Inc. It runs any Dockerfile-based workload as a minimal Linux microVM, with cold starts it states as under 10 ms and scale-to-zero.

Your Dockerfile becomes the VM image at build time. Each instance runs on a customized Firecracker VMM and can go into standby when no traffic arrives. It is a general compute platform for dense, bursty work such as HTTP services, browsers and agent fleets. It sells flat self-serve plans, plus Enterprise dedicated hosts, on-prem and bring your own cloud. You reach instances through services, the CLI and a sandbox plugin for commands and files. For SSH or a desktop, you add them to your image with its official guides.

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. “63rd cheapest of 374” means 62 of the other 373 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 workloadSprites: price rankUnikraft Cloud: price rankboat: price rank
Software factory
100 at once · 4 vCPU / 8 GB · 2,200 sessions of 8 h a month
Sprites gives an agent a ready Ubuntu machine with Docker and a 100 GB disk, while Unikraft builds your Dockerfile into the VM and documents no container runtime inside; boat adds systemd and /dev/kvm on every plan.
101st of 365, with limits
$546 a month
Not ranked: misses a requirement5th cheapest of 365
$634 a month
Always-on AI employees
50 machines 24/7 · 2 vCPU / 4 GB
An always-on assistant drops its open connections on every Sprite pause, and on Unikraft it shares the Team pool of 8 GiB with every other running instance. A boat sandbox keeps running once you turn auto-stop off (default 1 hour).
214th of 361, with limits
$1,166 a month
Not ranked: misses a requirement6th 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 both: Sprites bills only real CPU and memory while awake, and Unikraft wakes in milliseconds, though its self-serve plans stop at 24 running instances.
99th of 336, with limits
$140 a month
Not ranked: misses a requirement189th 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
Neither fits 300 user sandboxes at once as published: Sprites does not confirm that many running, and Unikraft Pro runs 24, so you need a plan or contract from sales.
61st of 349, with limits
$428 a month
Not ranked: misses a requirement3rd 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
114th of 349, with limits
$6,540 a month
Not ranked: misses a requirement39th 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
130th of 359, with limits
$545 a month
Not ranked: misses a requirement10th cheapest of 359
$200 a month
CI runners
40 at once · 8 vCPU / 16 GB · 6,000 sessions of 12 min a month
CI that builds Android apps or VM images needs /dev/kvm: the Sprites docs do not mention it, Unikraft keeps it for Enterprise, and boat has it on every plan.
63rd cheapest of 374
$476 a month
Not ranked: misses a requirement2nd cheapest of 374
$86 a month
24/7 dev boxes
1 machine 24/7 · 4 vCPU / 8 GB
Our default ranking puts boat at #13 ($26 a month), Sprites at #14 ($27) and Unikraft at #19 ($39). Sprites tunnels SSH through its CLI, Unikraft reaches an SSH server in your image through a TLS tunnel, and boat gives direct SSH and systemd.
120th cheapest of 371
$27 a month
121st cheapest of 371
$39 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 has a prebuilt desktop. On Sprites you install a display, a browser and a stream yourself; Unikraft documents a VNC desktop you build into your image and resume from a snapshot. boat streams a 60fps desktop with an agent built in.
132nd of 367, with limits
$136 a month
Not ranked: misses a requirement7th cheapest of 367
$200 a month
Browser-use agents
50 at once · 2 vCPU / 4 GB · 30,000 sessions of 10 min a month
Teams run their own headless Chrome on Unikraft at scale, and on Sprites you install one yourself; boat ships Chrome on a desktop you can watch.
236th of 356, with limits
$122 a month
Not ranked: misses a requirement7th 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
279th of 343, with limits
$206 a month
Not ranked: misses a requirement6th 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
139th of 327, with limits
$4,113 a month
Not ranked: misses a requirement73rd 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
243rd of 351, with limits
$223 a month
Not ranked: misses a requirement3rd cheapest of 351
$200 a month
GPU eval jobs
10 at once · 8 vCPU / 32 GB · 500 sessions of 30 min a month
Not ranked: misses a requirementNot ranked: misses a requirementNot 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

FeatureSpritesUnikraft Cloudboat
IsolationFirecracker microVM with its own kernelMinimal Linux microVM on a customized Firecracker VMM; full VMs on EnterpriseFull VM with its own kernel, on physical hosts dedicated to boat (AMD Ryzen 7 9700X and Ryzen 9 9950X); vCPUs are shared
Machine sizeFixed 8 vCPU and 100 GB disk; memory scales from 2 GB to 16 GB as needed and bills on usePlan pool shared by all running instances: 2 vCPU / 4 GiB, 8 vCPU / 8 GiB or 24 vCPU / 32 GiB; per-instance maximum not published4 vCPU / 8 GB by default, 2 to 16 vCPU per sandbox; 16 vCPU / 32 GB needs the $100 plan or higher; disk is fixed per size (51 to 251 GB)
ImageOne managed Ubuntu image; you install on top of itYour Dockerfile becomes the VM imageboat's Ubuntu 24.04 image or a saved snapshot; you cannot boot your own Docker or OCI image
Docker and systemd insideRoot and Docker (a user reports docker exec fails for containers that do not run as root); services run through the Sprites services API, not systemdRuns as root; the docs describe no container runtime inside a running instanceRoot, Docker with Compose and systemd, like any Ubuntu machine
Nested virtualizationNo /dev/kvm in the docsYes, with a per-instance flag and permission, Enterprise onlyYes, /dev/kvm for Android emulators and VMs on every plan
SSHThrough the sprite proxy CLI, with an SSH server you installYes, with setup: run sshd in your image and reach it through a TLS service port plus a local tunnel (socat or 'unikraft instances tunnel'); no built-in SSH endpointBuilt in on every sandbox, through a shared IPv4 host and port; no tunnel
Idle and wakePauses about 30 seconds after activity stops; wakes on the next request in 100 to 500 ms with memoryStandby after a 1 second idle cooldown by default; wakes on traffic in milliseconds with memory restoredAuto-stop timer (default 1 hour, up to 30 days, or off on a paid plan) that does not watch for idle; started again by API, like a reboot; no wake on request
Fork and checkpointsFilesystem checkpoints that restore in place; no fork command in the CLI or API docsCheckpoint memory and volumes of a running microVM, then start new instances from itFork a running sandbox from its last 1-minute disk save, without memory; disk saved every minute and at each stop
Inbound accessOne HTTPS URL to one HTTP port; other ports through the sprite proxy CLIServices on its load balancer: HTTP, HTTPS and TLS-wrapped TCP, custom domains; no public IP per instanceUp to 50 HTTPS URLs, token-gated by default; public IPv6 for raw ports; no dedicated IPv4
Outbound rulesDNS-based domain allowlist set from outside; private IPs always blockedNetwork shield filters traffic, Enterprise only, limited accessOpen internet, no provider-side allowlist
Keeping API keys out of the sandboxConnectors gateway holds the token for any HTTP API, with path allow and block listsNetwork shield can inject secrets into HTTP traffic, Enterprise only, limited accessOptional AI credentials proxy on every plan, $1 per day on plus $1 per 1,000 requests; covers supported model providers; other secrets still enter the sandbox
Coding agentsClaude Code, Codex, Gemini CLI and Cursor preinstalled, run through exec or a consoleNone installed; you add the agent to your own imageSeven agent harnesses installed, with a prompt, steer and events API to drive them from outside
Desktop and browserNo desktop or browser built in; you install a browser, display server and stream yourselfNo prebuilt desktop or computer-use agent; an official VNC/noVNC desktop recipe you build into your image, snapshotted after login so it resumes in millisecondsDesktop and Chrome built in, streamed at 1920x1080, 60fps, with computer-use tools
ComplianceSOC 2 Type II; HIPAA package with a pre-signed BAA on paid plansSOC 2 Type II certified; HIPAA and audit logs on EnterpriseSOC 2 in progress; no HIPAA BAA documented
RegionsNo region option when you create a SpriteDallas, Frankfurt, San Francisco, Singapore and Washington DC, more on requestGermany, Finland and France; no US or Asia region; you cannot pick one
Every feature Battleships tracks (43)
FeatureSpritesUnikraft Cloudboat
Full VM (own kernel)YesYesYes
Docker insideYesNo documented wayYes
Nested virtualizationNo documented wayYesYes
RootYesYesYes
SystemdNo documented wayNot publishedYes
Desktop GUINo documented wayWith your own setupYes
BrowserNo documented wayWith your own setupYes
Computer-use APINo documented wayNo documented wayYes
SSHWith your own setupWith your own setupYes
Persistent diskYesYesYes
Pause/resumeYesYesYes
Automatic snapshotsYesYesYes
Fork/cloneNo documented wayYesYes
Live fork (no pause)No documented wayYesYes
Memory forkNo documented wayYesNo documented way
Custom image (Docker or snapshot)YesYesYes
≥24 h sessionsYesYesYes
Idle auto-stopYesYesNo documented way
Wake on requestYesYesNo documented way
HTTPS preview URLsYesYesYes
Raw TCP inboundNo documented wayNot publishedYes
Public IPv4No documented wayNo documented wayNo documented way
Egress allowlistYesYesNo documented way
Secret proxyYesYesYes
Secret proxy for any APIYesYesYes
Preinstalled agentsYesNo documented wayYes
Agent harness APINo documented wayNo documented wayYes
MCP serverYesNo documented wayNo documented way
GPUNo documented wayYesNo documented way
WindowsNo documented wayNo documented wayNo documented way
Arm64No documented wayYesNo documented way
Self-hostingNo documented wayYesNo documented way
BYOCNo documented wayYesNo documented way
Open sourceNo documented wayNo documented wayNo documented way
Scoped API keysNot publishedNot publishedYes
Spend limitsNot publishedNot publishedYes
Usage per sandbox (API)No documented wayNo documented wayYes
Audit logsNot publishedYesNo documented way
SSOYesNo documented wayNo documented way
SOC 2YesYesNo documented way
HIPAAYesYesNo documented way
EU data residencyNo documented wayYesNo documented way
Zero data retentionNot publishedNot publishedYes

Performance

SpritesNot measured
Unikraft CloudNot measured
boat28.06 runs/s

Sprites and Unikraft Cloud are 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. Unikraft states cold starts under 10 ms and Sprites states wakes of 100 to 500 ms, but those are their own figures for start time, not CPU speed.

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. Sprites and Unikraft Cloud 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.

ScenarioSprites, a monthUnikraft Cloud, 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
$23 · Pay-as-you-go$39 · Hobby$20 · $20/mo
One agent that never stops
4 vCPU / 8 GB, 50 GB disk, running 24/7 all month
$92 · Pay-as-you-go$39 · Hobby$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,120 · Pay-as-you-goNot ranked: misses a requirement$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
$314 · Pay-as-you-go · with limitsNot ranked: misses a requirement$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
$1,134 · Pay-as-you-go · with limitsNot ranked: misses a requirement$8,800 · $2000/mo · with limits

Sprites: Sprites bills CPU time at $0.0385 per CPU-hour and actual memory at $0.021875 per GB-hour, only while the Sprite is awake. Storage costs about $0.50 per GB-month for hot data while awake and about $0.02 per GB-month for cold data while it is kept. Optional plans add fixed CPU-hour, memory-hour and storage allowances, and usage above them bills at the normal rates.

Unikraft Cloud: Unikraft charges a flat monthly fee for a pool of running capacity: free for 2 vCPU / 4 GiB with no card, $39 for 8 vCPU / 8 GiB and $199 for 24 vCPU / 32 GiB. Standby instances do not count against the pool. It publishes no per-hour, disk or egress price, so anything bigger is an Enterprise quote.

Unikraft Cloud: Plans cost $20, $100, $500 or $2,000 a month, and the whole plan price comes back as VM time for that month. A card is required, also for the 7-day trial. A running sandbox bills per second at full rate, busy or idle: $0.036 an hour for 4 vCPU / 8 GB. 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 AI credentials proxy still charge while sandboxes are stopped. The $20 plan includes 12 starts a minute and 200 a day; extra starts cost $0.03 to $0.07.

Limits in those scenarios

Unikraft's limits are pools that every running instance shares: one 4 vCPU / 8 GB agent fills the Team plan, so 50 agents, 300 user sandboxes and 1,000 short jobs fit no self-serve plan. Sprites does not publish how many machines can run at once on pay as you go, so 300 user sandboxes and 1,000 jobs at once are not confirmed, and an always-on agent needs a task hold renewed every hour. boat caps sandboxes running at once by plan (100 on $20, up to 2,000 on $2,000) and auto-stops after 1 hour by default; on a paid plan you can turn auto-stop off. At 1,000 short jobs at once, even the $2,000 plan includes 90 starts a minute; extra starts cost $0.03 to $0.07, and starts above 270 a minute fail with 429. boat never queues a start.

ScenarioSpritesUnikraft Cloudboat
One coding agent, workdaysNone for this scenario
  • flat pool: the tier is billed whether used or not
  • disk beyond 0 GiB: price unknown
  • egress price not published
None for this scenario
One agent that never stopsNone for this scenario
  • flat pool: the tier is billed whether used or not
  • disk beyond 0 GiB: price unknown
  • egress price not published
None for this scenario
50 agents in parallel
  • how many machines can run at once: limit not published, probably fine at 50 (the typical published limit is 50)
  • no pool tier with 200 vCPU / 400 GiB for 50 VMs
  • no published per-resource rate
None for this scenario
Sandboxes for your users
  • not confirmed: how many machines can run at once (you need 300; the typical published limit is 50)
  • no pool tier with 600 vCPU / 1,200 GiB for 300 VMs
  • no published per-resource rate
None for this scenario
1,000 short jobs at once
  • not confirmed: how many machines can run at once (you need 1,000; the typical published limit is 50)
  • no pool tier with 2,000 vCPU / 4,000 GiB for 1,000 VMs
  • no published per-resource rate
  • 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 Sprites when

you want a ready Ubuntu computer for a coding agent that sits idle much of the day, billed only for what it uses, with a domain allowlist on self-serve plans.

  • A ready computer for coding agents. Each Sprite is an Ubuntu machine with a 100 GB disk and Claude Code, Codex, Gemini CLI and Cursor already installed.
  • Billed by real use. Sprites bills the CPU time and memory a machine actually uses while awake, so a mostly idle agent costs little.
  • Egress allowlist and connectors, self-serve. Teams that must limit where agents connect get a domain allowlist and API path rules without an Enterprise contract.

Use Unikraft Cloud when

you run many small services or headless browsers from a Dockerfile that must wake in milliseconds, need US or Asia regions, or want GPUs or on-prem under Enterprise.

  • Millisecond starts from your Dockerfile. Best for many small services built from a Dockerfile that sleep most of the time and must answer in milliseconds.
  • Checkpoints you can start new instances from. Unikraft can checkpoint a running microVM's memory and start new instances from it, with warm caches.
  • Regions, a free plan, GPUs and your own hardware. Unikraft runs in the US, Frankfurt and Singapore, has a free plan with no card, and Enterprise adds GPUs, arm64, on-prem or your own cloud.

Where boat fits

Sprites and Unikraft Cloud are both built around machines that sleep most of the time. If your agents work for hours, run Docker and emulators, need a screen, or run as fleets of 50 or more, look at boat: each sandbox is a full VM that keeps running until auto-stop or until you stop it.

A full machine with systemd and /dev/kvm

Sprites runs services through its own API instead of systemd and has no /dev/kvm in its docs. Unikraft documents no container runtime inside and keeps nested virtualization for Enterprise. On either, Android emulators and stacks built on systemd units need rework or a sales contract.

Agents that keep working, and fleets that fit

A Sprite drops open connections on every pause unless a task hold, renewed each hour, keeps it awake. Unikraft's biggest self-serve pool is 24 vCPU / 32 GiB, so 50 agents at 4 vCPU / 8 GB need an Enterprise quote. boat runs 100 sandboxes at once from the $20 plan, and with auto-stop off there is no session cap.

A desktop and SSH out of the box

On both, you build the display, browser and stream yourself, and SSH goes through a tunnel. Unikraft documents a VNC desktop recipe, and Sprites tunnels SSH through its CLI. boat has a 60fps desktop, direct SSH, 50 HTTPS URLs and an API to drive agents inside.

Use boat when your agents need a full machine for hours: Docker, systemd, emulators, direct SSH, a desktop and browser, forks, and fleets of full-size sandboxes without a sales call. Compare it one to one: boat vs Sprites and boat vs Unikraft Cloud.

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 Sprites cheaper than Unikraft Cloud?

For one coding agent on workdays, yes: $23 a month on Sprites against the $39 Team pool on Unikraft. For one agent that never stops, Unikraft's flat $39 beats $92 on Sprites. For 50 agents in parallel, Sprites comes to $1,120 and no self-serve Unikraft plan fits. boat comes to $20, $26 and $317 for the same three.

Which one is faster?

Unikraft states cold starts under 10 ms, and a Sprite wakes in 100 to 500 ms, by each provider's own figures. Neither is in the public CPU benchmarks we use, so we cannot compare CPU speed. 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, second of 15.

Can Sprites or Unikraft Cloud run Docker?

Users run Docker inside Sprites, though a user reports docker exec failing for containers that do not run as root, and Sprites does not run systemd. Unikraft uses your Dockerfile to build the VM itself and does not document a container runtime inside. A boat sandbox runs Docker, systemd and /dev/kvm.

Can I SSH into Sprites or Unikraft Cloud?

Yes, with setup on both. On Sprites you install an SSH server and tunnel it through the sprite proxy CLI. On Unikraft you add an SSH server to your image, expose it as a TLS service, and connect through a local tunnel (socat or 'unikraft instances tunnel'). Every boat sandbox takes SSH directly, with no tunnel.

Which one keeps an agent running all day?

Neither by default. A Sprite pauses about 30 seconds after activity stops unless a task hold keeps it awake for up to an hour at a time, and Unikraft puts idle instances into standby. A boat sandbox stops after 1 hour by default; on a paid plan you can turn auto-stop off, and it keeps running until you stop it.

Where do they run?

Sprites has no region option. Unikraft runs in Dallas, Frankfurt, San Francisco, Singapore and Washington DC, with more on request. boat runs on machines in Germany, Finland and France, you cannot pick a region, and snapshot copies can be stored outside the EU.

Try boat

Install the CLI, then run boat new.

7-day free trial

More comparisons