Compare

Fly.io vs Railway

Fly.io and Railway both host apps you deploy, and the bills are built differently. Fly.io charges no monthly platform fee: a started Machine is billed per second, and the published Machine price depends on the region. Railway's plan fee is a minimum usage commitment, then CPU and memory are billed per second for what a running service uses. Unbroker is a third option. App CPU and memory follow the capacity you configure while replicas run.

Fly.io and Railway figures were read on November 3, 2026.

How the bill is built

Fly.io's pricing page says new organizations use pay as you go, with no monthly platform fee and no free tier. A trial lasts up to 2 hours of Machine runtime or 7 days, whichever comes first, and it does not require a credit card. After the trial, a card is required to keep billable resources. Railway publishes Hobby at $5 per month with $5 of included usage, and Pro at $20 per workspace per month with $20 of included usage. If usage stays inside that credit, the usage bill is the plan fee. If usage is higher, Railway charges the usage total. Included usage resets each cycle.

The monthly Machine prices below assume 30 days of continuous runtime in Fly.io's lowest-priced regions, Ashburn (iad) and Secaucus (ewr). Railway's monthly column is the same per-second rate held for a full billing month. The invoice is still per second, so a service that runs for part of the month costs less than that constant. Unbroker's app rates come from the current pricing catalogue, not from either vendor's meter.

Fly.io and Railway prices read on November 3, 2026. Unbroker rates come from the current catalogue.
TopicFly.ioRailwayUnbroker
Plan feeNo monthly platform fee. New organizations pay for resources they use.Hobby $5 per month with $5 of usage. Pro $20 per workspace per month with $20 of usage. The fee is a minimum commitment.Free is $0 inside published caps. Pro is $25 per month with $25 of usage credit. The credit does not roll over.
App computeA started Machine is billed per second. shared-cpu-1x with 256MB RAM is $2.19 per 30 days in Ashburn or Secaucus. 512MB is $3.69. 1GB is $6.70 in those regions.CPU $0.00000772 per vCPU-second ($20 per vCPU over a full month). Memory $0.00000386 per GB-second ($10 per GB). Billing is per second of use.$0.03 per vCPU-hour and $0.015 per GiB-hour of the capacity you configure, while replicas run.
Stopped or idleA stopped or suspended Machine is billed for its root filesystem at $0.15 per GB per month.A running service meters CPU and memory even with no traffic. A stopped service does not accrue that compute charge.Configured CPU and memory accrue while replicas are running. Replica autoscaling bills the replicas that are actually running.
Disk and egressVolumes are $0.15 per GB per month of provisioned capacity. Public egress is $0.02 per GB in North America and Europe, $0.04 in Asia Pacific, Oceania, and South America, and $0.12 in Africa and India. Inbound transfer is free.Volume disk uses a $0.15 per GB monthly constant and is billed per second. Service egress is $0.05 per GB.App egress is $0.05 per GB after the included amount (10 GB on Free, 100 GB on Pro). A Linux cloud server does not meter egress as a separate overage.

Regions

Fly.io's regions page lists 17 region codes. Machine CPU and RAM prices vary by region. On the pricing page, a shared-cpu-1x Machine with 1GB of RAM is $6.70 per 30 days in Ashburn, $7.73 in Frankfurt, and $8.50 in Singapore. Volumes are not given that regional markup. Managed Postgres is marked on 13 of the 17 regions. Stockholm, Paris, Secaucus, and Johannesburg are on the list and are not marked for Managed Postgres.

Railway's regions page lists four deploy regions: US West (California), US East (Virginia), EU West (Amsterdam), and Southeast Asia (Singapore). It says those regions provide the same experience. Changing a service's region does not, on that page, require a domain change. A service with a volume needs the volume migrated, and that migration causes downtime.

Unbroker Linux cloud servers are offered in the European Union, US Central, US East, and US West, at one monthly price in each. Cloud Apps on the shared cell are not a scheduler you pin to Fly.io's region list. Managed database and server regions follow the create flow for that product. The regions guide is the placement note.

Deploying an app

Fly.io's launch guide starts with flyctl. From the project directory, fly launch scans the app and, for most common frameworks, generates a Dockerfile and configuration. An existing Dockerfile can be used instead. fly deploy ships the app. Builds with Fly.io's builders, and storage in the Fly.io registry, are not charged today. The pricing page says that can change, with notice.

Railway's quick start deploys from a GitHub repository in the dashboard, from the CLI with railway init and railway up, or from a Docker image. Private Docker registry deploys require Railway Pro. GitHub autodeploys are documented separately.

On Unbroker you connect a Git repository and use a framework preset. Pro also builds a Dockerfile or runs a container image. A GitHub-connected service can deploy on push to the configured branch, and Pro can open a preview for a pull request. Read Unbroker as a Railway alternative for the longer note. The migration steps live on Migrate from Railway and in the Railway migration tutorial.

