Hello! I see a few topics where people asked if this functionality exists, but here is an official feature request.
From the other topics:
”I’m afraid of leaving an instance accidentally running and racking up unexpectedly huge costs. How do I set a spend limit to ensure this doesn’t happen?”
”Does this mean that if my API key gets compromised, I could end up paying thousands of dollars because there’s no way to establish spending limits and no system in place to warn about usage?”
They both make some good points. This feature seems pretty important.
We are most certainly aware that spending limits is a fairly common request from our users.
Our engineering team are looking into the overall feasibility of implementing this feature.
For now, kindly keep checking your expenditures in the Usage page in your Cloud Dashboards to keep track of each instance’s costs.
I can imagine how creating usage limits on rented instances could get messy (example: every time a long running instance breaches the spend-limit, the provider has to decide to eat the cost and track a debt or kill what might be a mission-critical non-resumable workflow for someone).
With this in mind there are many interim solutions I would hope could be added in the near term. I like AWS’s approach with customizable billing alerts or even instance start/stop alerts. It’s not bulletproof by any means but the risk is massively reduced.