Fly.io Machines vs Azure Container Apps Sandboxes
Fly.io Machines are the microVMs under an app hosting platform: you boot your own image and keep data on one Volume. Azure Container Apps Sandboxes are built for agent code inside an Azure account, with sandboxes from your own OCI image that suspend with their memory and wake on traffic.
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.
Azure Container Apps Sandboxes
Azure Container Apps Sandboxes is a service inside Microsoft Azure that gives each agent or user an isolated microVM you create, suspend and resume through an SDK.
It is part of Azure Container Apps, the hyperscaler's serverless container platform, and lives in your Azure subscription as a sandbox group resource. Each sandbox boots from an OCI image or a snapshot and has its own kernel. A stop keeps the disk, or the disk and the memory, and a memory-mode sandbox resumes in under a second. It is built for teams already on Azure that want stateful code execution with Azure networking, identity and billing.
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 | Azure Container Apps Sandboxes: price rank | boat: price rank |
|---|---|---|---|
| Software factory 100 at once · 4 vCPU / 8 GB · 2,200 sessions of 8 h a month Azure fits with an image that has Docker, such as azure-dev; nested virtualization is not documented. On Fly you install Docker and a desktop in your image and keep files on a Volume. boat ships Docker, /dev/kvm and a desktop on every machine. | 123rd of 365, with limits $836 a month | 33rd cheapest of 365 $5,276 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 | 52nd cheapest of 361 $6,780 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 Azure fits short code runs well: sandboxes suspend with their memory and resume in under a second. Fly can do it on cheap shared CPU, but you build the sandbox image yourself. | 83rd of 336, with limits $94 a month | 39th cheapest of 336 $354 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 Azure fits one sandbox per user, but 300 active cores per region is the default quota. Fly's API creates about one Machine per second per app, so sign-up waves need pre-created Machines. | 75th of 349, with limits $600 a month | 32nd cheapest of 349 $2,260 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 | 52nd of 349, with limits $2,838 a month | 158th of 349, with limits $10,740 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 | 85th cheapest of 359 $1,728 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 CI keeps the CPU busy, which drains a shared Fly vCPU's burst balance; performance CPU avoids it at a higher rate. Azure fits. boat adds /dev/kvm for Android and VM builds. | 154th of 374, with limits $288 a month | 108th cheapest of 374 $1,046 a month | 2nd cheapest of 374 $86 a month |
| 24/7 dev boxes 1 machine 24/7 · 4 vCPU / 8 GB A dev box wants SSH and a disk that lasts. Azure gives a shell through its aca CLI, SDK and portal. Fly has SSH and keeps files on a Volume, or on the root file system with opt-in persist_rootfs. | 160th of 371, with limits $35 a month | 327th of 371, with limits $262 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 Fly nor Azure ships a desktop image; on both you build one into your own image and publish it on an HTTPS port. boat streams one at 60fps. | 140th of 367, with limits $173 a month | 58th cheapest of 367 $1,573 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 On Fly and Azure you package a browser into your own image. boat has Chrome and browser control ready in every machine. | 229th of 356, with limits $90 a month | 129th of 356, with limits $795 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 | 112th cheapest of 343 $561 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 well above Azure here: scrapers run on cheap shared CPU across 17 regions and pay only for the seconds they run. | 47th of 327, with limits $1,232 a month | 240th of 327, with limits $10,956 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 | 30th cheapest of 351 $517 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 | Azure Container Apps Sandboxes | boat |
|---|---|---|---|
| Kind of product | App hosting platform; you boot your own image as a microVM through a REST API | A sandbox compute type inside Azure Container Apps, driven through an SDK, CLI or portal | Agent sandbox: a full VM per agent, ready to use |
| Isolation | Firecracker microVM with its own kernel | MicroVM per sandbox 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 |
| Docker and systemd | Root and Docker you install yourself; Fly's own init by default (systemd as PID 1 is not a documented setup) | Depends on the image: azure-dev ships Docker on systemd and the copilot image runs systemd; the default ubuntu image has only Buildah | Docker with BuildKit and Compose, systemd and root on every machine |
| Nested virtualization | /dev/kvm not documented | Not documented | Yes, /dev/kvm for Android emulators and VMs |
| Custom image | Your own Docker image | Any OCI image from a public or private registry, imported as a disk image | Start from boat's Ubuntu 24.04 image or a saved snapshot; you cannot boot your own Docker image |
| 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 (daily snapshots), billed for its full size around the clock | A stop keeps the disk, or the disk and the memory; stopped sandboxes pay no CPU or memory; storage billing is announced as coming | The disk is saved every minute and at each stop, with no compute charge while stopped, and kept at least 14 days; memory and /tmp are not saved |
| Sleep and wake | Fly Proxy stops or suspends idle Machines and wakes them on a request; memory kept only up to 2GB | Auto-suspend with memory after an idle timeout (default 5 minutes); traffic or a start command resumes it in under a second | Auto-stop timer (default 1 hour, up to 30 days, or off on paid plans) that does not watch for idle; start by API, which boots from disk |
| Fork | Clone copies a Machine's config; its Volume starts empty unless you restore a volume snapshot or fork the Volume | Snapshot a running sandbox with its memory and create new sandboxes from it | Fork a running sandbox from its last 1-minute disk snapshot |
| Reaching the sandbox | Public HTTPS and TCP through Fly Proxy, Anycast IPs, custom domains, SSH, private network | Public HTTPS routes per published port; private endpoint from your VNet at extra cost; no SSH and no public IP | SSH, up to 50 HTTPS URLs token-gated by default, public IPv6 and outbound IPv4; no dedicated IPv4 |
| Desktop and computer use | Not built in; you set it up: add a desktop, a browser and a VNC stream to your own image | No desktop or browser in the public images; you can build one into your own OCI image and publish it on an HTTPS port | Linux desktop and Chrome streamed at 1920x1080, 60fps, with computer-use tools |
| Coding agents | Not built in on Machines; you install agents in your image. Fly's separate Sprites product ships coding agents | Copilot CLI and Claude Code images, run through the exec API | Seven 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 | An egress Transform rule adds a group secret or managed-identity token as a header outside the sandbox, one rule per API host; the built-in Copilot and Claude connections put tokens inside | Optional AI credentials proxy ($1 per day while on, plus $1 per 1,000 requests); with it on, real keys of supported providers stay outside; other secrets still enter |
| Outbound rules | Network policies allow chosen ports and protocols and deny the rest | Egress policy with allow, deny, rewrite and header rules by host, path and method; VNet integration | Open internet; no provider-side allowlist |
| CPU and sizes | Shared vCPUs guarantee 6.25% of a core plus bursts; performance vCPUs get the full core at a higher rate | Seven tiers from 0.25 cores / 0.5 GiB to 16 cores / 32 GiB; 300 active cores per region by default | Shared vCPUs with no baseline quota or burst balance; up to 16 vCPU / 32 GB on the $100 plan and above |
| Regions | 17 regions on six continents | 40 Azure regions, 9 of them in the EU | Germany, Finland and France; no US or Asia region, and you cannot pick one |
Every feature Battleships tracks (43)
| Feature | Fly.io Machines | Azure Container Apps Sandboxes | boat |
|---|---|---|---|
| Full VM (own kernel) | Yes | Yes | Yes |
| Docker inside | Yes | Yes | Yes |
| Nested virtualization | Not published | Not published | 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 | No documented way | Yes |
| SSH | Yes | No documented way | 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 | 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 | Yes | Yes |
| Audit logs | Not published | Yes | No documented way |
| SSO | No documented way | Yes | No documented way |
| SOC 2 | Yes | Yes | No documented way |
| HIPAA | Yes | Yes | 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 Azure Container Apps Sandboxes 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, since shared vCPUs guarantee only 6.25% of a core.
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 Azure Container Apps Sandboxes 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 | Azure Container Apps Sandboxes, 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 | $68 · Pay-as-you-go | $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 | $262 · Pay-as-you-go · with limits | $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 | $3,421 · Pay-as-you-go | $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 | $989 · Pay-as-you-go | $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 | $2,148 · Pay-as-you-go | $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 are billed 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.
Azure Container Apps Sandboxes: Azure bills per second on the Container Apps Consumption meters for the tier's vCPU and memory while a sandbox runs, idle time before auto-suspend included. The XL tier (4 cores / 8 GiB) is $0.432 an hour at East US rates. Stopped sandboxes pay no CPU or memory, and there is no plan fee. Storage billing per GiB is announced as coming soon.
Azure Container Apps Sandboxes: 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 all five scenarios: its lowest figures need a 1-year reservation and use shared vCPUs that guarantee only 6.25% of each core, so long builds get throttled. Azure fits four of the five. Its always-on price of $262 a month needs a 3-year savings plan, and Azure does not state that the plan covers Sandboxes. Azure's default quota is 300 active cores per region and subscription, so 300 user sandboxes or 1,000 short jobs need a support request first. boat does not fit the 1,000-job burst: the $2,000 plan charges for starts above 90 a minute and refuses them above 270. boat's other limits: auto-stop defaults to 1 hour, and a resume is like a reboot.
| Scenario | Fly.io Machines | Azure Container Apps Sandboxes | boat |
|---|---|---|---|
| One coding agent, workdays |
| None for this scenario | None for this scenario |
| One agent that never stops |
|
| 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 |
| None for this scenario |
|
Which one should you use?
Use Fly.io Machines when
you host web apps or light services worldwide that sleep between requests, and you want to build the sandbox image yourself.
- A full app platform around each Machine. Useful if you host a whole product: Fly adds public TCP, SSH, Anycast IPs, custom domains and private networking next to your sandboxes.
- Cheap shared CPU for light work. Useful for agents that mostly wait on the network: shared vCPUs bill per second with no plan fee.
- No cloud account to set up. Useful for small teams outside Azure: a card or prepaid credits is enough, after a 7-day free trial with $1 of credit.
Use Azure Container Apps Sandboxes when
your team runs on Azure and wants sandboxes from its own OCI images that suspend with their memory, wake on traffic and sit behind strict egress rules.
- Memory suspend and wake on traffic. Good for stateful jobs that sleep between requests: a sandbox suspends with its memory and resumes in under a second.
- Fine-grained outbound rules. Useful when agents must reach only chosen hosts: rules can allow, deny or rewrite each request by host, path and method.
- Your own image, inside Azure, in 40 regions. Teams already on Azure get Entra ID, Azure billing, VNets and their own OCI images, in 40 regions on six continents.
Where boat fits
Fly hosts apps and Azure runs agent code from your own image, so on both you build the desktop and agent setup yourself. If your agents install tools, run Docker and emulators, use a browser or work for hours, boat gives every machine a full VM with a desktop, coding agents and a disk saved every minute.
A whole computer with /dev/kvm
Fly does not document systemd as PID 1 or /dev/kvm, and keeps lasting files on one Volume unless you turn on persist_rootfs. Azure documents no nested virtualization and no SSH. boat gives every machine root, systemd, Docker, /dev/kvm and SSH.
A desktop and coding agents installed
On Fly and Azure you build the desktop, browser and stream into your own image. Azure ships Copilot CLI and Claude Code images. boat ships a 60fps desktop with Chrome and seven coding-agent harnesses that you drive from outside through one API.
Keys outside the sandbox, without your own rules
Fly passes secrets as environment variables unless you run its tokenizer proxy yourself. Azure can add a secret as a header outside the sandbox with one egress rule per API host. boat's optional paid proxy ($1 a day while on, plus $1 per 1,000 requests) keeps real keys of supported AI providers outside; other secrets still enter.
Use boat when your agents do real work for hours on a full VM: SSH, Docker, emulators, a desktop and a browser, with coding agents installed and an optional credentials proxy. Compare it one to one: boat vs Fly.io Machines and boat vs Azure Container Apps Sandboxes.
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 Azure Container Apps Sandboxes?
On Fly's lowest rate, yes in every scenario here: one workday agent is $15 a month on Fly against $68 on Azure, and 50 agents in parallel are $487 against $3,421. Fly's figures need a 1-year reservation and shared vCPUs that throttle under sustained load. boat is $20 and $317 for the same two.
Which is faster, Fly.io Machines or Azure Container Apps Sandboxes?
Neither is in the public benchmarks we use, so we cannot say. On Fly, speed under long loads depends on picking performance vCPUs over shared ones.
Can Fly.io Machines or Azure sandboxes run Docker?
On Fly you install Docker yourself in your image; Fly does not document systemd as PID 1 or /dev/kvm. On Azure the azure-dev image ships Docker on systemd, while the default ubuntu image has only Buildah. boat has Docker, systemd and /dev/kvm on every machine.
Which one keeps memory when a sandbox sleeps?
Azure can suspend a sandbox with its memory and resume it in under a second. Fly keeps memory only for Machines up to 2GB, and drops it on a deploy or host move. boat saves the disk every minute and at each stop, and resumes by booting again.
Do I need an Azure account for Azure Container Apps Sandboxes?
Yes. It needs an Azure subscription, a Microsoft Entra ID account and the Container Apps SandboxGroup Data Owner role. Fly needs a card or prepaid credits after its 7-day trial. boat needs a card too, also for its 7-day trial.
Where do they run?
Fly runs Machines in 17 regions and Azure runs sandboxes in 40 regions, both across six continents. boat runs on machines in Germany, Finland and France, and you cannot pick a region. Snapshot copies can be stored outside the EU.
Try boat
Install the CLI, then run boat new.
7-day free trial
More comparisons
- boat vs Fly.io Machines
- boat vs Azure Container Apps Sandboxes
- 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