Buried under the title “Understand charges beyond the free allowances” is the following:
We’re happy to discuss a refund if you do create compute resources by mistake, or if your app receives unexpected traffic due to an attack and generates a surprisingly large bill. Just send an email to billing@fly.io.
The policy is actually more than that paragraph implies: If you’re a customer of ours, we’re going to charge you in exacting detail for every resource you intentionally use of ours, but if something blows up and you get an unexpected bill, we’re going to let you off the hook.
Right now, what I’m working on is just a start-up. The goal is to eventually license the software to very large enterprise customers.
In my experience selling to these kinds of customers, they are — for good reason — extremely concerned about unexpected costs.
So I need to build cost management into my solution from the start. “Accident Forgiveness” is a great if I were selling to medium-sized companies, but not for very large enterprises.
There’s a reason enterprises have >100 employees whose real responsibility is to control AWS costs.
I need to think about this a bit. Fly.io offers three things that are important for my app:
Easy setup of globally distributed compute
Easy setup if you have a Dockerfile
A transparent and fair pricing model
However, without an easy way to build cost overrun management into the product, I’ll need to set up processes to handle that.