Databases

Fly.io Managed Postgres is a separate product from the app. Plans run from Basic at $38 per month (Shared-2x, 1GB RAM) to Performance at $1,922 per month (Performance-8x, 64GB RAM). Every plan includes high availability, backups, and connection pooling. Storage is $0.28 per GB for a 30-day month, metered on usage for current clusters. You choose Postgres 16 or 17 at creation, and a major version is not upgraded in place. Managed Postgres can be created only in regions the regions page marks for it.

Railway maintains PostgreSQL, MySQL, Redis, and MongoDB templates, provisions them, and ships security patches for their images. The Redis template is owned by Redis. High availability, backups, point-in-time recovery for PostgreSQL and MySQL, and PostgreSQL connection pooling are turned on by you. Railway's databases page says it does not publish an uptime SLA. Schema, queries, and data stay yours. You can also run another database from a Docker image.

On Unbroker, a managed database is a provider-operated cluster and requires Pro. The smallest managed Postgres plan in the current catalogue is $21.21 per month for 1 vCPU, 1 GB RAM, and 10 GB of storage, separate from the Pro fee. An Apps database node is a database image you operate as a private service. Recovery depends on the engine and plan. The managed Postgres page lists the plans.

Scaling

Fly.io scales by changing Machine count, CPU, and RAM. The launch guide points at those controls. Fly Proxy can start and stop or suspend Machines from traffic settings in fly.toml, including a minimum number left running. A separate metrics autoscaler is documented for keeping spare stopped Machines ready. A started Machine is billed per second. A stopped one is billed for rootfs.

Railway scales vertically up to the plan's CPU and memory limits, and horizontally by setting a replica count in the service settings. Replicas can be placed in more than one region. Public traffic goes to the nearest region, then Railway distributes requests at random inside that region. The scaling page says sticky sessions are not supported. The pricing page lists replica caps of 1 on Free, 2 on the free trial, 6 on Hobby, and 42 on Pro.

Unbroker replica autoscaling requires Pro. You set a minimum and a maximum, and the bill follows the replicas that are running, not the maximum. On the shared cell a service can run up to 3 replicas. Repository and upload services can run several replicas. Image services, workers, and any service with a persistent volume run one replica. Free services run one replica. The services guide and replica autoscaling spell out the triggers.

Where Unbroker fits

Pick Fly.io when the app needs a specific region on that 17-region list, or when you want to size Machines and stop them. Pick Railway when you want CPU and memory billed from what a running service uses, and the app already runs there. A $5 Hobby plan with $5 of usage can fit a small project. Price the workload, including disk, egress, and the database, before you treat any fee as the whole invoice.

Unbroker fits when you want the app from Git, a provider-operated database, and an optional Linux cloud server on one account, operated from the console, the API, or ubctl. The app CPU and memory line follows the configuration you set. A traffic spike does not change that line while the settings and the running replica count stay the same. It is a different meter from Fly.io and from Railway, not a promise that the invoice is lower.

Read the Railway alternative, Fly.io alternatives, Railway vs Render, and Railway pricing. Unbroker fees are on pricing. VPS vs PaaS and Docker Compose to production cover the hosting shape.

Questions

How do Fly.io and Railway prices differ?

There is no single answer. Fly.io prices a Machine preset per second, and that preset's price changes by region. Railway prices a plan fee plus per-second CPU and memory for what a running service uses. On November 3, 2026, the smallest always-on Fly.io Machine was $2.19 per 30 days in Ashburn or Secaucus, and Railway Hobby was $5 per month with $5 of usage. Add disk, egress, and the database before you compare invoices.

Does Fly.io or Railway have a free plan?

Fly.io's pricing page says new organizations have no free tier and no monthly free allowance. The trial is up to 2 hours of Machine runtime or 7 days, whichever comes first. Railway lists Free at $0 with $1 of usage per month, and a free trial with a one-time $5 credit for 30 days. Unbroker Free is $0 with hard caps: 1 project, up to 2 services, 250m CPU, and 256 MiB per service.

Where does Unbroker fit between Fly.io and Railway?

Unbroker hosts the app from Git and can add a managed database or a Linux cloud server. App CPU and memory follow configured capacity while replicas run, at $0.03 per vCPU-hour and $0.015 per GiB-hour. Pro is $25 per month with $25 of usage credit. That is a different meter from Fly.io's Machine presets and from Railway's per-second usage.

Can I use the same regions on all three?

No. Fly.io lists 17 regions, and Managed Postgres is marked on 13 of them. Railway lists four regions and says they provide the same experience. Unbroker Linux cloud servers are the European Union, US Central, US East, and US West. Cloud Apps are not placed by picking a city from Fly.io's list.

Sources