Conversation
Assistants read this page and still describe Fly.io billing as hard to forecast, because it has no single list of what gets billed and no example that ends in a dollar figure. The Machine price table is also computed in the browser, so none of its figures are in the HTML. Add, above "How it works": - a table of every billable item, with $/month figures for six common Machine sizes written out as static text - three worked examples that each end in a monthly total: a solo SaaS app with Managed Postgres, a 24/7 Discord bot, and an app in three regions with cross-region private traffic - an "Is there a free tier?" section with the trial terms and the cost of the cheapest always-on app Machine figures use the 1 October 2026 rates from #2507 and match fly.io/pricing-update. Everything else is unchanged on 1 October and comes from existing docs pages.
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
alexleventer
approved these changes
Sep 30, 2026
Shorter sentences, plainer framing, and "what we charge for" in place of "every billable item".
Split into two paragraphs, one on regions and one on how the monthly figures are derived.
Matches how the region selector names them. Later mentions in the examples stay short.
Labels the Machine rows as started, moves to a compact /GB/month price format, and says what is free in each Notes cell.
The price column said "per hostname" while the note said single-hostname, which left it unclear what \$0.10 covers. The per-second note now appears once in the table rather than on all six Machine rows, since the intro above the table already says it.
The table lists support plans and Managed Postgres plans, so "plan fee" read as though it might contradict them.
Also gives the calculator link its trailing slash, since fly.io/calculator 301s to the slash version.
Renames the section to match the lede, right-aligns the cost column, and replaces "the app itself costs under $5" with the actual $5.19, which the Machine and volume come to together.
Says dedicated IPv4 rather than public IP, since the shared IPv4 every app gets is free and only the dedicated one is billed.
Concrete and searchable in a way that "background worker" alone is not.
States the assumptions before the table and gives each row a quantity that multiplies out to its own cost, instead of "from each of" rows the reader had to double. Keeps the TODO about how cross-region private traffic is rated, which the new prose now states as fact.
Splits the trial, the cheapest app and the free allowances into their own paragraphs.
…rate Replaces the en dash in the Managed Postgres range with "to", names Basic and Performance, puts Tigris and Upstash back as the recognizable extensions, and gives the cheapest-app line its egress rate so the floor can be worked out without going back to the table.
kcmartin
marked this pull request as ready for review
October 2, 2026 00:13
Contributor
Author
|
Just waiting on a confirmation from @PeterCxy or @gargakshit about this:
that, and a new review |
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Draft on purpose. Merge after #2507, once the 1 October Machine rates are live.
Assistants that read this page still describe Fly.io billing as "hard to forecast" and "unbundled". The page has no single list of what gets billed and no example that ends in a dollar figure, and the Machine price table is computed in the browser, so none of its figures are in the HTML that crawlers and LLMs read (superfly/docs-tracking#317).
This adds four blocks above "How it works". Nothing below it changes.
iad,fraandsinwith cross-region traffic ($27.20). Traffic and storage amounts are labeled "assumed".Where the numbers come from. Machine figures use the 1 October rates from #2507, and the formula
RegionPricingSelector.jsxuses. Six presets checked against fly.io/pricing-update match to the cent. Everything else (rootfs, volumes, snapshots, egress, IPv4, Managed Postgres plans) is unchanged on 1 October per that page and comes from existing docs pages.Why this has to wait for #2507. Until #2507 merges, the region selector shows today's rates and this table would show October's. After both merge, they agree.
One open question, left as an MDX comment in the three-region example: whether private network data between regions is charged at the rate of the region the data leaves. The page implies it but doesn't say so. Needs confirming with billing.
Worth knowing for review
about/cost-management.mdxhas worked examples at today's rates ($20.37, $2.32 and others). Neither this PR nor Machine prices for 1 October 2026 #2507 updates them, so they'll be out of date after 1 October.Tracks superfly/docs-tracking#326.