Leaving Firebase

Every read is a line item. Growth is the bill.

Firebase bills per read, per write, per invocation, per GB, per monthly active user. Each meter scales with your growth, which is how the $70,000-in-a-day stories happen. Here is a production project at moderate scale.

A typical Firebase bill

$2,570/mo

Firestore reads/writes/deletes (~1.4B reads)$900

Network egress (~6TB)$700

Cloud Functions invocations (~120M)$400

Hosting bandwidth beyond free tier$300

Auth MAU beyond free tier$270

Modeled from operation counts and published rates.

The same workload on Cloudflare Workers

$61/mo

Sized from the workload above, not a marketing tier. Saves $2,509/mo.

Workers Paid plan$5

Requests beyond included (~110M/mo)$33

CPU time beyond included$23

Egress (~7.5TB) — Cloudflare does not bill bandwidth$0

Auth + seats — no MAU billing, no per-seat pricing$0

Honest caveat: Firestore's document model shapes the whole app, so this migration includes a relational redesign. infralift scopes that phase explicitly before quoting, and the quote is still fixed.

The migration is the product

infralift builds the new environment in parallel with your live site, delivers everything as Terraform you own, then cuts over at the edge, which is reversible in seconds for as long as the old stack stays warm. Moving the database needs a short write pause, minutes long and sized from your data. The assessment is free and reads your account with a scoped token; the migration is a fixed fee quoted up front, so the price in the report is the price you pay.

How we handle secrets, data sync, and the cutover itself: the migration process.

Run the free assessment