Databases · head to head
FaunaDB vs Firestore

FaunaDB
Databases
Document-relational database whose hosted service closed in 2025 and whose core is now unmaintained Apache 2.0 code.
- From
- Free
- Rated
- -

Firestore
Databases
Flexible, scalable NoSQL cloud database from Firebase
- From
- Free
- Rated
- -
The short version
- Each has a real cost: FaunaDB the hosted service was wound down in 2025, so there is no managed Fauna to buy; every remaining user either operates a JVM cluster themselves or migrates, and both are projects rather than tasks.; Firestore the no-cost Spark plan caps Standard edition at 50,000 document reads, 20,000 writes and 20,000 deletes per day
- They diverge on capability: FaunaDB covers Document-relational model, Firestore covers Document Model.
- Prices and features above were last checked on 30 August 2026.
Where they differ
Only the attributes on which FaunaDB and Firestore actually diverge.
Identical on both: starting price (Free), pricing model (freemium), free tier (Yes), user rating (Not yet rated), category (Databases).
What each one covers
Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.
Only in FaunaDB
- Document-relational model
- FQL v10
- Distributed ACID transactions
- HTTPS access
- User-defined functions
- Attribute-based access control
- Document history
- Event streaming
Only in Firestore
- Document Model
- Real-time Updates
- Offline Support
- ACID Transactions
- Expressive Queries
- Multi-region
- Security Rules
- Firebase Auth
What people use each for
The jobs each tool is most often brought in to do.
FaunaDB
- Keeping an existing Fauna-backed application alive on self-hosted infrastructure while a migration is planned and fundednot Firestore
- Extracting historical data from a Fauna dataset that can no longer be reached through the hosted APInot Firestore
- Studying a production implementation of deterministic distributed transactions, since the full server source is now readable under Apache 2.0not Firestore
- Forking the engine deliberately, where an organisation has JVM and distributed-systems staff and wants a document-relational store it fully controlsnot Firestore
Firestore
- Storing structured application data with realtime listenersnot FaunaDB
- Backing mobile and web apps with a serverless document databasenot FaunaDB
- Building offline first apps that sync when connectivity returnsnot FaunaDB
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
FaunaDB
- The hosted service was wound down in 2025, so there is no managed Fauna to buy; every remaining user either operates a JVM cluster themselves or migrates, and both are projects rather than tasks.
- The open-sourced repository has had no substantive activity since May 2025 and the drivers were frozen alongside it, so you inherit responsibility for security patches in a Scala distributed database that almost nobody else is running.
- FQL has no wire or dialect compatibility with anything else, so migrating off is a rewrite of every query, index and access rule in the application rather than a data export.
- No BI tool, ORM or CDC connector speaks FQL, so reporting and analytics always required exporting the data first, and that export tooling is now also unmaintained.
- The community was small before the shutdown and has dispersed since, so operational answers, tuning advice and people who have run a Fauna cluster in anger are all scarce when something breaks.
Firestore
- The no-cost Spark plan caps Standard edition at 50,000 document reads, 20,000 writes and 20,000 deletes per day
- The Spark plan caps storage at 1 GiB and network egress at 10 GiB per month
- Charging is per document read, so a query returning many documents bills for every one of them
- Going beyond the free thresholds requires the pay as you go Blaze plan billed at Google Cloud rates with no fixed monthly ceiling
Pricing, plan by plan
FaunaDB
Free- FreeFree
- 100K read ops
- 50K write ops
- 1GB storage
- Pro$25/month
- Pay per use
- Priority support
- Advanced features
Firestore
Free- SparkFree
- 1GB storage
- 50K reads/day
- 20K writes/day
- BlazeFree
- Pay as you go
- Unlimited operations
- Multi-region
Which should you pick?
Choose FaunaDB if
- You need document-relational model.
- You want to start without paying.
- You also want fql v10.
Choose Firestore if
- You need document model.
- You want to start without paying.
- You work on Web, Ios, Android, Flutter.
- You also want real-time updates.
Questions people ask
- Is FaunaDB or Firestore better?
- Neither clearly leads. FaunaDB starts at Free and Firestore at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, FaunaDB or Firestore?
- FaunaDB starts at Free and Firestore at Free.
- Does FaunaDB or Firestore run on more platforms?
- FaunaDB runs on Web. Firestore runs on Web, Ios, Android, Flutter.
- Can I use FaunaDB for free?
- Both have a free tier, so you can try either at no cost before committing.
- What is FaunaDB best used for?
- FaunaDB is most often used for keeping an existing fauna-backed application alive on self-hosted infrastructure while a migration is planned and funded, extracting historical data from a fauna dataset that can no longer be reached through the hosted api, studying a production implementation of deterministic distributed transactions, since the full server source is now readable under apache 2.0, forking the engine deliberately, where an organisation has jvm and distributed-systems staff and wants a document-relational store it fully controls. Of those, keeping an existing fauna-backed application alive on self-hosted infrastructure while a migration is planned and funded and extracting historical data from a fauna dataset that can no longer be reached through the hosted api are not what Firestore is typically brought in for.
- What can FaunaDB do that Firestore cannot?
- FaunaDB covers Document-relational model, FQL v10, Distributed ACID transactions, HTTPS access. Firestore covers Document Model, Real-time Updates, Offline Support, ACID Transactions.
Answered from the vendors’ own pages
FaunaDB: Can I still sign up for Fauna as a service?
No. Fauna Inc. wound down the hosted service in 2025 and the company website is no longer serving. The only way to run Fauna now is to build and operate the open-sourced server yourself.
Firestore: What are the free limits on Cloud Firestore?
The Spark Plan includes 1 GiB of stored data, 50,000 reads per day, 20,000 writes per day, and 20,000 deletes per day at no cost.
SourceFaunaDB: What licence is the open-sourced code under?
Apache 2.0, with the copyright held by a FaunaDB Foundation. That is a permissive OSI licence with no competing-use clause, so you may run it, modify it and even offer it as a service.
Firestore: What happens when I exceed the Spark Plan free tier?
Exceeding the free tier requires upgrading to the Blaze Plan, which bills based on actual usage through Google Cloud pricing. Charges apply for reads, writes, deletes, and data storage.
SourceFaunaDB: Is the open source version the same software that ran the cloud?
It is the core database engine. The control plane, billing, dashboard and multi-tenant operational tooling that made it a service are not part of the release, so you are running the engine, not the product.
Firestore: Can I use Firestore without a credit card?
Yes, you can use the Spark Plan indefinitely without a credit card. To use the Blaze Plan (pay-as-you-go), a credit card is required.
SourceFaunaDB: What should I migrate to?
There is no drop-in target. Teams that valued the document model with relationships usually land on Postgres with JSONB, and teams that valued the serverless HTTP access pattern usually land on DynamoDB or a managed Postgres with an HTTP driver. Either way the query layer is rewritten.
Firestore: Is there a trial period for Cloud Firestore?
No trial period is specified. The Spark Plan free tier serves as the trial, with no time limit.
SourceFaunaDB: How hard is it to self-host?
It builds as a fat JAR and runs as a multi-node JVM cluster. There is an OPERATING.md, but no supported packaging, no operator, no upstream releases and no support contract, so budget for a distributed-systems engineer, not a container.
Related pages
Other head to heads
- FaunaDB vs Amazon Aurora
- FaunaDB vs PostgreSQL
- FaunaDB vs Airtable
- FaunaDB vs Cockroach Labs
- FaunaDB vs BigQuery
- FaunaDB vs CouchDB
- FaunaDB vs CosmosDB
- FaunaDB vs ArangoDB
- FaunaDB vs Dgraph
- FaunaDB vs DynamoDB
- FaunaDB vs Google Cloud SQL
- FaunaDB vs Apache Pinot
- FaunaDB vs Amazon RDS
- FaunaDB vs Apache Pulsar
- FaunaDB vs Cassandra
- FaunaDB vs Amazon Redshift
- FaunaDB vs Couchbase
- FaunaDB vs RavenDB
- FaunaDB vs Estuary
- FaunaDB vs ClickHouse
- FaunaDB vs OpenSearch
- FaunaDB vs Qdrant
- FaunaDB vs SingleStore
- FaunaDB vs TiDB
- FaunaDB vs Tinybird
- FaunaDB vs Typesense
- FaunaDB vs Apache Kafka
- Firestore vs Amazon Aurora
- Firestore vs PostgreSQL
- Firestore vs Airtable
- Firestore vs Cockroach Labs
- Firestore vs BigQuery
- Firestore vs CouchDB
- Firestore vs CosmosDB
- Firestore vs ArangoDB
- Firestore vs Dgraph
- Firestore vs DynamoDB
- Firestore vs Google Cloud SQL
- Firestore vs Apache Pinot
- Firestore vs Amazon RDS
- Firestore vs Apache Pulsar
- Firestore vs Cassandra
- Firestore vs Amazon Redshift
- Firestore vs Couchbase
- Firestore vs RavenDB
- Firestore vs Estuary
- Firestore vs ClickHouse
- Firestore vs OpenSearch
- Firestore vs Qdrant
- Firestore vs SingleStore
- Firestore vs TiDB
- Firestore vs Tinybird
- Firestore vs Typesense
- Firestore vs Apache Kafka
