Start with the job Firebase needs to do for you. Use the same acceptance checks for each candidate; do not infer a recommendation from a catalogue label.
How to use this shortlist
These candidates keep the existing editorial order. Dated documentation supports the plan facts; it does not establish equal output quality or a tested migration. Try your own small task before switching.
Applications needing Postgres plus integrated identity and storage.
Free
Monthly organization plan starting prices, supported by the official USD billing FAQ. 50,000 MAU; 500 MB database; 1 GB storage; two active projects; pauses after one week of inactivity.
Limits and paid options
Access policies, backups and application logic remain your responsibility. Compute and resource usage can exceed the plan starting price.
Model representative data and verify access is isolated between test users.
Rehearse a migration, backup and recovery exercise with a small dataset.
Quote storage, compute, requests, egress and the required operational support.
Compare these candidates side by side, then select each plan.Open comparison →
Keep the switch reversible
Export a small sample, verify it can be restored or imported, and keep the existing workflow available until the trial passes. Record the missing features and migration work before moving a team.
Check the budget and evidence
Each card links to its dated plan source. Check the billing basis, seats, usage and migration work before moving. Missing details stay unverified.