Suggestion on setting billing limits: implement them yourself 🤩

We see here from time to time a request for billing caps, and the answer is either the Accident Forgiveness Policy, or that explicit caps may appear on the Fly internal development roadmap in the future. For some potential customers, this may not be enough.

So, I thought I’d float an idea. Of course Fly has a RESTful API, and it’s a feature-complete Fly playground. Any customer can write an app to explore all the apps and machines to which it has permissions, and monitor usage levels, and stop/suspend any machines that have gotten out of control.

I appreciate customers would like this to exist already, and for it to be built into the platform. But for customers of a certain size, writing this extra bit of infra might be a relatively trivial effort, which would give them the reassurance factor that an automatic action will be taken when certain limits are hit.

This could be offered as an open-source project too, for anyone inclined to help others benefit from the same feature.

1 Like