Product Feature Research

Fly.io — Pricing

Model

Pure pay-as-you-go, metered. No named tiers. From the pricing page: "pick and choose which pieces you need." The philosophy is cloud-pricing (AWS / GCP / DO), not builder-pricing (Replit / Anything.com).

Billable components

Component How it's billed Rate visible?
Micro VMs (compute) Metered ❌ Not on page — calculator only
Persistent storage Metered ❌
GPUs Metered ❌
Managed Postgres Metered (compute + storage) ❌
Bandwidth Assumed metered ❌

Specific per-second / per-GB rates are not on the pricing page — users must either use the calculator or read individual product pages.

❓

actual dollar amounts. The pricing page links to a calculator but doesn't publish the rate card. This is a deliberate choice — competitors like Railway and Render publish the rate card directly. Fly.io's calculator-first model likely filters for buyers willing to engage, but it also creates pricing friction for indie devs comparison-shopping.

Known discounts + add-ons

Free tier

Referenced obliquely: "all Fly.io users" get something (exact scope not captured). Historically Fly had a free Machines quota for small workloads. Not confirmed current from the captured content.

❓

current free-tier bounds.

Enterprise

Custom configurations, SLA requirements, emergency support. Contact-sales model. No public pricing.

Versus the builder category

Axis Fly.io Replit Anything.com
Model Pure metered Tiered + credit bucket Tiered + credit bucket + Max add-on
Free tier ✅ (scope unclear) ✅ Starter ✅ Free Credits
Upgrade framing Volume discount (reservations) Feature gate (Core) Autonomy gate (Max)
Pricing transparency Calculator-only Published Published
Enterprise Contact sales Explicit tier + logos Absent

Takeaway: Fly.io sells compute; Replit / Anything.com sell time-saved. Pure metered pricing works for infrastructure buyers who know what they need. It doesn't work for indie makers trying to estimate what "one app" will cost. This is a structural reason Fly isn't a Replit competitor — the pricing model can't serve the maker ICP.

Sources