Fly.io Machines vs Deno Sandbox
Both run code in Firecracker microVMs. Fly.io Machines are an app hosting building block that runs your image for as long as you want. Deno Sandbox runs short pieces of untrusted code that Deno says start in under 200 ms and end after 30 minutes; it is closed to new customers since November 2026.
The companies and products
Fly.io Machines
Fly.io is an app hosting platform, and Machines are the microVMs underneath it that you can also start and stop through a REST API.
A Fly Machine boots your Docker image as a Firecracker microVM on Fly's own servers, in one of 17 regions. You pick a shared or performance CPU preset and mount one Volume at a time for data that must last. Fly Proxy can stop, suspend and wake Machines as traffic comes and goes. Machines themselves are an app-hosting building block; for agent sandboxes Fly also sells Sprites (see boat vs Sprites), so this page compares only the Machines product.
Deno Sandbox
Deno Sandbox comes from the company behind the Deno runtime and runs untrusted or AI-generated code in Linux microVMs. Since November 2026 it is not part of Deno Deploy plans and is not available to new customers.
Each sandbox is a Firecracker microVM with 2 vCPU, 768 MB to 4 GB of memory and a 10 GB disk that is wiped when it ends, created from a TypeScript or Python SDK. A bootable volume (Chicago only) can be the root disk and keep its files. Deno Deploy can limit outbound traffic to a host allowlist and swap placeholder secrets for real ones. A sandbox can be promoted to a Deno Deploy app.
- Isolation
- Firecracker microVM per sandbox
- Lifetime
- Up to 30 minutes
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. “123rd cheapest of 365” means 122 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 | Fly.io Machines: price rank | Deno Sandbox: price rank | boat: price rank |
|---|---|---|---|
| Software factory 100 at once · 4 vCPU / 8 GB · 2,200 sessions of 8 h a month Fly can keep an agent running for hours, where a Deno sandbox stops at 30 minutes. On Fly you build the image and keep files on a Volume or with opt-in persist_rootfs. boat fits with Docker, /dev/kvm and a desktop ready. | 123rd of 365, with limits $836 a month | No published price | 5th cheapest of 365 $634 a month |
| Always-on AI employees 50 machines 24/7 · 2 vCPU / 4 GB An assistant that works all month needs more than Deno's 30-minute sandboxes; a bootable volume in Chicago can carry its files to the next sandbox. On Fly it keeps files on a Volume. On boat, turn auto-stop off (1 hour by default) on a paid plan. | 186th of 361, with limits $816 a month | No published price | 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 Deno suits short code bursts: it says a sandbox starts in under 200 ms, and CPU bills only while code runs, but new customers cannot sign up. Fly bills per second with no plan fee. | 83rd of 336, with limits $94 a month | No published price | 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 Fly has no published cap on Machines at once but creates about one per second per app. Deno gives existing organizations 5 sandboxes at once by default and is closed to new customers. | 75th of 349, with limits $600 a month | No published price | 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 | 52nd of 349, with limits $2,838 a month | No published price | 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 | 124th of 359, with limits $457 a month | No published price | 10th 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 Docker images needs Docker, which you can install on Fly and Deno does not document. Neither documents /dev/kvm for Android emulators. boat has both. | 154th of 374, with limits $288 a month | No published price | 2nd cheapest of 374 $86 a month |
| 24/7 dev boxes 1 machine 24/7 · 4 vCPU / 8 GB A dev box that stays on all month works on Fly with a Volume, not on Deno with its 30-minute lifetime. boat saves the disk every minute and at each stop, with no compute charge while stopped. | 160th of 371, with limits $35 a month | No published price | 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 Fly nor Deno ships a desktop: on both you install and stream one yourself, and Deno caps it at 2 vCPU and 4 GB. boat has a 60fps desktop with Chrome in every machine. | 140th of 367, with limits $173 a month | No published price | 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 | 229th of 356, with limits $90 a month | No published price | 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 | 233rd of 343, with limits $67 a month | No published price | 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 Fly has a ranked price here and Deno has none: scrapers on Fly can spread across 17 regions with no 30-minute stop. | 47th of 327, with limits $1,232 a month | No published price | 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 | 168th of 351, with limits $63 a month | No published price | 3rd 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 requirement | No published price | 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 | No published price | Not ranked: misses a requirement |
Key features
| Feature | Fly.io Machines | Deno Sandbox | boat |
|---|---|---|---|
| Kind of product | App hosting platform; you boot your own image as a microVM | Sandbox for short runs of untrusted or AI-written code, from Deno; closed to new customers since November 2026 | Agent sandbox: a full VM per agent, ready to use; self-serve plans from $20 a month |
| Isolation | Firecracker microVM with its own kernel | Firecracker microVM with its own kernel | Full VM with its own kernel, on physical hosts dedicated to boat (AMD Ryzen 7 9700X and Ryzen 9 9950X); vCPUs are shared |
| Machine size | Shared or performance CPU presets you choose | 2 vCPU (no CPU option documented), 768 MB to 4 GB memory, 10 GB disk | 2 to 16 vCPU and 4 to 32 GB, with 51 to 251 GB of disk; 16 vCPU needs the $100 plan or higher |
| Session length | No documented cap; a Machine runs until you or autostop stop it | Up to 30 minutes; for longer work, start a new sandbox or promote it to a Deno Deploy app | Auto-stop defaults to 1 hour; set up to 30 days, or turn it off on a paid plan for no cap |
| Files after a stop | Root file system resets by default; opt-in persist_rootfs keeps it, but Fly staff say not to trust it with critical data. One Volume of up to 500GB per Machine, billed for its full size all month | Default root disk is wiped at the end; a bootable volume (300 MB to 20 GB, Chicago only) can be the root file system and keeps its files | The disk is saved every minute and at each stop and kept at least 14 days; memory and /tmp are not saved |
| Pause, snapshots and fork | Suspend keeps memory for Machines up to 2GB; a clone copies config, and its Volume starts empty unless you restore a volume snapshot or fork the Volume | On-demand read-only volume snapshots that many new sandboxes can boot from (Chicago only); no pause | Automatic disk snapshots and fork of a running sandbox from its last 1-minute snapshot; resume reboots from disk |
| Docker, systemd and nested virtualization | Root and Docker you install yourself; Fly's own init by default (systemd as PID 1 is not a documented setup); /dev/kvm not documented | Root access; Docker and nested virtualization not documented | Docker, root, systemd and /dev/kvm on every machine |
| CPU | Shared vCPUs guarantee 6.25% of a core plus bursts; performance vCPUs get the full core at a higher rate | 2 vCPU; CPU billed only while code is running | Shared vCPUs with no baseline quota or burst balance; billed per second while the sandbox runs, busy or idle |
| Start time | Fast-starting microVMs; Fly Proxy can wake a stopped Machine on a request | Under 200 ms, as stated by Deno | Boots a full VM; not in the public start-time benchmarks we use |
| Desktop and coding agents | Not built in; you add a desktop, browser and agents to your own image. Fly's separate Sprites product ships coding agents | No desktop documented; a root image with Claude Code run through shell commands, a VS Code editor in the browser and SSH | 60fps desktop with Chrome and computer-use tools; seven coding-agent harnesses installed, with a prompt, steer and events API |
| Keeping keys out of the sandbox | Secrets arrive as environment variables; you can deploy Fly's open-source tokenizer proxy yourself | Any secret swapped in on outbound HTTPS requests to approved hosts; the sandbox only sees a placeholder | Optional AI credentials proxy ($1 a day while on, plus $1 per 1,000 requests) for supported model providers; other secrets still enter |
| Outbound rules | Network policies allow chosen ports and protocols and deny the rest | Host allowlist per sandbox, enforced outside your code | Open internet on every plan; no provider-side allowlist |
| Reaching the sandbox | Public HTTPS and TCP through Fly Proxy, Anycast IPs, custom domains, SSH, private network | HTTPS URL per exposed port, public without authentication; SSH | Up to 50 HTTPS URLs, token-gated by default; SSH; public IPv6 and outbound IPv4; no dedicated IPv4 |
| Regions | 17 regions on six continents | Amsterdam or Chicago; volumes and snapshots only in Chicago | Germany, Finland and France; no US or Asia region, and you cannot pick one |
Every feature Battleships tracks (43)
| Feature | Fly.io Machines | Deno Sandbox | boat |
|---|---|---|---|
| Full VM (own kernel) | Yes | Yes | Yes |
| Docker inside | Yes | Not published | Yes |
| Nested virtualization | Not published | No documented way | Yes |
| Root | Yes | Yes | Yes |
| Systemd | Not published | Not published | Yes |
| Desktop GUI | No documented way | No documented way | Yes |
| Browser | No documented way | No documented way | Yes |
| Computer-use API | No documented way | No documented way | Yes |
| SSH | Yes | Yes | Yes |
| Persistent disk | Yes | Yes | Yes |
| Pause/resume | Yes | No documented way | Yes |
| Automatic snapshots | Yes | No documented way | Yes |
| Fork/clone | Yes | No documented way | Yes |
| Live fork (no pause) | Yes | 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 | No documented way | Yes |
| Idle auto-stop | Yes | No documented way | No documented way |
| Wake on request | Yes | No documented way | No documented way |
| HTTPS preview URLs | Yes | Yes | Yes |
| Raw TCP inbound | Yes | No documented way | Yes |
| Public IPv4 | Yes | No documented way | No documented way |
| Egress allowlist | Yes | Yes | No documented way |
| Secret proxy | No documented way | Yes | Yes |
| Secret proxy for any API | No documented way | Yes | Yes |
| Preinstalled agents | No documented way | Yes | Yes |
| Agent harness API | No documented way | No documented way | Yes |
| MCP server | Yes | No documented way | No documented way |
| GPU | No documented way | No documented way | No documented way |
| Windows | No documented way | No documented way | No documented way |
| Arm64 | No documented way | 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 | Yes | No documented way | No documented way |
| Scoped API keys | Not published | Not published | Yes |
| Spend limits | No documented way | Yes | Yes |
| Usage per sandbox (API) | No documented way | No documented way | Yes |
| Audit logs | Not published | Not published | No documented way |
| SSO | No documented way | No documented way | No documented way |
| SOC 2 | Yes | Not published | No documented way |
| HIPAA | Yes | Not published | No documented way |
| EU data residency | Yes | Yes | No documented way |
| Zero data retention | Not published | Not published | Yes |
Performance
Neither Fly.io Machines nor Deno Sandbox is 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. On Fly the result depends on the CPU class, and Deno's fixed 2 vCPU shape could not run the 4 vCPU test as set up.
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. Fly.io Machines and Deno Sandbox 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 | Fly.io Machines, a month | Deno Sandbox, 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 | $15 · Pay As You Go · with limits | No published price | $20 · $20/mo |
| One agent that never stops 4 vCPU / 8 GB, 50 GB disk, running 24/7 all month | $36 · Pay As You Go · with limits | No published price | $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 | $487 · Pay As You Go · with limits | No published price | $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 | $110 · Pay As You Go · with limits | No published price | $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 | $232 · Pay As You Go · with limits | No published price | $8,800 · $2000/mo · with limits |
Fly.io Machines: Fly bills each Machine per second while it runs, by CPU preset and memory, with no plan fee. Stopped Machines pay for their root file system, and Volumes bill for their full size all month at $0.15 per GB. The figures here use shared vCPUs bought in 1-year reservation blocks for 40% off, the lowest rate Fly sells.
Deno Sandbox: Deno Sandbox is no longer part of Deno Deploy plans and is not available to new customers (November 2026). Deno publishes no current sandbox rates, so this page shows no Deno price. The launch post listed $0.05 per hour of CPU time and $0.016 per GB-hour of memory.
Deno Sandbox: Plans cost $20, $100, $500 or $2,000 a month. The whole plan price comes back as VM time for that month, and unused time does not carry over. A default 4 vCPU / 8 GB sandbox costs $0.036 an hour, billed per second while it runs. A stopped sandbox has no compute charge; extra saved snapshots and the optional AI credentials proxy still charge. The $20 plan includes 200 starts a day; extra starts cost $0.03 to $0.07 each.
Limits in those scenarios
Deno Sandbox is closed to new customers, so it has no price in our scenarios. For existing organizations a sandbox lives up to 30 minutes on 2 vCPU with up to 4 GB of memory, and 5 run at once by default. Fly fits none of the five scenarios as written: its low figures need a 1-year reservation and shared vCPUs that guarantee only 6.25% of each core, and its API starts about one Machine per second per app. boat fits four of the five. At 1,000 short jobs at once the $2,000 plan charges for starts above 90 a minute and refuses them above 270.
| Scenario | Fly.io Machines | Deno Sandbox | boat |
|---|---|---|---|
| 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 |
|
|
|
Which one should you use?
Use Fly.io Machines when
you want long-running microVMs from your own image, near users in many regions, and you want to build the sandbox yourself.
- No 30-minute stop. For work that runs for hours or all month: a Fly Machine has no documented time cap and keeps running until you stop it.
- 17 regions worldwide. For users spread across the world: Fly runs Machines in 17 regions, from the US to Sydney and Johannesburg.
- Open to new customers, with wake on request. Anyone can sign up for Fly, and Fly Proxy wakes Machines on traffic, with custom domains and a private network around them.
Use Deno Sandbox when
Use Deno Sandbox if your organization already has it and you run short pieces of untrusted code that must start in milliseconds and reach only the hosts you allow. New customers cannot sign up since November 2026.
- Starts in under 200 ms. For one sandbox per request: Deno says a sandbox starts in under 200 ms, and CPU bills only while code runs.
- Locked-down outbound traffic and secrets. For untrusted code: each sandbox can reach only hosts you list, and real secrets are swapped in outside the VM.
- A path to Deno Deploy. For existing Deno Deploy teams: a sandbox can be promoted to a Deploy app. New customers cannot sign up since November 2026.
Where boat fits
If you run coding or computer-use agents that work for hours, both products leave a gap. Deno stops at 30 minutes on 2 vCPU and is closed to new customers, and on Fly you build the sandbox image yourself. boat gives each agent a full VM with Docker, a desktop and coding agents installed, and a disk saved every minute.
A disk saved with no setup
On Deno the default root disk is wiped at the end, and a bootable volume in Chicago keeps files. On Fly lasting files go on a Volume billed for its full size all month, or on the root file system with opt-in persist_rootfs. boat saves the disk every minute and at each stop. It does not save memory, and a machine failure loses writes after the last good snapshot.
Docker, systemd and /dev/kvm ready
Deno does not document Docker. On Fly you install Docker yourself, and Fly does not document systemd as PID 1 or /dev/kvm. boat has Docker, systemd and /dev/kvm on every machine, for Android emulators and nested VMs.
A desktop and agents you drive from outside
Neither ships a desktop, so for computer use you install and stream one yourself. On Fly you also package agents into your image, and on Deno you run Claude Code through shell commands. boat has a 60fps desktop and a prompt, steer and events API.
Use boat when your agents do real work for hours: installs, builds, Docker, emulators and a browser on a full VM whose disk is saved every minute and at each stop, with coding agents installed. Compare it one to one: boat vs Fly.io Machines and boat vs Deno Sandbox.
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 Fly.io Machines cheaper than Deno Sandbox?
We cannot compare prices. Deno Sandbox is closed to new customers and publishes no current rates. On Fly's lowest rate, one agent running all month is $36 and 50 agents in parallel are $487; on boat they are $26 and $317. Fly's figures assume a 1-year reservation and shared vCPUs.
Which is faster, Fly.io Machines or Deno Sandbox?
Neither is in the public benchmarks we use. Deno says a sandbox starts in under 200 ms. On Fly, speed depends on the CPU class: shared vCPUs guarantee 6.25% of a core with bursts, and performance vCPUs get the full core at a higher rate.
How long can each one run?
A Deno sandbox lives up to 30 minutes, and longer work can be promoted to a Deno Deploy app. A Fly Machine has no documented time cap and runs until you or autostop stop it. On boat, auto-stop defaults to 1 hour; you can set up to 30 days or turn it off on a paid plan.
Can Fly.io Machines or Deno Sandbox run Docker?
On Fly you can install and run Docker yourself, since a Machine is a microVM with root. Deno's docs do not say Docker works inside a sandbox. Neither documents /dev/kvm for nested VMs. boat has Docker, systemd and /dev/kvm on every machine.
Do they keep files after a stop?
On Fly, files on the Machine's Volume last, and the root file system lasts too with opt-in persist_rootfs, which Fly staff say not to trust with critical data. On Deno, a bootable volume in Chicago keeps its files; the default root disk is wiped. boat saves the disk every minute and at each stop and keeps it at least 14 days.
Is boat SOC 2 compliant?
SOC 2 is in progress. We're open about where we stand: live status at status.ascii.dev and our data retention policy at docs.boat.dev/data-retention.
Try boat
Install the CLI, then run boat new.
7-day free trial
More comparisons
- boat vs Fly.io Machines
- boat vs Deno Sandbox
- E2B vs Fly.io Machines
- Daytona vs Fly.io Machines
- Modal vs Fly.io Machines
- Vercel Sandbox vs Fly.io Machines
- Cloudflare Sandbox vs Fly.io Machines
- Blaxel vs Fly.io Machines
- Runloop vs Fly.io Machines
- Tensorlake vs Fly.io Machines
- Morph Cloud vs Fly.io Machines
- CodeSandbox SDK vs Fly.io Machines