Fly.io Machines vs Freestyle
Fly.io Machines are Firecracker microVMs for hosting your own apps in 17 regions, and you build any sandbox on top yourself. Freestyle sells full KVM VMs made for agents, with systemd, Docker, nested virtualization and coding agent CLIs ready, plus memory pause, live fork and wake on request.
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.
Freestyle
Freestyle sells full Linux virtual machines for AI agents, built for long running, complex tasks.
Each Freestyle VM is a KVM virtual machine with its own kernel, booted from a base snapshot. The default Ubuntu image has systemd, Docker and coding agent CLIs preinstalled. VMs can be paused with their memory, snapshotted while running, forked and woken by the next request. Every VM starts behind a default-deny firewall. You drive it from a TypeScript SDK, a CLI or an API.
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 | Freestyle: price rank | boat: price rank |
|---|---|---|---|
| Software factory 100 at once · 4 vCPU / 8 GB · 2,200 sessions of 8 h a month Freestyle has systemd, Docker and /dev/kvm ready; on Fly you install Docker yourself and keep files on a Volume. boat also has all three, and did 28.06 against Freestyle's 10.22 runs/s in StarSling's run of 3 October 2026. | 123rd of 365, with limits $836 a month | 31st cheapest of 365 $3,311 a month | 5th cheapest of 365 $634 a month |
| Always-on AI employees 50 machines 24/7 · 2 vCPU / 4 GB | 186th of 361, with limits $816 a month | 49th cheapest of 361 $4,195 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 Freestyle ranks well ahead of Fly here: its VMs pause with memory and wake on the next request. | 83rd of 336, with limits $94 a month | 46th cheapest of 336 $482 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 Freestyle fits fully and wakes a paused user VM on its next request. Fly creates about one Machine per second per app. boat fits too, with start limits per plan. | 75th of 349, with limits $600 a month | 26th cheapest of 349 $1,358 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 Fly ranks well above Freestyle here on price. Freestyle can snapshot a running VM with its memory and boot copies, which suits rollouts that branch. | 52nd of 349, with limits $2,838 a month | 116th of 349, with limits $6,600 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 | 124th of 359, with limits $457 a month | 68th cheapest of 359 $1,046 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 Busy CI jobs drain a shared Fly vCPU's burst balance, and Freestyle's docs send sustained heavy CPU work to other providers. boat ranks near the top here. | 154th of 374, with limits $288 a month | 169th of 374, with limits $625 a month | 2nd cheapest of 374 $86 a month |
| 24/7 dev boxes 1 machine 24/7 · 4 vCPU / 8 GB Freestyle fits a 24/7 dev box with its whole disk kept; a paused VM bills only storage. Fly keeps files on its Volume, or on the root file system with opt-in persist_rootfs. | 160th of 371, with limits $35 a month | 102nd cheapest of 371 $151 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 Fly you build it into your image, and on Freestyle you follow official guides to install GNOME or headed Chromium with noVNC. boat streams one at 60fps. | 140th of 367, with limits $173 a month | 51st cheapest of 367 $940 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 | 229th of 356, with limits $90 a month | 99th of 356, with limits $482 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 | 233rd of 343, with limits $67 a month | 110th cheapest of 343 $482 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 Fly ranks highest of the three here: it can spread scrapers across 17 regions and bill only the seconds they run. | 47th of 327, with limits $1,232 a month | 183rd of 327, with limits $6,560 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 | 168th of 351, with limits $63 a month | 28th cheapest of 351 $482 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 | Not ranked: misses a requirement | Not ranked: misses a requirement | 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 | Not ranked: misses a requirement | Not ranked: misses a requirement |
Key features
| Feature | Fly.io Machines | Freestyle | boat |
|---|---|---|---|
| Kind of product | App hosting platform; Machines are its VM building block with a REST API | Full Linux VMs sold for AI agents | Agent sandbox: a full VM per agent, ready to use |
| Isolation | Firecracker microVM with its own kernel | Full KVM VM with its own kernel on bare metal; Freestyle says it oversubscribes host resources | Full VM with its own kernel, on physical hosts dedicated to boat (AMD Ryzen 7 9700X and Ryzen 9 9950X); vCPUs are shared |
| 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 | systemd is pid 1, Docker runs from boot, full KVM support | Docker, root, systemd and /dev/kvm on every machine |
| CPU benchmark (V8 Web Tooling, 4 vCPU / 8 GB, StarSling run of 3 October 2026) | Not in the run; shared vCPUs guarantee 6.25% of a core, performance vCPUs get the full core | 10.22 runs/s, 14th of 15 | 28.06 runs/s, 2nd of 15 (rank shared), on a Ryzen 9 9950X host |
| 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. Lasting data goes on one Volume, billed for its full size | Whole disk kept; a paused VM bills only storage, after 60,000 free GiB-hours a month | The disk is saved every minute and at each stop, kept at least 14 days, with no compute charge while stopped; memory is not saved |
| Pause with memory | Suspend keeps memory for Machines up to 2GB; dropped on deploy or host move | Pause saves memory and disk; the same processes resume | Resume boots again from disk (no memory snapshots) |
| Fork | Clone copies a Machine's config; its Volume starts empty unless you restore a volume snapshot or fork the Volume | Clone a running VM without pausing it; snapshots capture memory and disk | Fork a running sandbox from its last 1-minute disk snapshot |
| Wake on request | Fly Proxy stops or suspends idle Machines and wakes them on traffic | A VM paused by idle timeout resumes on the next traffic | No; you start a stopped sandbox through the API; auto-stop is a timer (1 hour by default), not an idle check |
| Coding agents | Not built in on Machines; you install agents in your image. Fly's separate Sprites product ships coding agents | claude, codex, opencode and openclaw preinstalled, driven through exec or a terminal | Seven harnesses installed, with a prompt, steer and events API to drive them from outside |
| Desktop, browser and computer use | Not built in; you set it up: add a desktop, a browser and a VNC stream to your own image | You set it up: official guides install GNOME with TigerVNC and noVNC, or headed Chromium driven with Playwright or CDP | Linux desktop and Chrome streamed at 1920x1080 and 60fps, with computer-use tools, embeddable stream |
| Keeping keys out of the sandbox | Secrets arrive as environment variables; you can deploy Fly's open-source tokenizer proxy yourself | Credentials injected at the edge for HTTPS headers, Postgres and S3; the VM must trust the Freestyle CA | Optional AI credentials proxy ($1 a day while on, plus $1 per 1,000 requests); other secrets still enter the sandbox |
| Outbound rules | Network policies allow chosen ports and protocols and deny the rest | Default-deny firewall with allow rules by IP, VM, VPC or exact domain | Open internet on every plan; no provider-side allowlist |
| Biggest machine | Pick a shared or performance CPU preset, up to 16 vCPU | Up to 32 vCPU / 64 GiB on Pro, 64 / 128 with Enterprise custom limits | Up to 16 vCPU / 32 GB on the $100 plan and above |
| Regions | 17 regions on six continents | Not published | Germany, Finland and France; no US or Asia region, and you cannot pick one |
Every feature Battleships tracks (43)
| Feature | Fly.io Machines | Freestyle | boat |
|---|---|---|---|
| Full VM (own kernel) | Yes | Yes | Yes |
| Docker inside | Yes | Yes | Yes |
| Nested virtualization | Not published | Yes | Yes |
| Root | Yes | Yes | Yes |
| Systemd | Not published | Yes | Yes |
| Desktop GUI | No documented way | With your own setup | Yes |
| Browser | No documented way | With your own setup | Yes |
| Computer-use API | No documented way | With your own setup | Yes |
| SSH | Yes | Yes | Yes |
| Persistent disk | Yes | Yes | Yes |
| Pause/resume | Yes | Yes | Yes |
| Automatic snapshots | Yes | Yes | Yes |
| Fork/clone | Yes | Yes | Yes |
| Live fork (no pause) | Yes | Yes | Yes |
| Memory fork | No documented way | Yes | No documented way |
| Custom image (Docker or snapshot) | Yes | Yes | Yes |
| ≥24 h sessions | Yes | Yes | Yes |
| Idle auto-stop | Yes | Yes | No documented way |
| Wake on request | Yes | Yes | No documented way |
| HTTPS preview URLs | Yes | Yes | Yes |
| Raw TCP inbound | Yes | Yes | 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 | Yes | 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 | Yes | Yes |
| Spend limits | No documented way | Not published | Yes |
| Usage per sandbox (API) | No documented way | No documented way | Yes |
| Audit logs | Not published | Yes | No documented way |
| SSO | No documented way | Yes | No documented way |
| SOC 2 | Yes | Not published | No documented way |
| HIPAA | Yes | Not published | No documented way |
| EU data residency | Yes | Not published | No documented way |
| Zero data retention | Not published | Not published | Yes |
Performance
In StarSling's run of 3 October 2026 (run 37073680030), on the V8 Web Tooling Benchmark at 4 vCPU / 8 GB, boat did 28.06 runs per second (2nd of 15, rank shared) and Freestyle did 10.22 (14th of 15), about 2.7 times the CPU work. 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. Providers ran on different hardware in different regions. Fly.io Machines are not in the run, and their speed depends on whether you pick shared vCPUs, which guarantee 6.25% of a core, or performance vCPUs.
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 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 | Fly.io Machines, a month | Freestyle, 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 | $27 · Free | $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 | $159 · Free | $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 | $2,139 · Pro | $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 | $581 · Pro | $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 | $1,305 · Pro · with limits | $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 Fly's lowest rate: shared vCPUs bought in 1-year reservation blocks for 40% off.
Freestyle: Freestyle bills per second for the vCPU, RAM and disk allocated to a VM, busy or idle, after monthly allowances of 200 vCPU-hours, 400 GiB-hours of RAM and 60,000 GiB-hours of storage. Free stops when the allowances run out and needs no card; Hobby and Pro have a $50 or $500 monthly minimum that counts as usage. A paused VM bills only for storage.
Freestyle: 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
Fly is marked a compromise in every scenario because its lowest figures need a 1-year reservation and use shared vCPUs that throttle above 6.25% of each core. Freestyle fits the first four scenarios, but 50 agents need Pro, and Pro's cap of 400 concurrent VMs is why it does not fit 1,000 short jobs at once. Freestyle has no idle timeout by default, so a VM bills until you pause it or set one. boat does not fit that burst either: the $2,000 plan includes 90 starts a minute, charges for extra starts, and refuses them above 270 a minute.
| Scenario | Fly.io Machines | Freestyle | boat |
|---|---|---|---|
| One coding agent, workdays |
| None for this scenario | None for this scenario |
| One agent that never stops |
| None for this scenario | None for this scenario |
| 50 agents in parallel |
| None for this scenario | None for this scenario |
| Sandboxes for your users |
| None for this scenario | None for this scenario |
| 1,000 short jobs at once |
|
|
|
Which one should you use?
Use Fly.io Machines when
you host apps or light services that must run near users on several continents, sleep between requests and wake on traffic.
- 17 regions worldwide. Useful when agents or users sit far apart: Fly runs Machines in 17 regions, from the US to Sydney and Johannesburg.
- A full app platform around each Machine. Useful if you also host the product: private networking, Anycast IPs, custom domains and port-level network policies come built in.
- No monthly minimum. Useful for light or bursty work: Fly bills each Machine per second while it runs, with no plan fee.
Use Freestyle when
you want a ready agent VM that pauses with its memory, forks while running, starts behind a default-deny firewall, needs more than 16 vCPU, or starts on a free plan.
- Built as an agent VM. Useful if you want a ready machine: systemd, Docker, nested virtualization and four coding agent CLIs come in the base image.
- Memory pause and live fork. Useful for VMs that sleep and branch: pause keeps the running processes, and you can clone a VM while it runs.
- Default-deny network, big machines and a free plan. Useful for locked-down or heavy jobs: each VM starts with no network access, Pro VMs go up to 32 vCPU, and the Free plan needs no card.
Where boat fits
If you run coding agents that work for hours, look at boat too. On Fly you build the sandbox yourself, and Freestyle gives you the VM but you set up the desktop and drive the agents through exec. boat ships both, and it did more CPU work than Freestyle in StarSling's run of 3 October 2026.
More CPU work in the same run
On the V8 Web Tooling Benchmark at 4 vCPU / 8 GB, in StarSling's run of 3 October 2026, boat did 28.06 runs per second and Freestyle 10.22. That boat sandbox ran on a Ryzen 9 9950X host; boat also places sandboxes on other hosts. Fly was not in the run, and its shared vCPUs throttle once a long build drains the burst balance.
A disk saved every minute
On Fly, lasting files go on one Volume billed for its full size, or on the root file system with opt-in persist_rootfs. Freestyle keeps the whole disk and bills a paused VM only for storage. boat saves the disk every minute and at each stop, with no compute charge while stopped. It does not save memory, and a machine failure loses writes after the last good snapshot.
Desktop and agents you drive from outside
Neither ships a desktop: on Fly you build it into your image, and on Freestyle you install GNOME or headed Chromium with noVNC from its guides. boat streams a 60fps desktop with computer-use tools, and an API prompts and steers the agents inside.
Use boat when your agents do real work for hours: builds, tests, Docker and emulators on a full VM with a desktop, a disk saved every minute and an API to drive the agents inside from outside. Compare it one to one: boat vs Fly.io Machines and boat vs Freestyle.
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 Freestyle?
On Fly's lowest rate, yes. One agent running all month is $36 on Fly and $159 on Freestyle, and 50 agents in parallel are $487 against $2,139. Fly's figures use shared vCPUs on a 1-year reservation, which throttle above 6.25% of a core. boat is $26 and $317 for the same two. A Freestyle VM that pauses while idle bills only storage, so a mostly idle VM costs less there.
Which is faster, Fly.io Machines or Freestyle?
Fly is not in the public benchmarks we use, so we cannot compare it. Freestyle did 10.22 runs per second on the V8 Web Tooling Benchmark at 4 vCPU / 8 GB in StarSling's run of 3 October 2026. boat did 28.06 in the same run, on a Ryzen 9 9950X host.
Can Fly.io Machines and Freestyle run Docker?
Both can. On Fly you install Docker yourself in your image; Fly does not document systemd as PID 1 or /dev/kvm, so nested VMs and Android emulators are not a documented path. Freestyle runs Docker from boot with systemd and full KVM support, like boat.
Do they keep my files when a VM stops?
Freestyle keeps the whole disk and bills a paused VM only for storage. A Fly Machine keeps files on its Volume, and on the root file system too with opt-in persist_rootfs, which Fly staff say not to trust with critical data. boat saves the disk every minute and at each stop and keeps it at least 14 days.
Can either one pause with memory?
Both can. Fly suspends Machines up to 2GB of memory and drops the snapshot on deploy or host move. Freestyle pauses a VM with its memory and disk and can clone it while it runs. boat keeps the disk but boots again on resume.
Where do they run?
Fly runs Machines in 17 regions on six continents. Freestyle does not publish its regions. boat runs on machines in Germany, Finland and France, and you cannot pick a region.
Try boat
Install the CLI, then run boat new.
7-day free trial
More comparisons
- boat vs Fly.io Machines
- boat vs Freestyle
- 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