I’ve seen past questions about this but I’m still confused on how to prevent wild charges after I add my credit card.
Example, I build a chat bot for a website and that chat is hit by a bunch of bot/spam chats. How am I protected from that running up the bill?
Sorry, I’m clearly new to all of this but I feel like there has to be a better way of presenting how billing works for new people? I would assume you’re losing potential business because of it.
The simple answer here is: the only charge you don’t have explicit control over is bandwidth. If you want to avoid wild charges, provision no more resources than you can afford at maximum.
We have cost reduction features like auto-suspend, but in the pathological case, your machine can be running non-stop for the full month. That is your maximum cost for CPU/RAM. And so on for other resources.
If your concern is a big bandwidth bill, you could closely monitor your bandwidth. Lots of potential ways to do this - I don’t know if the managed grafana we provide supports alerts (you may need to subscribe to a different plan of theirs), but that is one potential solution.
This is only really a concern if your app is publicly accessible. If you just want it for private use, you can do everything using flyctl proxy, which all happens through private networking. That way you never need to provision a public IP and your app will not be accessible from the public internet.
We are aware that people want better ways to handle this. Nothing is on our roadmap yet, but it’s definitely under consideration. Sorry I’m not able to offer anything more firm in this respect, hope the above is helpful.
Thank you so much! That is helpful. My use case is a public facing chat feature so that’s where my concern is coming from. I’ll consider my options but appreciate you explaining it this way no matter what.