Fly.io is a global hardware-virtualized public cloud that runs your containers as Firecracker micro-VMs in 35+ regions, with instant-boot Fly Machines for apps and Sprites for AI agent sandboxes. We rate it 75/100 — the cleanest global deploy experience in the PaaS space and a natural home for real-time, edge-heavy, or agent-driven workloads, but the complex resource-based pricing, lack of billing alerts and the end of the original free tier mean it is no longer the cheap Heroku replacement it used to be.

What is Fly.io?

Fly.io is a public cloud built by Kurt Mackey, Thomas Ptacek and the team at Superfly, Inc., which has been around since December 2017 and pivoted to its current "hardware-virtualized containers" shape in 2020. You push a Dockerfile (or let fly launch generate one from a Rails, Django, Phoenix, Laravel or Next.js app) and Fly boots it as a Firecracker VM on bare-metal servers across 35+ regions — from Amsterdam and Ashburn to Sydney, Johannesburg and São Paulo — with sub-100ms latency for most of the world.

The pitch is specific. Vercel, Railway and Render are great at shipping a single-region web app; AWS and GCP hand you everything but ask you to become a platform engineer. Fly.io sits in the middle: real multi-region by default, persistent volumes and private networking at every POP, first-class Postgres and SQLite (LiteFS), and a CLI-first workflow that DevOps teams actually enjoy. flyctl, the open-source CLI, has 1,600+ stars on GitHub, and LiteFS, the replicated SQLite filesystem, has 4,700+. Notable customers include Supabase, Builder.io, Mercor, Cogram, Reflex and Imbue.

Fly.io flyctl CLI — the open-source command-line client for deploying Fly Machines — flyctl on GitHub: Fly.io's open-source command-line client (Apache-2.0), used to deploy, scale and manage apps and volumes across 35+ regions.

Key features of Fly.io

Fly Machines: Firecracker-based micro-VMs that cold-start in 300–800ms, suspend to memory snapshots when idle, and resume on the next request — you pay per second of wake time, not for an "always-on" container.
35+ global regions: machines boot in 35+ cities with Anycast routing that sends each user to the nearest running instance, so the same fly deploy really does run everywhere.
Fly Sprites (launched January 2026): stateful 100GB VMs that spin up in 1–12 seconds and sleep automatically, purpose-built as sandboxes for AI coding agents like Claude Code and GitHub Copilot. A Sprite MCP server lets you drop an agent's work into the cloud with one CLI call.
Fly Postgres and LiteFS: managed Postgres clusters with read replicas per region, plus LiteFS, the open-source FUSE-based SQLite replication layer that replicates a SQLite file across every POP with sub-ms read latency.
Private WireGuard 6PN network: end-to-end encrypted private IPv6 network between every machine, with static egress IPs for third-party allowlists at about $3.60/month each.
Fly Kubernetes (FKS): managed Kubernetes clusters at $75/month per cluster, plus compute — for teams that want multi-region Kubernetes without standing up their own control plane.

What users say about Fly.io

The Hacker News thread on the Sprites launch was the most positive Fly has had in years — Simon Willison called Sprites "the cleanest dev-sandbox plus API-sandbox pairing I've seen," and Thomas Ptacek confirmed on-thread that a local open-source version is coming. On Dept Agency's long-form Fly.io review, the verdict was "genuinely the Heroku successor for 2020s-scale apps."

The complaints are consistent and have gotten louder. On the community forum's "Free tier is dead?" thread and across r/webdev and r/reactjs, three issues come up over and over: (1) billing is unpredictable — a single traffic spike can multiply your invoice overnight because CPU, RAM, volumes, egress, dedicated IPs and inter-region private networking are all metered separately; (2) Fly.io still does not ship billing alerts; (3) the dashboard is minimal and most day-to-day work happens through flyctl. Kurt Mackey has acknowledged on Hacker News that the main CLI surface is "complex" and that the Sprite CLI is an attempt to fix that for new users.

Sprites by Fly.io — stateful 100GB VM sandboxes for AI agents, launched January 2026 — Sprites.dev: Fly's January 2026 product, designed for coding agents that need a disposable Linux VM with a 100GB persistent disk and a one-second cold start.

Fly.io pricing

Fly.io runs entirely on pay-as-you-go resource pricing in 2026 — there is no free tier any more. New accounts get a minimal trial (roughly 2 VM hours or 7 days) before a credit card is required. All prices below are for the US/EU "Amsterdam" tier:

