Should You Switch to Usage-Based Billing? Calculate Your ROI First
Bas de GoeiFly.io runs apps close to users on a global network, making it a popular choice for fly hosting among developers. The platform charges on a usage basis for compute, storage, and bandwidth, with optional support tiers.
Fly.io pricing in 2025 is primarily usage-based, with standard support plans starting at $29 per month. Fly.io pricing ranges from effectively $0 (for tiny hobby usage) up to enterprise-level spend with premium support, depending on usage and support needs.
This guide explains Fly.io features and pricing so you can understand its pricing models in 2025 at a glance.
Note: For the most up-to-date pricing, check Fly.io’s official pricing page. Plan details may change over time.
Below is a breakdown of each available Fly.io pricing plan as of 2025, what it offers, and who it’s built for.
There’s no monthly fee. Users pay based on what their app consumes: virtual machines (billed per second), storage (at $0.15 per GB per month), and outbound bandwidth (starting at $0.02 per GB).
Fly.io no longer offers a general free tier for new organizations. While new accounts don’t include a free plan, documentation still references Fly.io free tier features for legacy users who retained early allowances.
Key features:
Basic support plan with a 36-hour response time and technical architecture assistance, ideal for solo developers and early-stage teams.
Standard is the first paid tier. It focuses on giving small teams access to help without jumping into high-cost support.
Key features:
Better support with faster response times, dedicated Slack access, and quarterly architecture reviews for scaling apps.
Premium adds faster, more hands-on support and visibility into how apps perform on Fly.io.
Key features:
Top-tier support with 24/7 response coverage, 15-minute emergency SLAs, and dedicated engineering contacts for mission-critical workloads.
Key features:
Remember: For the most updated pricing info, always check Fly.io’s pricing site.
Fly.io supports private networking with Tailscale, which allows secure, encrypted communication between machines without writing any VPN configs.
Tailscale itself offers a free tier and paid business plans, but on Fly.io, users don’t pay extra to enable WireGuard tunnels between Fly-hosted machines in their app. That means:
Note: Explore common pricing models for products in our dedicated post on the subject. For context on other no-code tools, you should look into Glide pricing.
Here’s a quick overview of Fly.io’s usage-based elements and their pricing.
Machines are billed per second. A shared 256 MB instance costs approximately $0.0027 per hour, or around $1.94 per month if it runs continuously. Larger instances scale in a predictable, linear cost structure, making budgeting simpler.
Persistent volumes are priced at $0.15 per GB per month. Users pay for provisioned size, whether it’s full or not, and storage costs continue even if the VM is stopped.
Outbound data starts at $0.02 per GB in North America and Europe. Other regions can cost up to $0.12 per GB. Inbound bandwidth is free. Inbound traffic and same-region app/machine traffic remain free under granular rates
Services like Fly Postgres, Redis, and object storage are charged separately. A small database may cost $2 to $5 per month. High-availability setups can cost $80 or more per month.
Note: To estimate the monthly bill more accurately, users can try theFly.io pricing calculator. It lets them input machine sizes, hours, bandwidth, storage, and support options to see a real-time cost preview.
Usage-based billing suits platforms that meter infrastructure. It ties price to actual consumption and encourages user adoption. Here is why teams choose it:
Note: For a practical overview of when to mix subscriptions with meters, read our hybrid pricing guide.
Buyers expect bills that reflect the value they receive. The model scales across customer sizes and workloads without reworking plans. This approach ties directly into modern cloud billing expectations, where costs reflect real consumption rather than fixed tiers.
Here are some reasons why usage-based billing is growing in popularity.
Usage ties spend to outcomes. When customers process more requests, store more data, or transfer more bytes, the price follows that activity. This builds trust because units match how teams experience value in production. Procurement reviews a clear mapping from usage to cost.
Traffic shifts by region, time, and feature rollouts. Seasonal peaks and launch surges push usage up only when they occur. Quiet periods pull usage down without manual adjustments. Teams avoid plan changes and can stay focused on performance and reliability.
Companies ship new capabilities often. Metered building blocks let teams introduce, package, and iterate on features without reworking legacy tiers. Finance updates rates or thresholds while engineering ships improvements. Pricing evolves at the same pace as the product.
The same events that drive operations drive invoicing and reporting. Usage flows into revenue, margin, and forecast models. Leaders review one source of truth for volume, cost, and price. Decisions move faster because the data stays consistent across tools.
Note: If you plan to test meters, thresholds, or free allowances, explore our guide to pricing experiments. It covers experiment design, guardrails for revenue, and a simple launch checklist.
You can use Fly.io’s deployment calculator to estimate monthly costs based on VM sizes, hours, bandwidth, storage, and support levels. Just input your expected usage, and it shows a real-time price preview.
Fly.io itself is not fully open source, but it supports and contributes to open-source tools like the Fly.io CLI and Nix-based build systems. Many of its building blocks are open or self-hostable. However, the full Fly platform is proprietary.
Fly.io runs applications on its global edge network, with data centers in over 30 regions across North America, Europe, Asia, and more. You can deploy apps close to your users for better latency. Specific regions can be selected per deployment.
Orb helps teams launch and manage usage-based pricing. You can define billing metrics with the Orb SQL Editor or a visual editor and build new pricing plans without engineering.
Orb ingests and tracks every raw event so invoices remain accurate and transparent as your pricing evolves. It also enables forecasting and supports workflows across finance, product, and ops. Here’s how Orb can help you launch pricing models and evolve them over time:
If you want to launch your pricing models with confidence, Orb helps you do it without complex engineering. Explore Orb’s flexible pricing tiers.
See how AI companies are removing the friction from invoicing, billing and revenue.