We want pricing at Fly.io to be as simple as humanly possible, so you don’t have to spend any brain-space on figuring out what your bill’s gonna look like. So, we’re getting rid of plans. Pricing will now be just “pay for what you use.”
We haven’t changed the pricing on any of our individual resources. The difference is: we’re not grouping certain things together and calling them “Launch” or “Scale” anymore.
You can see pricing broken down by resource here, or you can use our shiny new pricing calculator to fool around with different elements.
How can I purchase things that previously came with plans, like Support and Compliance?
They’re now sold separately, so that you can pick only the things you need (when you need them). You can get Support at 3 different levels, depending on your needs ($29/month for Standard, $199/month for Premium, or Enterprise starting at $2500) or add on a Compliance package for $99/month. If you want more details, you can check out the Support page here, the Compliance page here, or purchase either one in your dashboard.
What if I already have a plan?
Rest easy; for those with existing plans, nothing changes. You’ll continue to get the same stuff (support, compliance, free allowances, etc) that previously came with your plan, and pay the same amount.
Our intent here is to make things simpler, not increase prices; that’s why we’re separating things out, so that people can pick the individual elements they want to use.
But yes, you’re right that separating out Support makes it a little more expensive. We’re still working things out, so please keep giving us feedback as we share updates.
Fly.io no longer offers plans to new customers. If you purchased a Launch or Scale plan before October 7, 2024, you can remain on those plans unless you upgrade, change your payment method, or otherwise stop using Fly.io.
Dropping plans also means that everyone can launch apps in every region, right? So, e.g. fra is not reserved for people with plan anymore?
@Elder I feel like you’re being extremely shrill, and borderline toxic, without much reason. We’re not raising your prices.
We are making bundling and pricing changes based on feedback. What we’ve learned when we talk to people who haven’t become paid customers yet is (a) it’s hard for people to understand what they’re getting and (b) people already have expectations of how cloud billing works that they’d like us to conform to.
In particular, we got two very specific responses to our old plans:
Many, many devs are building med tech apps and want a HIPAA BAA, and they want to be able to check that box for about $100 per month before they launch. ~$200 per month was far too much
People were really confused about support. They’re used to paying for support agreements specifically, bundling it with usage didn’t make any sense. If you search the community forum you’ll find many people who aren’t sure if they have support access or not.
This set of changes applies to new sign ups and people who might benefit from the HIPAA BAA only. It has no effect on what you or anyone else is already paying.
And, given aggregate organization billing, you can apply what you’ve already got to many new organizations.
We’re doing our best. It’s not easy! Pricing is complicated, and, as you can see, people are unsparing in their analyses of any pricing change. Different companies handle this problem in different ways. Our way is to be up front about things, even when that means our explanations are clumsy or create more questions, and rely on mutual trust with our users that we’re not trying to sneak stuff past them.
We have raised prices in the past and will again. When we do that, we’ll do it openly and proudly. We’re not scared of sharing our economics with our users. That’s part of the premise of our service, and a big part of the reason we run our own hardware.
That doesn’t mean we won’t occasionally slip a price increase into something, but if you catch one of them, you can safely assume we missed it. We’re glad to have things like that called out, but call us out for being fallible, not for being sneaky.
(And, of course, like Kurt said, this pricing change doesn’t impact people currently on plans anyways.)
This one stung because a lot of internal effort went into figuring out how to make our pricing more legible to users, and how best to communicate our pricing.
Both can be true, though (regardless of the intent)? If given a choice, folks (like me) paying more than $29+/mo would ideally prefer the Launch plan over paying $29 separately for support.
Glad that folks like me on the Launch plan are being grandfathered in.
you can remain on those plans unless you upgrade, change your payment method, or otherwise stop using Fly.io.
Is there a way to ensure we never get migrated to this simpler billing?
Our experience has been that most customers don’t agree, but all of this stuff involves a lot of turning the dials and figuring out what works, and we’re glad to be able to do it in public and in dialogue with our customers.
If we ever do something with pricing that freaks you out, you know where to reach us. We don’t want to bill you for stuff you don’t want.
Hey, love the new pricing calculator! I will be using it a bunch as I plan some things out. I’m curious about the pricing of volumes. Since their launch, they have been $0.15/GB. Most cloud providers offer block storage in ranges from $0.08-$0.12/GB. However, they usually also provide some level of redundancy.
Can we expect volumes to gain some sort of fault tolerance or a price reduction since right now the only option to increase durability is to run at least 2 volumes, and replicate the data at the app level at the price of $0.30+/GB?
So how do you choose how many CPU cores the machine has?
I’m my opinion, GPU selection should be separate from the CPU type. GPU is an add-on that simply limits the CPU type to performance and requires a minimum machine size.