This is critical for me as a lone dev. If Firebase won’t offer this obvious option I’ll have to look at some of the options mentioned on this thread.

For many small developers or organizations, not having this feature is a deal breaker. For some of us, having our spending under control might be more important than anything else. It will make Firebase more appealing for everyone.

This would alleviate many users' concerns about high costs and make Firebase much more popular.

Absolutely critical. Looking forward to getting this added.

I have thought if shifting to s new solution because if the ambient anxiety not having this gives me. How is this not a thing.

This will be SUPER helpful to simply set an amount limit per-day so I don't need to over-engineer my Firebase backend and frontend apps to handle potential spam, like I have been in the past.

+1 for peace of mind

I see many developers on social media who are scared of using Firebase because they can end up with a huge bill. This would be a good thing for both developers and Firebase.

Coming back here to point out that:

- Vercel has this: https://vercel.com/docs/pricing/spend-management#managing-your-spend-amount
- Azure has this: https://learn.microsoft.com/en-us/azure/cost-management-billing/manage/spending-limit
- Supabase has this: https://supabase.com/docs/guides/platform/spend-cap
- AWS has this: https://docs.aws.amazon.com/cost-management/latest/userguide/budgets-controls.html

I sent the question below to the Firebase team.
I got the response that an internal ticket exists but I can also create an external ticket so external people can upvote the feature request as well.
If you would like to have this feature available as well, you can upvote this ticket, and hopefully this feature will become reality one day.

Dear Firebase Team,

I hope this message finds you well. I'm writing to share my feedback and a feature request regarding the Firebase Blaze Plan.

First and foremost, I want to express my satisfaction with Firebase. My initial experience with the Spark Plan has been excellent, and I'm truly impressed with the platform. However, as I plan for my second application, which will require additional functionalities such as sending emails, I find myself in need of the Blaze Plan.

I appreciate Firebase's pay-per-use model, which seems fair. However, what concerns me is the absence of a billing cap feature for the Blaze Plan. This lack of a cap introduces uncertainty, and I fear the possibility of unexpectedly high bills due to potential programming mistakes, online bullying, or other unforeseen circumstances.

I'm not alone in this concern; several discussions on platforms like Reddit and Stack Overflow echo similar sentiments, underscoring the importance of addressing this issue.

While I understand Google's rationale for not implementing a cap feature to accommodate potentially high loads, I believe that users should have the option to set a cap on their billing. Personally, I would prefer my site to go down if I exceed the cap rather than facing the anxiety of a hefty bill.

I've gone through the resources provided by Google, including the billing documentation and support FAQs. While the suggestion to implement custom billing caps through user-defined functions is appreciated, I worry about the reliability and robustness of such an approach compared to a built-in solution from Firebase.

Given that the Spark Plan already offers the option to cap billing, I'm hopeful that a similar feature could be extended to the Blaze Plan or perhaps introduced in a new plan tier.

I would greatly appreciate it if you could provide an update on any progress towards implementing billing caps for the Blaze Plan. As a satisfied Firebase user, I am eager to continue utilizing the platform for my projects, but the absence of this crucial feature is a significant consideration.

Thank you for considering my feedback and feature request. I look forward to hearing from you soon.

Kind regards,

Siebe

One of my pet projects was found by bots (because I was streaming the launch publicly with a small group of friends). The resulting bill was $800 within half an hour.

I did not get a refund because it was my code that was not designed to have thousands of people open the app. Thus is was my "fault".

Limiting the budget of a project is an essential part of using an infrastructure provider. This should be a GCP-wide thing, but as the very least a firebase feature.

I use firebase a lot for personal and professional projects, and many times I need to tell a customer "I cannot limit the billing, so yea it's a risk for your budget".

Firebase support literally told me "hey you can just implement this yourself using pub/sub and cloud functions". I should not have to write code to limit my budgets so I can sleep at night.

This is a must have. Simple coding bug may destroy your life if you are single developer. Pay as you go in the current form is a joke. I love Firebase, but I don't use it for my projects, because I don't want to wake up one day with $200k bill to pay for Google... For now, I use Supabase over Firebase.

This is a great idea!