{"slug": "google-cloud-s-new-spend-caps-work-with-firebase", "title": "Google Cloud's new spend caps work with Firebase", "summary": "Google Cloud announced new spend caps on budgets that pause supported services when a cap is reached, and they work with Firebase services including Cloud Functions for Firebase, Firebase AI Logic, Firebase App Hosting, and Firebase Extensions. The feature allows multiple caps per project, one per service, and is available now, though limited to a single Google Cloud project and a single eligible service per budget.", "body_md": "This week, [Google Cloud announced the ability to set spend caps on budgets](https://cloud.google.com/blog/topics/cost-management/new-early-anomalies-and-spend-caps-on-google-cloud-budgets). This is a Big Deal. The new spend caps actually pause supported services when a cap is reached.\n\nSince Firebase projects are Cloud projects, spend caps can apply to Firebase services, too! Specifically, these:\n\n| Firebase product | Cloud product |\n|---|---|\n| Cloud Functions for Firebase | Cloud Run Functions |\n| Firebase AI Logic | Gemini API or Gemini Enterprise Agent Platform (formerly Vertex AI) |\n| Firebase App Hosting | Cloud Run (plus\n|\n| Firebase Extensions | Cloud Run Functions |\n\nI set up spend caps on one of my projects and thought I’d share a bit about the experience.\n\n## Caps on multiple services\n\nOne thing that confused me in the spend cap setup flow was that I was only able to pick a *single* service (and [the docs](https://docs.cloud.google.com/billing/docs/how-to/budgets-spend-caps#limitations) say “Spend caps are limited to budgets that are scoped to a single Google Cloud project and a single eligible service within the specified project.”).\n\nWhat if I use Functions *and* AI Logic in a project? Do I need to pick just one? Thankfully, no. Even though a **single** cap only supports a single service, I could create **multiple spend caps**, one for each service:\n\n## Setting up a spend cap\n\nI’ll leave the full setup instructions to [the documentation](https://docs.cloud.google.com/billing/docs/how-to/budgets-spend-caps), but if you’re curious, here’s what spend cap setup looked like for me:\n\n- Create a budget, and choose “Spend cap enforcement”.\n- Choose the service that backs the Firebase product you’re using.\n- Set an amount.\n- View the notification thresholds (trying to change them shows a popover “Spend cap notification settings cannot be edited”).\n\n## Set them up on your project\n\nRead through [Manage spend cap budgets](https://docs.cloud.google.com/billing/docs/how-to/budgets-spend-caps) (and especially [Limitations](https://docs.cloud.google.com/billing/docs/how-to/budgets-spend-caps#limitations)) before making a decision, but even with the current limitations, this is a valuable new tool to prevent surprise bills.\n\nAnd, just a reminder that Firebase’s [Avoid surprise bills](https://firebase.google.com/docs/projects/billing/avoid-surprise-bills) guide has other tips to, well, avoid surprise bills.", "url": "https://wpnews.pro/news/google-cloud-s-new-spend-caps-work-with-firebase", "canonical_source": "https://jhuleatt.com/posts/cloud-spend-caps-firebase/", "published_at": "2026-07-31 00:00:00+00:00", "updated_at": "2026-08-27 19:19:26.713169+00:00", "lang": "en", "topics": ["ai-products", "developer-tools"], "entities": ["Google Cloud", "Firebase", "Cloud Functions for Firebase", "Firebase AI Logic", "Firebase App Hosting", "Firebase Extensions", "Gemini API", "Gemini Enterprise Agent Platform"], "alternates": {"html": "https://wpnews.pro/news/google-cloud-s-new-spend-caps-work-with-firebase", "markdown": "https://wpnews.pro/news/google-cloud-s-new-spend-caps-work-with-firebase.md", "text": "https://wpnews.pro/news/google-cloud-s-new-spend-caps-work-with-firebase.txt", "jsonld": "https://wpnews.pro/news/google-cloud-s-new-spend-caps-work-with-firebase.jsonld"}}