Firestore reads are costing money and you can't see where

What should be true before you start?

Before you optimize anything, accept what the Firestore usage page can and cannot tell you. It shows reads over time as a single total; it does not say which collection, query, or screen produced them. The work is to add that missing dimension — a name on every read — without adding load to the database you are trying to make cheaper.

Read cost is a measurement problem before it is an optimization problem. You cannot cut what you cannot attribute, and a database bill is a single total with no memory of which feature, screen, or background job spent it. The first job is to make the reads legible — grouped by the part of the product that caused them — so the expensive path is obvious instead of theoretical.

• Know your baseline: the reads-per-day total from the Firebase console.
• List the read-heavy paths you suspect — feeds, dashboards, scheduled jobs.
• Decide the feature names (buckets) you want your reads grouped under.

How do you find where the reads go?

The Firestore read meter installs once and counts the documents each query already returned. It does not run a second query to measure, so it never inflates the bill it is reporting on. You wrap the paths you care about in a named bucket, and every read inside — anywhere in the call stack — is grouped under that name.

The honest version of this measures the work already in hand. A good read meter counts the documents or rows a query already returned — it never runs an extra query, an EXPLAIN, or a profiler scan to measure, because a cost tool that itself costs reads is worse than none. Counting stays in memory, and attribution rides on the name you gave the path.

• Install the collector and pass your Firestore instance so the read meter activates.
• Wrap a suspected path in bucket("home-feed", ...) so its reads group under that name.
• Let the meter count get(), count(), and onSnapshot reads automatically — no per-call code.
• Open the readout and rank features by reads; the biggest bar is your first target.
• Wrap any unnamed remainder so no reads stay attributed to “untagged”.

import { init, bucket } from "@cross-deck/buckets"

init({ firestore }) // installs the read meter — observe-only, no extra queries

await bucket("home-feed", () =>
  db.collection("posts").where("live", "==", true).get())

Where do teams get this wrong?

The trap is assuming a user-facing feature is the culprit. More often it is something on a timer.

Most read-cost surprises are not one greedy query; they are an unattributed one. A scheduled job that re-reads a collection every few minutes, a dashboard that re-scans on every refresh, or a listener that fans out on each change can outspend every user-facing feature combined — and none of it shows up until you group the reads by cause and one bar dwarfs the rest.

• Blaming the feed or search when a scheduled job is re-reading a collection every few minutes.
• Refreshing a dashboard that re-scans the same documents on every load.
• Leaving listeners attached that re-read on every change, fanning out reads invisibly.

How does Crossdeck Buckets surface this?

Crossdeck Buckets is built on the no-monster rule: the meter observes the documents a query already returned, keeps a count in memory, and flushes a small summary about once a minute. The dashboard reads that summary, never the raw data, so watching your costs never adds to them.

In practice you open one view, see that a background reconcile job is your largest single source of reads, and fix that one path — instead of guessing across the whole app.

This is also the upgrade path, and it stays free across the step. The open-source collector shows the reads on one surface, grouped by the buckets you named — no account needed. Sign up to Crossdeck and a single SDK install adds the dimension the collector alone cannot see: which environment each read ran in — your server, your web app, your dashboard, or a mobile build — folded into the same buckets, still free. A spike stops being a guess between “is it the backend or the client?” and becomes a labelled segment you can read at a glance.

What should a healthy setup let you do?

After instrumenting, you should be able to open one view and name the top three features by read load, point to the single path driving the biggest bar, and say which environment it ran in. If that still takes a spreadsheet and a guess, the setup is not finished.

A healthy setup also makes the next change cheap to verify. Shipping an index, a cache, or a narrower query should move a specific bucket down — and you should be able to see that it did, not infer it from next month’s invoice.

• Rank features by read load and find the biggest single path.
• See which environment a read ran in — server, web, dashboard, or mobile.
• Confirm a fix moved the right bucket down, not just the bill as a whole.

What should you review after it is running?

Review the biggest bucket first — the single largest source of reads is almost always where the cheapest win lives. Then look for the rhythm that does not match your users: a steady overnight wave with nobody on the app is a machine, not a customer, and machines are the easiest reads to cut.

Treat the read meter as an operating surface, not a one-time audit. Each spike, each new feature, and each background job is a chance to confirm the cost is attributed before it compounds.

• Start at the largest bucket; that is where the cheapest win usually is.
• Watch for read patterns with no matching user activity.
• Re-check attribution whenever you add a feature or a scheduled job.

How should the whole team use it?

Read cost is not only an engineering concern. A founder watching runway wants the trend and the biggest line item. An engineer wants the exact path and environment to fix. Both are reading the same buckets, just at different depths.

When the cost is attributed by feature and labelled by environment, the conversation changes from “the database bill went up” to “this job, on the server, doubled — here is the fix.” That is the difference between a vague worry and a one-line task.

• Founder: watch the trend and the largest cost driver.
• Engineering: jump to the exact path and environment to fix.
• Everyone: reason from one attributed view instead of a single total.

Frequently asked questions