Skip to content
← Have an idea? Share it!

Settings and activity

1 result found

  1. Allow setting a maximum amount per billing cycle

    86 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    14 comments  ·  General  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    Siebe Dom supported this idea  · 
    An error occurred while saving the comment
    Siebe Dom commented  · 

    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