# Fly.io pricing, line by line: Machines, volumes, egress, Managed Postgres, and the same app on Cloud Run

> What Fly.io charges for in 2026: Machines by the second, volumes, egress, IPv4, Managed Postgres and support. No free tier. The same small app priced on Cloud Run.

Published 2026-10-19 · Updated 2026-10-19 · [By Exodus team](https://exodus.elim.io/about) · Pricing, From Fly
<https://exodus.elim.io/blog/fly-io-pricing-next-to-cloud-run>

Fly.io charges by the second for each Machine while it runs, with no plan fee and, for new accounts, no free tier. The smallest Machine, `shared-cpu-1x` with 256 MB, costs $2.19 for 30 days in Ashburn; with 512 MB it is $3.69. Volumes cost $0.15 per GB a month, internet egress $0.02 per GB in North America and Europe, and Managed Postgres starts at $38 a month.

## In short

- Fly.io has had no free tier for new organizations since its plans closed on October 7, 2024. A new account gets a trial of 2 hours of Machine runtime or 7 days, whichever ends first, and then needs a card.
- A Machine is priced by size and region: $2.19 to $528.02 for 30 days in Ashburn, up to 1.615 times that in São Paulo, plus $6.00 per GB of extra RAM. A stopped Machine costs $0.15 per GB of its root file system.
- Volumes are $0.15 per GB of provisioned size, snapshots $0.08 per GB after 10 GB free, a dedicated IPv4 address $2 a month, egress $0.02 to $0.12 per GB by region.
- Managed Postgres runs from $38 a month (Basic: shared-2x, 1 GB, high availability and backups) to $1,922, plus $0.28 per GB of data.
- A small app of 1,000 visits a day costs $3.87 on Fly.io and $1.08 on Cloud Run without a database, and $42.15 against $10.34 with each platform's smallest Postgres. At 10,000 visits a day Fly.io is cheaper: $6.19 against $21.28.

Fly.io prices are from fly.io/pricing and Fly's docs, Google's from its pricing pages, all read on October 19, 2026, for a 30-day month.

## How Fly.io bills

Fly.io bills each organization once a month for what it used. There is no platform fee and no plan to pick: the invoice is a list of resources, each pro-rated to the time it existed. Machines are billed by the second while they are started, volumes and snapshots by the hour. Every organization needs a credit card on file, except one linked to another organization for billing; without a card you can buy prepaid credit from $25. Fly may place a hold of under $10 on a new card to check it.

The lines a web app usually meets are these, and the rest of this guide takes them one at a time:

- **Machines**, the VMs that run your image, by CPU, memory and region.
- **Stopped Machines**, which pay for their root file system only.
- **Volumes** and their **snapshots**.
- **Data transfer** to the internet and between regions.
- **IP addresses** and **certificates**, mostly free.
- **Managed Postgres**, a separate product with plans.
- **Support** and **compliance** packages, optional.

Two things are missing from that list. One is a free allowance: Fly's cost management page says plainly that there is no free account or free tier. The other is a spending cap or alert: the same page says Fly does not support billing alerts yet, and that free credit never caps a bill. If you need a hard ceiling, it has to come from how you size and count your Machines.

## Machines: size, CPU class and region

A Machine's price is a named preset of CPU and memory, plus any memory you add. Shared presets come with 256 MB per vCPU, performance presets with 2 GB per vCPU, and memory beyond that costs $6.00 per GB for 30 days. In Ashburn (`iad`) and Secaucus (`ewr`), Fly's cheapest regions, a Machine running for 30 days costs:

- `shared-cpu-1x`: $2.19 with 256 MB, $3.69 with 512 MB, $6.70 with 1 GB.
- `shared-cpu-2x` with 2 GB: $13.39. `shared-cpu-8x` with 2 GB: $17.55.
- `performance-1x` with 2 GB: $33.00. `performance-2x` with 4 GB: $66.00. The largest, `performance-16x` with 32 GB: $528.02.

![Bar chart of one Fly.io Machine running for 30 days in Ashburn: shared-cpu-1x with 256 MB $2.19, with 512 MB $3.69, with 1 GB $6.70; shared-cpu-2x with 2 GB $13.39; performance-1x with 2 GB $33.00; performance-2x with 4 GB $66.00](https://exodus.elim.io/media/v2026-09-16/t/exodus/assets/image-ed39f8329f45243113cce32a077fd8044693ce6cc71e3c3b3e2ad8ad3c0a1eb3-680x400-svg/bytes "What one Machine costs for 30 days in Fly.io's cheapest region, by size. Fly.io price list, read October 19, 2026")

The two CPU classes are not two speeds of the same thing. A `performance` vCPU is yours all the time. A `shared` vCPU may run 5 ms out of every 80 ms, which is 6.25% of a core, and saves up the time it does not use as a burst balance of up to 500 seconds, during which it runs at full speed. A web app that sits idle and then answers a request fits that well. An app that keeps a core busy, such as image processing or a heavy API, uses its balance up and is then held at 6.25%, and the fix is a bigger preset or a `performance` one. This is the main way a Fly.io bill grows: with traffic, you move up the list above, one step at a time.

Regions change the price of CPU and memory by a multiplier. Ashburn and Secaucus are 1.000; Amsterdam and Stockholm 1.038; London and Paris 1.135; Frankfurt 1.154; Chicago and Dallas 1.250; Singapore and Sydney 1.269; Tokyo 1.308; São Paulo 1.615. So the $3.69 Machine costs about $3.83 in Amsterdam and $4.26 in Frankfurt. Volumes and snapshots do not take the multiplier, and egress is priced by where the data goes, not where the Machine runs.

If your load is steady, Fly sells reservation blocks per region and CPU class with a 40% discount: you pay $36 a year up front for $5 of shared-Machine credit each month, or $144 a year for $20 of performance-Machine credit, and larger blocks to match. The credit applies only to CPU and extra memory, and a month's unused credit is lost.

## Stopped Machines and auto-stop

A stopped or suspended Machine pays nothing for CPU or memory, only $0.15 per GB a month for its root file system, the unpacked image. A Machine with a 1 GB image that is stopped all month costs $0.15.

That is how a Fly.io app can cost less than its always-on price. With `auto_stop_machines` set, Fly's proxy stops Machines that have no traffic and starts them again on the next request. On a first deploy, `fly launch` and `fly deploy` create two Machines for an app that serves traffic, with auto start and stop on and `min_machines_running = 0`, so both can stop when nobody is visiting. An app with a volume gets one Machine, because volumes are not replicated.

Fly's own advice is to budget for the always-on cost and treat anything below it as a saving, because traffic patterns rarely stay put. This guide does the same: its comparisons below assume one Machine running all month. Keep `min_machines_running = 1` if the first request after a quiet hour must not wait for a Machine to start.

## Volumes, snapshots, IPs and certificates

**Volumes** are local disks attached to a Machine. They cost $0.15 per GB a month of provisioned size, not of data written, and they keep billing while detached or while their Machine is stopped. A 10 GB volume is $1.50 a month whether it holds 10 GB or 100 MB. On a mostly idle app, Fly notes, a volume can cost more than everything else together.

**Snapshots** of volumes are $0.08 per GB a month of data stored, after the first 10 GB each month, which are free. New volumes take a daily snapshot and keep five; the snapshots are incremental, so a 10 GB volume with 2 GB of data and little change costs for about 2.5 GB of snapshots.

**IP addresses**: every app gets a shared IPv4 address and IPv6 addresses for free. A dedicated IPv4 is $2 a month per app, which adds up if you give one to every branch preview. A static egress IP, a fixed outbound address for calls to an API that allows a list of IPs, is $0.005 an hour, about $3.60 a month.

**Certificates**: the first 10 single-hostname certificates of an organization are free, then $0.10 a month each; a wildcard certificate is $1 a month.

## Data transfer

Inbound traffic is free. Outbound traffic to the internet is priced by the region the data leaves from:

- North America and Europe: $0.02 per GB.
- Asia Pacific, Oceania and South America: $0.04 per GB.
- Africa and India: $0.12 per GB.

Traffic between Machines in the same region is free. Between regions, over Fly's private network, organizations created after July 18, 2024 pay $0.006 per GB in North America and Europe, $0.015 in Asia Pacific, Oceania and South America and $0.050 in Africa and India, counted in both directions. Older organizations pay the internet rate unless they switch.

Egress is the line where Fly.io and Google Cloud differ most. Google's Premium Tier internet egress from a US region to North America costs $0.12 per GiB after the first GiB of the month, six times Fly's rate, as the [guide to egress on Google Cloud](https://exodus.elim.io/blog/egress-on-google-cloud-explained) explains in detail. An app that sends a lot of data, such as media, large downloads or a busy API, feels it first.

## Managed Postgres

Fly's Managed Postgres is a separate product, priced by plan plus storage. Every plan is a high-availability cluster with automatic backups and connection pooling:

- Basic: shared-2x, 1 GB of memory, $38 a month.
- Starter: shared-2x, 2 GB, $72.
- Launch: performance-2x, 8 GB, $282.
- Scale: performance-4x, 32 GB, $962.
- Performance: performance-8x, 64 GB, $1,922.

Storage is $0.28 per GB of data actually used, metered hourly, up to 1 TB per cluster, so 10 GB of data adds $2.80. Transfer inside the region is free. Fly's docs list what is not there yet: a cluster cannot be upgraded to a new major Postgres version in place (you create a new one and copy the data with `pg_dump` and `pg_restore`), and there are no alerts on CPU or storage, only emails about maintenance.

The older Fly Postgres, which you run yourself as an ordinary Fly app on Machines and volumes, still exists, but Fly lists it as unsupported. It costs what its Machines and volumes cost: about $2 a month for a single-node dev cluster, $82 to $164 a month for a three-node production one. A Managed Postgres cluster also outlives the app that uses it, so delete it separately when you clean up, or it keeps billing.

## Support, compliance and the rest

Community support on Fly's forum is free. Paid support is a monthly package: Standard at $29 (first response within 36 hours), Premium at $199 (24 hours, 1 hour for urgent issues, a dedicated Slack channel) and Enterprise from $2,500, which is also where Fly's 99.9% uptime SLA lives. A HIPAA package with a pre-signed BAA is $99 a month.

A few other lines appear on some bills: Fly Kubernetes at $75 a month per cluster plus its Machines and volumes, and extensions such as Tigris object storage and Upstash Redis, which you pay at the provider's list price through the Fly.io invoice. Early-stage companies can apply for up to $15,000 of credit through Fly's startup program.

## Is there a free tier?

No, not for organizations created since the plans closed on October 7, 2024. A new account gets a trial instead: 2 hours of Machine runtime in total or 7 days, whichever comes first, up to 10 Machines, 20 GB of volumes and 2 shared vCPUs with 4 GB per Machine, without dedicated IPv4 or performance CPUs. Trial Machines stop after 5 minutes of running. When the trial ends, or as soon as you add a card, billing starts and the apps keep running only with a payment method.

A few things stay free after the trial: inbound traffic, the shared IPv4 and IPv6 addresses, the first 10 GB of snapshots and the first 10 certificates. Organizations that bought the old Hobby, Launch or Scale plans before October 7, 2024 keep their allowances of three `shared-cpu-1x` 256 MB Machines, 3 GB of volumes and 100 GB of egress in North America and Europe.

Google Cloud is the opposite case: a free tier that renews every month, such as 2 million Cloud Run requests and 180,000 vCPU-seconds, next to a separate $300 trial. [The Google Cloud free tier for a small app](https://exodus.elim.io/blog/google-cloud-free-tier-for-a-small-app) lists it product by product.

## The same small app on Fly.io and on Cloud Run

The two platforms charge for different things. Fly.io bills the Machines you create, for as long as they run, whatever they do. Cloud Run with request-based billing bills the time an instance spends handling requests, takes its free tier off first, and costs nothing at zero instances.

![Table of the bill lines on Fly.io and on Cloud Run: compute per second while started, $3.69 for 30 days for shared-cpu-1x with 512 MB, against per 100 ms while serving with 180,000 vCPU-seconds free a month; idle $0.15 per GB of rootfs against $0 at zero instances; disk $0.15 per provisioned GB against Cloud Storage at $0.02 per GB; egress $0.02 per GB against $0.12 per GiB with the first GiB free; IPv4 shared free and dedicated $2 against included; Postgres from $38 with high availability against Cloud SQL db-f1-micro at $7.56; free use a trial of 2 hours or 7 days against a free tier every month](https://exodus.elim.io/media/v2026-09-16/t/exodus/assets/image-b579099bfad3bdf831a3cdcca2525237cfef10700480d83258158ef46d380820-680x430-svg/bytes "The same bill lines on the two platforms. List prices read October 19, 2026; Fly.io in iad, Cloud Run in us-central1")

To compare them, take one app and price it on both. It is the app from the free tier guide: a web app of 10 requests per visit, each taking 200 ms, and 0.3 MB sent per visit. On Cloud Run it runs in `us-central1` with 1 vCPU and 512 MiB, priced by exodus-cost, the open pricing code the Exodus report uses, with every request billed for its full 200 ms as if none shared an instance; that is an upper bound. On Fly.io it runs in Ashburn on one Machine all month, sized by the CPU the app really uses, taken as 50 ms of each request: the smallest preset with 512 MB whose shared baseline covers twice the day's average CPU. At 1,000 visits a day:

- **No database.** Fly.io: one `shared-cpu-1x` 512 MB Machine, $3.69, and 9 GB of egress, $0.18: **$3.87**. Cloud Run: 300,000 requests and 60,000 vCPU-seconds fit inside the free tier, and only the 9 GB of egress is billed, $1.08: **$1.08**.
- **With the smallest Postgres.** Fly.io adds Managed Postgres Basic, $38, and 1 GB of data, $0.28: **$42.15**. Cloud Run adds Cloud SQL `db-f1-micro` with 10 GB of SSD, $7.56 and $1.70: **$10.34**.
- **With Postgres that has a standby.** Fly's Basic plan already has one, so Fly.io stays at **$42.15**. Cloud SQL's nearest match is a high-availability `db-g1-small` with 10 GB, $53.75: **$54.83** with the app.

![Bar chart of the small app at 1,000 visits a day for 30 days: with no database Fly.io $3.87 and Cloud Run $1.08; with the smallest Postgres Fly.io $42.15 and Cloud Run $10.34; with Postgres that has a standby Fly.io $42.15 and Cloud Run $54.83](https://exodus.elim.io/media/v2026-09-16/t/exodus/assets/image-07be90996a4fa542133b00938a3974b38da1313018796be7316ced0bfefc755b-680x360-svg/bytes "The small app at 1,000 visits a day on each platform. Cloud Run priced by exodus-cost in us-central1, Fly.io from its price list in iad; list prices read October 19, 2026")

The database decides the middle row. Fly's cheapest managed Postgres is a highly available cluster; Google's cheapest is a single small instance without a standby and outside the Cloud SQL SLA, which is enough for many small apps and not for some. The [Cloud SQL guide](https://exodus.elim.io/blog/cloud-sql-smallest-instances-and-what-they-cost) lists every size in between. When both sides have a standby, Fly.io is cheaper by about $12.70 a month.

## Where the lines cross as traffic grows

The same app without a database, at six levels of traffic:

- 100 visits a day: $3.71 on Fly.io, $0.11 on Cloud Run.
- 1,000: $3.87 and $1.08.
- 3,000: $4.23 and $3.24.
- 10,000: $6.19 and $21.28. Fly.io has moved to a `shared-cpu-2x` Machine; Cloud Run has used up its free CPU time.
- 30,000: $18.56 and $75.43. Fly.io runs a `shared-cpu-6x` with 1.5 GB; on Cloud Run, CPU is $38.88 and egress $32.40 of the total.

![Line chart of the monthly bill against visits a day from 100 to 30,000 for the app without a database: Fly.io with one Machine always on starts at $3.71 and reaches $18.56; Cloud Run starts at $0.11, passes Fly.io between 3,000 and 10,000 visits a day, and reaches $75.43](https://exodus.elim.io/media/v2026-09-16/t/exodus/assets/image-475452812e552fbcc1b27bc51e9d202bdc078154ea4b8fbd244f93a2876b3b4a-680x370-svg/bytes "The same app at six traffic levels. Cloud Run is cheaper below a few thousand visits a day, Fly.io above. List prices of October 19, 2026")

The lines cross between 3,000 and 10,000 visits a day. Below that, Cloud Run's free tier carries the compute and Fly.io's floor is the Machine that runs all month. Above it, two things work for Fly.io: a request on Cloud Run is billed for its whole duration, waiting on the database included, while a Fly Machine is sized by the CPU actually used; and egress costs a sixth as much. With Postgres on both sides, Fly's $38 plan shifts its line up, and Cloud Run with a `db-f1-micro` stays cheaper up to about 10,000 visits a day ($30.54 against $44.47); at 30,000 it is $84.69 against $56.84.

Two things can move Cloud Run's line down. Concurrency lets one instance serve many requests at once, so an app that mostly waits on its database pays for far less CPU time than the upper bound above; [Cloud Run costs, worked examples by traffic](https://exodus.elim.io/blog/cloud-run-costs-worked-examples-by-traffic) shows by how much. And instance-based billing, at a lower rate per second, suits an app that is busy all day. Egress does not move: whatever the platform, the bytes have to leave.

## When Fly.io stays cheaper, and when Cloud Run does

Fly.io is usually cheaper when:

- the app is busy all day, so a Machine that never stops is not wasted;
- it sends a lot of data, since egress is $0.02 per GB against Google's $0.12;
- it needs a database with a standby, where $38 buys a highly available cluster;
- it runs in many regions at once, close to users, at a few dollars per Machine.

Cloud Run is usually cheaper when:

- traffic is low or uneven, so instances spend most of the month at zero and the free tier covers what is left;
- the database can be a single small instance or Firestore, from about $9 or nothing;
- there are many small services, each of which on Fly.io would need at least one Machine.

Price is rarely the only reason to move. Teams move from Fly.io to Google Cloud for managed services next to the app, such as Cloud SQL with point-in-time recovery, Pub/Sub and BigQuery, for IAM across every service, for more regions, or for the 99.95% SLA every Cloud Run service carries, against Fly's 99.9% on Enterprise support. [Moving an app from Fly.io to Cloud Run](https://exodus.elim.io/blog/fly-to-cloud-run) walks through the move itself, `fly.toml` line by line, and [what Cloud Run costs](https://exodus.elim.io/blog/what-cloud-run-costs) explains the other side's prices. For the other platforms people compare with Fly.io, see [moving from Railway or Render](https://exodus.elim.io/blog/railway-or-render-to-cloud-run).

## Checking the numbers for your own app

On the Fly.io side, the bill in the dashboard is the truth: Billing shows the upcoming invoice and a Cost Explorer, and the current month to date. For an app you have not deployed yet, Fly's calculator at fly.io/calculator prices a set of Machines, volumes and traffic. Remember the second Machine that `fly launch` creates, and the Managed Postgres cluster that stays after its app is deleted.

On the Cloud Run side, Exodus does the comparison for a real repository. Its CLI reads `fly.toml`, the Dockerfile and the code on your machine, and the report prices the app on Cloud Run for your traffic next to what it costs on Fly.io now, line by line, with the free tier taken off and the assumptions next to every number. When Fly.io stays cheaper, the report says so. [See a sample report](https://exodus.elim.io/demo).

## FAQ

### Does Fly.io have a free tier?

No. Organizations created since October 7, 2024 have no free tier or monthly allowance. A new account gets a trial of 2 hours of Machine runtime or 7 days, whichever ends first, and then needs a card. Inbound traffic, shared IPv4 and IPv6, the first 10 GB of snapshots and the first 10 certificates stay free.

### What is the cheapest app on Fly.io?

A `shared-cpu-1x` Machine with 256 MB in Ashburn or Secaucus, running all month: $2.19 for 30 days plus egress at $0.02 per GB. With 512 MB it is $3.69. With auto-stop the Machine costs only its root file system while idle, $0.15 per GB a month.

### How much is Fly.io Managed Postgres?

From $38 a month for the Basic plan (shared-2x, 1 GB, high availability, backups and pooling) to $1,922 for Performance, plus $0.28 per GB of data used. 10 GB of data adds $2.80. The cluster bills until you delete it, even after its app is gone.

### Is Fly.io cheaper than Cloud Run?

It depends on traffic and the database. A small app of 1,000 visits a day costs $3.87 on Fly.io and $1.08 on Cloud Run; at 10,000 visits a day, $6.19 against $21.28. With a highly available Postgres on both sides, Fly.io is cheaper at every level.

### Does Fly.io charge for bandwidth?

Outbound only. Egress to the internet 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 traffic and traffic inside a region are free; between regions it is $0.006 per GB in North America and Europe.

## Sources

1. [Fly.io pricing, Fly.io (Machine presets per hour and per month in Ashburn, more RAM at $6.00 per GB, region multipliers from 1.000 in iad and ewr to 1.615 in gru, volumes $0.15 and snapshots $0.08 per GB a month, egress $0.02, $0.04 and $0.12 per GB by region group, dedicated IPv4 $2.00, reserved compute 40% off, Managed Postgres plans, support plans, HIPAA $99, startup credit up to $15,000; read Oct 19, 2026)](https://fly.io/pricing)
2. [Fly.io resource pricing, Fly.io docs (no monthly platform fee; shared-cpu-1x 256MB $2.19, 512MB $3.69, 1GB $6.70 per 30 days; stopped Machine $0.15 per GB of rootfs; first 10 GB of snapshots free; static egress IP $0.005 an hour; SSL $0.10 a hostname, first 10 free; private network between regions $0.006 per GB; reservation blocks; no free tier for new organizations; Fly Kubernetes $75 a cluster; unmanaged Fly Postgres unsupported; example apps at $43.67, $2.21 and $27.20; read Oct 19, 2026)](https://docs.fly.io/about/pricing)
3. [Fly.io free trial, Fly.io docs (2 hours of Machine runtime or 7 days; 10 Machines, 20 GB of volumes, 2 vCPUs and 4 GB a Machine; trial Machines stop after 5 minutes; no dedicated IPv4 or performance vCPUs; adding a card ends the trial; read Oct 19, 2026)](https://docs.fly.io/about/free-trial)
4. [Fly.io billing, Fly.io docs (monthly per organization; Machines per second while started; volumes pro-rated to the hour, billed while detached; pre-authorization under $10; credits from $25; read Oct 19, 2026)](https://docs.fly.io/about/billing)
5. [Fly.io cost management, Fly.io docs (budget for the always-on cost; no billing alerts yet; free allowances do not cap the bill; no free tier; read Oct 19, 2026)](https://docs.fly.io/about/cost-management)
6. [Fly.io discontinued plans, Fly.io docs (plans closed to new customers on October 7, 2024; legacy allowances of 3 shared-cpu-1x 256MB VMs, 3 GB of volumes and 100 GB of egress in North America and Europe; read Oct 19, 2026)](https://docs.fly.io/about/discontinued-plans)
7. [Fly.io Managed Postgres, Fly.io docs (Basic shared-2x 1GB $38, Starter $72, Launch $282, Scale $962, Performance $1,922; HA, backups and pooling in every plan; $0.28 per GB used; 1 TB at most; no in-place major version upgrade; no metric alerts; read Oct 19, 2026)](https://docs.fly.io/mpg)
8. [Fly.io CPU performance, Fly.io docs (a shared vCPU may run 5 ms of every 80 ms, 6.25%; burst balance up to 500 s; performance vCPUs 100%; read Oct 19, 2026)](https://docs.fly.io/machines/cpu-performance)
9. [Fly.io autostop and autostart, Fly.io docs (a stopped Machine pays only its rootfs; a volume bills its full size; min_machines_running applies to the primary region; read Oct 19, 2026)](https://docs.fly.io/launch/autostop-autostart)
10. [Fly.io app availability, Fly.io docs (fly launch and fly deploy create two Machines for process groups with services, auto start and stop on, minimum running zero; one Machine when a volume is mounted; read Oct 19, 2026)](https://docs.fly.io/apps/app-availability)
11. [Fly.io support, Fly.io docs (Standard $29, Premium $199, Enterprise from $2,500 a month; community support free; read Oct 19, 2026)](https://docs.fly.io/about/support)
12. [Cloud Run pricing, Google (request-based billing in Tier 1: $0.000024 per vCPU-second, $0.0000025 per GiB-second, $0.40 per million requests; free 180,000 vCPU-seconds, 360,000 GiB-seconds and 2 million requests a month per billing account; read Oct 19, 2026)](https://cloud.google.com/run/pricing)
13. [Cloud SQL pricing, Google (db-f1-micro $0.0105 an hour, HA db-g1-small $0.07 an hour, SSD $0.000232877 and HA SSD $0.000465753 per GiB-hour in us-central1; shared-core machines outside the SLA; read Oct 19, 2026)](https://cloud.google.com/sql/pricing)
14. [VPC network pricing, Google (Premium Tier internet egress, first GiB a month free per account, then $0.12 a GiB to North America and Europe; read Oct 19, 2026)](https://cloud.google.com/vpc/network-pricing)
15. [Cloud Run SLA, Google (99.95% a month for a Cloud Run service; read Oct 19, 2026)](https://cloud.google.com/run/sla)
16. [exodus-cost, the open pricing crate of the Exodus CLI (Google list prices bundled and dated Oct 9, 2026; the Cloud Run side of the small app computed Oct 19, 2026; the Fly.io side from Fly's price list above)](https://github.com/elim-io/exodus)