Working with Firebase?

Firebase open to the world or burning cash? We fix it.

A lot of Firebase projects reach us the week after someone noticed the bill, or the week after a tester found they could read every document in the database. We lock the rules down to what the app actually needs and cut the read volume to match.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

firebase-debug.log

still failing

What it is

Firebase at a glance

Firebase is Google's backend-as-a-service: a bundle of hosted pieces that a mobile or web app can plug into instead of writing its own server. It started in 2011 as a company called Envolve, became Firebase soon after, and was acquired by Google in 2014.

The bundle covers Firestore and the older Realtime Database for storing data, Authentication for sign-in, Hosting for static files, Cloud Functions for server-side code, Cloud Messaging for push, and Analytics and Crashlytics for measurement. It is popular with mobile teams and with web apps assembled quickly from templates and AI tools.

Type
Backend-as-a-service
First released
2011
License
Proprietary SaaS from Google
Maintained by
Google LLC
Typically used for
Mobile apps, chat features, realtime collaboration, prototypes that shipped

The honest version

Firebase pros and cons

No technology is all upside. This is where Firebase earns its place and where it tends to cause trouble.

Where Firebase is strong

  • A back end without running oneFirestore or Realtime Database, sign-in, file hosting, Cloud Functions and push notifications all come from the same console. A small team can ship a working app without hiring an operations person.
  • Fast to get something on screenStarting a mobile or web project against Firebase is a short afternoon. The SDKs are mature and the sample code works, which is why so many prototypes begin here.
  • Realtime sync is genuinely goodDocuments update across clients within a few hundred milliseconds. For chat, presence indicators and collaborative editing it does the hard part for you.
  • Google infrastructure underneathThe services ride on Google's own network and data centres, so uptime and global latency are rarely the thing that goes wrong on a Firebase project.
  • Free tier that goes a long wayThe Spark plan covers small apps outright, which is why side projects and early-stage products often never hit a Firebase invoice at all.

Where Firebase bites

  • The default rules trust everyoneExample security rules from tutorials and starter templates frequently allow any signed-in user, or any user at all, to read and write every collection. Shipped unchanged, the whole database is exposed.
  • Every read and write is meteredYou pay per document read, per write, per gigabyte stored and per gigabyte of egress. A client-side listener in a loop, or a React effect without proper dependencies, can quietly run up four figures in a night.
  • Firestore is not a relational databaseThere are no joins, query shapes are restricted, and getting the data model right up front matters more than it would in Postgres. Awkward queries push logic into Cloud Functions or into expensive client fan-out.
  • The SDKs bind you to the platformFirestore, Auth and Functions each have Firebase-specific APIs that touch your code throughout. Moving off later means rewriting most of that layer, not swapping a driver.
  • Cloud Functions take their time to wakeIdle functions cold-start in seconds, not milliseconds. For an API that users wait on directly, that first request can feel broken.
  • Getting your data out is awkwardThere is no clean one-command export of a live Firestore project. Migrating away means scripts, reconciled batches and a plan that accounts for writes happening during the move.

Sound familiar?

Common Firebase problems we fix

The Firebase problems that bring people to us, and what you have once each one is fixed.

allow read, write: if true;

The security rules let anyone read the database

Starter rules shipped unchanged, or rules relaxed during development and never put back. Anyone who opens the browser console can list your users or orders.

Rules that match the actual data model

bill: $3,847 this month

The bill jumped overnight

A listener in a loop, a function triggering itself, or a client-side query reading the whole collection on every page view. Usually visible in the usage graph within one morning.

Reads cut, alerts before the next spike

PERMISSION_DENIED after tightening rules

Rules are right but the app broke

The old rules were covering for a client that was asking for more than it should. Fixing the rules exposes the query that needs to change too.

Rules and queries aligned

cold start: 8.4s

The first API call after a quiet period hangs

A Cloud Function that has been idle, often with a bulky dependency tree or a slow initialisation step at the top of the file.

Warm paths for the user-facing calls

1.2M document reads in an hour

An innocent change caused a read storm

A new screen subscribing to a collection without pagination, or a background job that forgot to limit its query.

Paginated, with a ceiling on read volume

export in progress · day 2

We want to move off Firebase

Firestore does not hand you a clean dump of a running project. The move needs a staged copy, a cutover window and a way to replay writes that happened in between.

Migrated onto Postgres or Supabase

AppCheck token invalid

Abuse from outside the app

Bots or scraped SDK keys hitting Firestore directly from scripts that never opened the real app.

App Check wired up and enforced

last backup: none configured

There is no backup of Firestore

The console does not back up your data on its own by default, and a bad client write can delete thousands of documents before anyone notices.

Scheduled exports with tested restores

What we do

Firebase help, from rescue to upkeep

Call us for one open rule, or hand us the whole project.

Rescue
Open rules, a surprise bill, or an app that stopped working after a rule change. We stop the bleeding first and explain the cause second.
Security rules
Rules written against the real data model and the queries the app actually makes, tested with the emulator before they go live.
Cost control
Reads, writes and egress traced to the code that causes them. Budget alerts set before the next invoice, not after.
Cloud Functions
Cold starts shortened, retries handled properly, and work moved off the client where it belongs on the server.
Migrations
Moving off Firestore onto Postgres or Supabase in a planned cutover, or tightening a Firebase project you want to keep.
Managed Tech
Rule reviews, usage monitoring and a team to call when the dashboard looks wrong, on an ongoing basis.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Firebase alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Firebase questions

Something else? Call+1 737 727 7327

Is my Firestore data readable by anyone?

Open the Firebase console, go to Firestore, and look at the Rules tab. If you see 'allow read, write: if true' or rules that only check whether the user is signed in, then any visitor or any registered account can read every document. We audit the rules against the collections and the app's real queries and rewrite them to match.

Why did my Firebase bill jump?

Almost always it is a sudden rise in Firestore document reads, Cloud Function invocations or outbound bandwidth. The usage graph in the console shows the day it started; from there we trace it to the listener, loop or background job that caused it and cap the damage.

Can we move off Firebase to Postgres or Supabase without rewriting the app?

Parts of it, yes. Auth and file storage port over reasonably cleanly. Firestore queries and Cloud Function triggers need rework because the data model is different. We scope that honestly before you commit to a move.

How do I write Firebase security rules properly?

Start from deny-all and open each collection only for the specific reads and writes the app actually needs, checking the authenticated user against document fields. Test the rules in the Firebase emulator against the real queries before deploying, and keep them in version control alongside the code.

Why are my Cloud Functions slow on cold start?

A function that has been idle has to boot its runtime, load its dependencies and run any top-level setup before it serves the first request. Trimming the dependency tree, moving one-off work out of the global scope and keeping critical paths warm bring that first call back under a second.

How much does Firebase help cost?

Estimates are free. Describe what the project is doing and you get a price before any work starts.

Free estimate

Firebase project worrying you?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.