I was looking for a spending limit/cap, including using compute to test new deployments before they churn through my money. I was looking at the following discussion:
“We do have prepaid support. You can buy $25 or more of credits and we suspend the account when credits are exhausted.”
I was under the impression that if I bought prepaid credit this would mean I would not be invoiced.
However once used up it rolled straight into invoicing. So I would like to clarify whether there’s any way to controll spending limits to prepayed amounts.
We aren’t able to cap spending limits at this time. It’s something we’d like to do in the future, but it’s not immediately planned.
The vast majority of charges comes from the VM size (CPU and RAM) and volume sizes you manually choose. The only variable is bandwidth, in most cases this isn’t a large part of monthly charges. The best way to manage costs will be to keep track of the number and size of the VMs you choose for your apps.
One crucial difference between Fly.io and other cloud vendors is that on Fly, machines are never created automatically; you create them and decide the amount of resources they will have. “Auto-scaling” on Fly.io means “starting or stopping machines that you have explicitly created”; it never means “machines appear out of thin air and start emptying your wallet”.
Credits are not a way to control spend. We meter all your usage, and issue a bill at the end of the month. If you have credits, those are used first to cover the outstanding balance. But any remaining unpaid amount is charged to your payment method on file.
If you want to cover everything with credits, what you can do is log in near the end of the month, check your bill to date, and load up enough credits to cover that. It’s the only way to prevent charges from going to your payment method.