Resource	Price	Notes
shared-cpu-1x (256MB)	~$2.02 / month	Smallest always-on machine
shared-cpu-4x (4GB)	~$23.66 / month	Typical small production app
performance-2x (8GB)	~$85.17 / month	Production web tier
performance-16x (128GB)	~$1,013.80 / month	Large workloads
Volumes	$0.15 / GB / month	Snapshots $0.08/GB, first 10GB free
Egress (NA/EU)	$0.02 / GB	$0.04 APAC, $0.12 Africa/India
Dedicated IPv4	$2 / month	Per app
Fly Kubernetes	$75 / month / cluster	Plus compute and volumes
Machine Reservations	40% off	$36–$14,400 / year prepay
Support	$29–$2,500 / month	Standard → Enterprise

LiteFS — Fly.io's open-source SQLite replication layer, 4,700+ GitHub stars — LiteFS: Fly's FUSE-based SQLite replication layer with 4,700+ stars on GitHub, used to keep a SQLite file in sync across every Fly region.

Who should use Fly.io?

Best for: teams shipping genuinely global apps where latency matters — real-time collaboration tools, WebSocket-heavy backends, multiplayer games, AI inference proxies, and anything that benefits from having the whole stack (compute plus volumes plus Postgres plus SQLite replica) close to users. Notable adopters include Supabase, Builder.io and Mercor, and Sprites is an obvious fit for anyone building coding agents.

Not ideal for: hobby projects and bootstrapped indie SaaS that need a true $0 tier — Railway, Render or a $5 Hetzner VPS will be cheaper and simpler. Also not the best pick for mostly-static frontend apps (Vercel or Netlify are closer to the metal for that) or teams that prefer a polished web dashboard over a CLI.

Pros and cons

Pros:

Genuine multi-region deploy with a single fly deploy — not a marketing gimmick; your machines really do boot in 35 cities.
Firecracker-level VM isolation with sub-second cold starts and suspend-to-memory auto-sleep — unusual at this price point.
LiteFS and Fly Postgres are first-class and actually replicate per-region, not just "available in region X."
Sprites is the cleanest agent-sandbox story on the market in early 2026.
Excellent public engineering blog — Fly engineers document outages, failed experiments and internal architecture in a way few clouds do.

Cons:

No true free tier since 2024; the trial is tight and billing starts the moment you add a card.
Resource-based pricing (CPU + RAM + storage + egress + IPs + snapshots + inter-region networking) makes costs hard to forecast before launch.
Billing alerts still not shipped — traffic spikes can produce surprise invoices.
Dashboard is minimal; complex operations require flyctl and familiarity with fly.toml.
Support is a paid add-on — Standard at $29/month is reasonable, but Premium and Enterprise get expensive fast.

Alternatives to Fly.io

For Heroku-style simplicity on a single region, Railway and Render are faster to get started and still have real free tiers. For Next.js and front-end-heavy apps, Vercel sits closer to the metal. If you want self-hostable on your own VPS, Coolify or CapRover give you Fly-style deploys for the price of a $5 box. For larger enterprise workloads, Northflank and AWS Fargate cover similar ground with a flatter per-hour cost model.

Verdict: is Fly.io worth it?

If your app needs to be within 100ms of users in Tokyo, Johannesburg and São Paulo at the same time — and you'd rather write a Dockerfile than a VPC CloudFormation template — Fly.io is still the easiest way to ship it in 2026. The Sprites launch also makes it the most interesting cloud for teams building with coding agents. We rate it 75/100: the product is very good, but the complex pay-as-you-go pricing and the death of the free tier put it firmly in "production workload" territory rather than "weekend project."

Frequently asked questions

Is Fly.io free?: No. Fly.io ended its Hobby, Launch and Scale free plans in 2024. New accounts now get a short trial (roughly 2 VM hours or 7 days) before you must add a credit card and pay per second of usage.
What platforms does Fly.io support?: Fly.io is a cloud platform with a flyctl CLI for macOS, Windows and Linux, plus a web dashboard. Any Dockerfile-based app runs, and Fly has first-class templates for Rails, Phoenix, Django, Laravel, .NET and Node.js.
How does Fly.io compare to Railway and Render?: Railway and Render are friendlier for single-region hobby apps — both still offer free tiers and richer dashboards. Fly.io is stronger for truly global, latency-sensitive or agent-driven workloads where multi-region deploys and Firecracker-level VM isolation matter.
Is Fly.io open source?: The platform itself is proprietary, but much of Fly's tooling is open source: flyctl (1.6k★), LiteFS (4.7k★) and the Corrosion gossip engine (1.6k★) are all on GitHub under Apache-2.0.
What is Sprites by Fly.io?: Sprites are 100GB-disk Linux micro-VMs launched in January 2026 that boot in 1–12 seconds and sleep automatically, designed as isolated sandboxes for AI coding agents like Claude Code and GitHub Copilot.

#edge-computing

Upstash

Fly.io