Google Firestore

Firestore is a NoSQL document database that Google runs as a managed service. Data is stored as documents, which hold fields and nested objects, grouped in collections, and a document can contain further subcollections. It started as the database for Firebase mobile and web apps, where client libraries talk to it directly under security rules, and it is also used from server code in Node.js, Java, Python, Go, C++ and Unity, or through REST and RPC.

Google says the service replicates data across zones automatically, offers strong consistency and ACID transactions, and scales without servers to manage. Two editions exist: Standard keeps the native API, and Enterprise adds a MongoDB-compatible API so existing MongoDB drivers and tools can be used. It only runs on Google's infrastructure.

• Document and collection model. Records live in documents with typed fields, nested maps and lists, organised in collections and subcollections. Queries can chain several filters and sort conditions, and Google says they are designed to stay efficient as data grows.
• Realtime listeners. Client apps subscribe to a document or a query and receive changes as they happen. Google presents this as the basis for collaborative and live-updating apps, and billing counts a read each time a result changes.
• Offline persistence. Mobile and web SDKs cache data in use on the device, so an app keeps reading, writing and listening while offline and syncs once the connection returns. Google lists offline mode for iOS, Android and web.
• Security rules and Authentication. A declarative rules language restricts access by user identity or data patterns, and Firebase Authentication supplies sign-in. This lets a front end talk to the database without a custom server layer in between.
• Transactions and replication. The documentation names automatic multi-region replication, strong consistency, atomic batch operations and ACID transactions. Multi-region locations such as Europe 3 sit next to single-region choices like Frankfurt, Paris or Warsaw.
• MongoDB compatibility. Enterprise edition accepts MongoDB application code, drivers and integrations, which Google positions as an option for teams that want a serverless document store but keep their MongoDB tooling.
• Operations and queries. The pricing page covers vector search with nearest-neighbour index reads, aggregation queries such as count, Query Explain to see index use, TTL deletes, point-in-time recovery, backups, restore and clone operations.

• A two-person team building a mobile app. The SDKs, rules and sign-in let the app read and write directly, and the daily free quota covers early traffic. The team avoids running an API server until business logic requires one, then adds Cloud Functions triggers.
• A SaaS company storing per-customer settings and activity. Documents map naturally to accounts and records, and listeners can update dashboards live. Costs follow operations, so the team watches read counts when screens poll or lists load many documents.
• A company moving a MongoDB workload to managed infrastructure. Enterprise edition's MongoDB compatibility lets existing code and drivers continue. The move ties data to Google Cloud, so the team should check export and exit steps before committing, since Google describes no stand-alone deployment.

The documentation points to Firebase and Google Cloud consoles for creating a database, choosing a location and picking the Standard or Enterprise edition. The location is chosen when the database is created, from a long list that includes European regions.

A free quota applies to one database per project, and further use needs billing enabled on the Google Cloud project. The docs provide quickstarts for web, iOS, Android and server languages, and agent skills for coding assistants. Developers who know document databases learn the collection model quickly, but query indexing and billing rules take attention.

Firestore Enterprise edition includes MongoDB compatibility and Standard edition keeps the native API. Billing counts operations, so a chatty application pays by the read. The Standard free quota is 1 GiB, 50K reads and 20K writes a day.

The database management systems list places Google Firestore 16 of 22: ScyllaDB sits directly above it and Amazon DocumentDB directly below. After the challenger places, Google Firestore is one of the established names, ranked in order and without a score.

By headquarters, 15 of the 22 are established in North America, as Google Firestore is in the United States.

The MongoDB compatibility overview says it is part of Enterprise edition, serverless, with 99.99 percent availability regional and 99.999 percent multi-regional.

In the catalogue: Per document read, write and delete plus storage; daily free quota on Standard edition.

Google lists a daily free quota for Standard edition per project: 1 GiB of stored data, 50,000 document reads a day, 20,000 writes a day, 20,000 deletes a day and 10 GiB of outbound transfer a month. Only one database per project qualifies, and TTL deletes, point-in-time recovery, backups, restores and clones are not covered. Beyond that, billing is per 100,000 document reads, writes and deletes, per GiB of storage and per GiB of bandwidth, with rates that depend on the location and discounts for 1-year and 3-year commitments. Queries are charged one read per batch of 1,000 index entries in some cases. Enterprise edition has its own pricing page.

Basis: firebase.google.com/products/firestore, read for the Best Database Management Systems in 2026 guide (reviewed 7 November 2026).

The pricing page lists many locations, including Frankfurt, Paris, Zurich, London, Warsaw, Stockholm, Madrid, Milan, Belgium, the Netherlands and the multi-region Europe 3, so EU residency can be chosen at creation.

Firebase's privacy page says Google is generally a data processor under GDPR and that the services are certified under major standards, with reports available through Google. Specific certification names were not listed in the text checked. Backups and clones are available for export and copies.

Integrations the vendor names (9):

• Firebase Authentication
• Cloud Functions
• Firebase SDKs for iOS, Android and web
• Node.js, Java, Python, Go and C++ client libraries
• Unity SDK
• REST and RPC APIs
• MongoDB drivers and tools (Enterprise edition)
• Firestore Query Explain
• Google Cloud billing and committed use discounts

These are the nearest neighbours of Google Firestore in the same list, picked on shared traits and price model.

• Microsoft SQL Server (#10 of 22): Windows and Linux database licensed per core, with free Express edition.
• Oracle Database (#11 of 22): Not for: small teams that need cheap, portable and simple setup. Commercial enterprise database, now branded Oracle AI Database, with capped free edition. (United States)
• ScyllaDB (#15 of 22): Wide-column database compatible with Cassandra and DynamoDB APIs. (United States)
• Azure Cosmos DB (#18 of 22): Microsoft's distributed database with NoSQL, MongoDB, Cassandra and PostgreSQL APIs. Suits: Azure teams wanting turnkey multi-region distribution. (United States)
• YugabyteDB (#22 of 22): Best for: Teams sizing a managed SQL cluster by vCPU who can estimate storage and transfer.

Read from the vendor’s own pages on 5 November 2026.

• firebase.google.com/products/firestore: product overview, editions, MongoDB compatibility, offline and rules
• firebase.google.com/docs/firestore: data model, replication, consistency, SDKs
• firebase.google.com/docs/firestore/pricing: billing components, free quota, listener and index read rules
• cloud.google.com/firestore/pricing: location list, commitment discounts, Standard edition pricing
• firebase.google.com/support/privacy: GDPR role and compliance statement

The same four questions are asked of every database management systems product: time to value, real cost, the way out and the intended buyer. On those tests Google Firestore lands at place 16 of 22. Details: how we rank software.