Conversation
Three per-second rates, taken from FlyWeb.Pricing in ui-ex, which is where the scheduled October rates live. Everything else follows: all 14 presets, all 18 regions through the markup table, both the hourly and monthly columns, and the additional-RAM sentence, which derives from the RAM rate rather than being written out. Do not merge before the fly.io side ships. /pricing has no date logic, so it switches when someone changes the code that day. Merging this early or late means the two pages disagree.
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
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
1 participant
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. Do not merge until the fly.io side ships.
Prices change on 1 October and customers have been told. This is the docs half, prepared now so it is reviewed in advance rather than written on the day.
Two lines in
snippets/RegionPricingSelector.jsx:0.000000750.00000084650.000011960.0000127320.000001930.000002316Everything else follows from those: all 14 presets, all 18 regions through the markup table, the hourly and monthly columns, and the additional-RAM sentence, which #2505 changed to derive from the RAM rate rather than being written out.
Where the numbers come from.
FlyWeb.Pricinginsuperfly/ui-exholds the scheduled October rates as@machine_base_cents_per_second_oct_2026and@ram_gb_month_oct_2026. They are in cents per second; these are the same figures in dollars.Verified against what is published. All 14 presets match
fly.io/pricing-updateexactly, hourly and monthly, and the RAM line comes out at $6.00:On timing.
/pricinghas no date logic.FlyWeb.Pricingcarries the October rates but nothing switches to them, and/pricing-updatepasses them explicitly. So on the day a person changes the code and deploys. This PR should merge at that moment, not on a schedule, or the two pricing pages disagree in between.Recheck before merging. These were verified against
/pricing-updateas published on 25 September. If the rates move before the 1st, this PR moves with them.Not addressed here:
bomis still in the region list, tracked in superfly/docs-tracking#316, and the table computes in the browser so none of the figures appear in the HTML that crawlers and LLMs read. Both are separate from the rate change.