diff --git a/about/cost-management.mdx b/about/cost-management.mdx index 4d4f9bf2b5..04ce35ab0a 100644 --- a/about/cost-management.mdx +++ b/about/cost-management.mdx @@ -15,12 +15,12 @@ We’ve done our best to make billing on Fly.io something you can reason about. ## A few examples -So when you’re budgeting, you can look at what you’ve provisioned and do some quick math. Let’s say you’ve deployed three “shared-1x 1GB” machines in `sjc`. That’s \$20.37/month, tops. If you let them stop when idle, you might only pay for a few hours of compute—but the worst-case scenario is still capped at that monthly rate. +So when you’re budgeting, you can look at what you’ve provisioned and do some quick math. Let’s say you’ve deployed three “shared-1x 1GB” machines in `sjc`. That’s \$23.95/month, tops. If you let them stop when idle, you might only pay for a few hours of compute—but the worst-case scenario is still capped at that monthly rate. Here are a few more grounded examples: -- A **staging app** running in the `sjc` region with one `shared-1x 256MB` machine that auto-stops when idle might cost less than **\$1/month**. If you leave it running full-time, it’s still only **\$2.32/month**. -- A **queue worker** (also in `sjc`) that uses metrics-based autoscaling on `shared-1x 512MB` machines might average 3–5 machines running during busy hours. If those stay up for 50% of the month, you’re looking at **\$5.72–9.52/month**, worst-case around **\$19 month** if they all run 24/7. +- A **staging app** running in the `sjc` region with one `shared-1x 256MB` machine that auto-stops when idle might cost less than **\$1/month**. If you leave it running full-time, it’s still only **\$2.62/month**. +- A **queue worker** (also in `sjc`) that uses metrics-based autoscaling on `shared-1x 512MB` machines might average 3–5 machines running during busy hours. If those stay up for 50% of the month, you’re looking at **\$6.61–11.01/month**, worst-case around **\$22 month** if they all run 24/7. We recommend budgeting for the “always-on” cost. You can get under that number with auto-stop or bursty usage, but don’t depend on it to hit your budget. diff --git a/blueprints/shared-nothing.mdx b/blueprints/shared-nothing.mdx index 84b2d178d6..51a121f0b6 100644 --- a/blueprints/shared-nothing.mdx +++ b/blueprints/shared-nothing.mdx @@ -325,7 +325,7 @@ For those who are curious, here's the [deployment script](https://github.com/rub This is a decent sized personal project, deployed across three continents. Even with a -significant amount of over-provisioning, the costs per month are around \$60, before taking +significant amount of over-provisioning, the costs per month are around \$75, before taking into account plans and allowances. @@ -336,16 +336,16 @@ I have two machines that will run puppeteer and Chrome on demand. keep things simple, I'm going to ignore all of that and just look at the total costs. From there, add your plan and subtract your allowances to see what this would cost for you. -And be aware that things may change, the below numbers are current as of early March, 2024. +And be aware that things may change, the below numbers are current as of October 2026. -Let's start with compute. 9 shared-cpu-1x machines with 1GB each at \$5.70 per month total \$51.30. -Two shared-cpu-1x machines with 512MB each at \$3.19 per month total \$6.38. +Let's start with compute. 9 shared-cpu-1x machines with 1GB each at \$6.70 per month total \$60.30. +Two shared-cpu-1x machines with 512MB each at \$3.69 per month total \$7.38. The print on demand machines are on bigger machines, but are only run when requested. I've configured them to stay up for 15 minutes when summoned. Despite all of this the -costs for a typical month are around \$0.03. So we are up to \$57.71. +costs for a typical month are around \$0.03. So we are up to \$67.71. Next up volumes. I have 9 machines with 3GB disks, and 2 machines that only need 1G each. -29GB at \$0.15 per month is \$1.35. +29GB at \$0.15 per month is \$4.35. I have a dedicated IPv4 address in order to use ssh. This adds \$2.00 per month. @@ -353,9 +353,9 @@ Outbound transfer is well under the free allowance, but for completeness I'm see which at \$0.02 per GB amounts to \$0.32. And about 0.1GB in Asia Pacific, which at \$0.04 per GB adds less than a cent, but to be generous, let's accept a total of \$0.33. -Adding up everything, this would be 57.71 + 1.35 + 2.00 + 0.33 for a total of \$61.39 per month. +Adding up everything, this would be 67.71 + 4.35 + 2.00 + 0.33 for a total of \$74.39 per month. -Again, this is before factoring in plans and allowances, and reflects the current pricing in March of 2023. +Again, this is before factoring in plans and allowances, and reflects the current pricing in October 2026. For my needs to date, I'm clearly over-provisioning, but it is nice to have a picture of what a fully fleshed out system would cost per month to operate. diff --git a/elixir/getting-started/migrate-from-heroku.mdx b/elixir/getting-started/migrate-from-heroku.mdx index efc47f9370..1d782d35fe 100644 --- a/elixir/getting-started/migrate-from-heroku.mdx +++ b/elixir/getting-started/migrate-from-heroku.mdx @@ -312,7 +312,7 @@ Fly.io pricing is [metered for the resources](/about/pricing) you use. Database | Fly.io Resource | Specs | Price | |----------|------|-------| -| App Server | 1GB RAM | ~\$5.70/mo | +| App Server | 1GB RAM | ~\$6.70/mo | | Database Server | 256MB RAM / 10Gb disk | ~\$3.44/mo | | **Estimated cost** | | ~\$9.14/mo | @@ -330,7 +330,7 @@ Here's roughly the equivalent resources on Fly: | Fly.io Resource | Specs | Price | Quantity | Total | |----------|-------|-------|----------|--------| -| App Server | 4GB RAM / 2X CPU | ~\$62.00/mo | 8 | ~\$496/mo | +| App Server | 4GB RAM / 2X CPU | ~\$66.00/mo | 8 | ~\$528/mo | | Database Server | 64GB RAM / 500GB disk | ~\$633/mo | 2 | ~\$1,266/mo | | **Estimated cost** | | | | ~\$1,762/mo |