Firebase
Fewer than 5 people recommend it so far, so there's no written verdict. Here is what commenters said.
2recommend
18warn against
Nov 5, 2025first mention
Sep 29, 2026latest mention
Why people recommend it
“We use firebase which supports the preview environments.”
“Both make it pretty dead simple to deploy.”
Show 2 more
“For personal projects, usually Firebase (+ occasional Cloud Run mixed in) which makes it relatively easy.”
“For simple apps, I prefer Firebase on GCP.”
Caveats and dissent
“Absolutely wild that such a widespread SDK could crash everyone with a serverside change.”
Show 2 more
“I read a bit about their pricing models and lost interest.”
“immediately went to my firebase project to downgrade my plan. This is horrific.”
Often compared with
Who recommends it in their own words
Threads where it came up
- €54k spike in 13h from unrestricted Firebase browser key accessing Gemini APIs 4 mentions
- He was called a 'terrorist sympathizer.' Now his AI company is valued at $3B 2 mentions
- Ask HN: Who wants to be hired? (January 2026) 2 mentions
- Show HN: SyncKit – Offline-first sync engine (Rust/WASM and TypeScript) 2 mentions
- Tell HN: Firebase service causing iOS crashes across many apps 1 mention
- Show HN: Every AI agrees with you. This writes your startup's obituary instead 1 mention
Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.
All comments 40
“Absolutely wild that such a widespread SDK could crash everyone with a serverside change.”
“Stack: Firebase functions”
“React Native, Supabase, Firebase, RevenueCat, Webflow,”
“And firebase?! Oh geez.”
“MySQL, Supabase, Firebase”
“It's on firebase”
“I read a bit about their pricing models and lost interest.”
“built with Capacitor, RxDB and Firebase”
“Cloud Social (Flutter app with real-time feeds + Agora live video/voice on Firebase)”
“you would be able to use Google firebase's free tier”
“with a Firebase backend”
“We use firebase which supports the preview environments.”
“This `push` rule publishes the static site to our CDN (firebase).”
We have spend caps at the billing account level and the project level (developer set) in the Gemini API now. There is up to a 10 minute delay in processing everything but this should significantly mitigate the risk here: https://ai.google.dev/gemini-api/docs/billing#tier-spend-caps By default, new Tier 1 paid accounts can only spend $250 in a given month.
That's actually crazy. So I can build a project I love, that does good, but somehow get in a situation where I'm accidentally paying 30.000€ (or 50.000€) to a big tech company? How is that fair? I mean yes, as a software engineer, you ought to reflect on all possible weaknesses, but there was a time when overlooking something meant something completely different than being down 30/50k. That is actually life-altering.
“immediately went to my firebase project to downgrade my plan. This is horrific.”
Considering the amount of repositories on public GitHub with hard-coded Gemini API tokens inside the shared source code (https://github.com/search?q=gemini+%22AIza%22&type=code), this hardly comes as a surprise. Google also has historically treated API keys as non-secrets, except with the introduction of the keys for LLM inference, then users are supposed to treat those secretly, but I'm not sure everyone got that me
“lots of outgoing requests, including”
“Receiving a ping from Firebase Cloud Messaging triggers the app”
“Stack is vue and firebase”
“cheapo Firebase account”
“Firebase auth”
“Single HTML file game backed by Firebase and Cloudflare Workers.”
“Built with Flutter + Firebase.”
“Built with Next.js, Firebase Admin SDK, and OpenAI”
“No reason to use mongodb or firebase in 2026”
“these are time-delayed e-mails and there is no out of the box way to do the straightforward thing”
“firebase avoidance on degoogled phones”
“Backend: Firebase + Google Cloud Run”
“reactive backends similar to Firebase, Airtable and Zapier, which come so close to almost working for normal people but miss the mark fundamentally”
“found that it also had rate limits from what I can tell which wouldn't have been so useful”
“both so that you don't have to operate (admin/provision/whatever) services”
“proprietary services that spy on your customers, like Sentry and Firebase”
“React + Vite on the frontend and Firebase on the backend”
“Next.js frontend, Firebase auth, Firestore for state”
“Both make it pretty dead simple to deploy.”
“For personal projects, usually Firebase (+ occasional Cloud Run mixed in) which makes it relatively easy.”
“Firebase”
“Firebase Auth”
“interfaces with our firebase based authentication”