- Company sizes or stages where this product is overkill or insufficient
- For conventional CRUD applications with minimal real-time requirements, a managed Postgres or plan-based database may offer simpler modeling and more predictable costs.
- Industries or use cases where competitors are clearly superior
- Heavy analytics and BI-driven workloads generally favor relational warehouses or lakehouse patterns and SQL-native systems.
- Technical requirements that this product cannot meet
- Applications that require complex multi-entity relational constraints and ad-hoc joins as primary database operations.
- Budget constraints that make alternatives more appropriate
- When surprise billing is unacceptable, an operation-based pricing model introduces practical risk unless mitigated by strong FinOps practices and instrumentation.
- Specific workflows or integrations where the product falls short
- Workloads needing robust full-text search or advanced aggregations typically require auxiliary systems, increasing total cost of ownership.
- Red flags in the buying process
- If a team is unable to invest in FinOps instrumentation, billing exports, and guardrails, the operation-based cost model can lead to unexpected costs as usage scales.
- Current limitations acknowledged by the vendor
- The platform supports Native mode and Datastore mode; the feature set differs between modes and the mode selection is often irreversible for a given database instance.
- Firebase Security Rules must be correctly configured to avoid insecure defaults when client SDKs have direct access.
- Features on the roadmap (not captured)
- Specific roadmap items were not identified in the materials reviewed; customers should request current product roadmaps from the vendor.
- Scale limitations (practical limits)
- Vendor materials emphasize scalability; community feedback suggests that practical limits are often economic (cost at scale) rather than purely technical.
- Security or compliance gaps
- Product-level certification disclosures are often managed at the platform level or via NDA; buyers should validate that Firestore is in scope for required compliance frameworks.
- Architectural limitations mentioned in reviews
- Document modeling can become difficult to maintain at scale without tooling and clear patterns, leading to architectural complexity over time.
- API limitations or integration constraints
- Mode selection (Native vs Datastore) is a foundational architectural choice and can constrain future migration paths.