> It's easy to build a bad billing cap that would slow down services and cause outages When you've exhausted your billing cap, what else could it do? Either sh

> It's easy to build a bad billing cap that would slow down services and cause outages When you've exhausted your billing cap, what else could it do? Either shutting off services or blowing past the cap seem like the only serious options. For a lot of small businesses, I suspect that an outage is often better than risking a surprise 6 figure bill. But it depends on what your software does. Also if the system shut down automatically when the budget got exhausted, there's a risk that a runaway backup process or something might accidentally eat through your regular budget and get the site shut down. For that, it might make sense to assign different resources into different budgetary buckets or something. I'm surprised firebase doesn't implement something like that.