Databases · head to head
Firestore vs Vitess

Firestore
Databases
Flexible, scalable NoSQL cloud database from Firebase
- From
- Free
- Rated
- -

Vitess
Databases
Scalable database clustering system for horizontal scaling of MySQL
- From
- Free
- Rated
- -
The short version
- Each has a real cost: Firestore the no-cost Spark plan caps Standard edition at 50,000 document reads, 20,000 writes and 20,000 deletes per day; Vitess vTGate scatter queries without sharding key incur significant performance penalties
- They diverge on capability: Firestore covers Document Model, Vitess covers Horizontal Sharding.
- Prices and features above were last checked on 30 August 2026.
Where they differ
Only the attributes on which Firestore and Vitess actually diverge.
Identical on both: starting price (Free), 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 Firestore
- Document Model
- Real-time Updates
- Offline Support
- ACID Transactions
- Expressive Queries
- Multi-region
- Security Rules
- Firebase Auth
Only in Vitess
- Horizontal Sharding
- Connection Pooling
- Query Routing
- Online Schema Changes
- Shard Management
- Replication Management
- Automated Failover
- MySQL
What people use each for
The jobs each tool is most often brought in to do.
Firestore
- Storing structured application data with realtime listenersnot Vitess
- Backing mobile and web apps with a serverless document databasenot Vitess
- Building offline first apps that sync when connectivity returnsnot Vitess
Vitess
- Transaction processingnot Firestore
- Data storagenot Firestore
- Application backendnot Firestore
- Reportingnot Firestore
- Data analyticsnot Firestore
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
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
Vitess
- VTGate scatter queries without sharding key incur significant performance penalties
- Foreign key constraints not enforced across shards, requiring application-level integrity handling
- Single primary per keyspace limits multi-region write capabilities
- Distributed transactions without proper sharding key routing suffer performance degradation
Pricing, plan by plan
Firestore
Free- SparkFree
- 1GB storage
- 50K reads/day
- 20K writes/day
- BlazeFree
- Pay as you go
- Unlimited operations
- Multi-region
Vitess
FreeNo published plan breakdown. See the Vitess review.
Which should you pick?
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.
Choose Vitess if
- You need horizontal sharding.
- You want to start without paying.
- You work on Linux, macOS, Docker, Kubernetes.
- You also want connection pooling.
Questions people ask
- Is Firestore or Vitess better?
- Neither clearly leads. Firestore starts at Free and Vitess at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Firestore or Vitess?
- Firestore starts at Free and Vitess at Free.
- Does Firestore or Vitess run on more platforms?
- Firestore runs on Web, Ios, Android, Flutter. Vitess runs on Linux, macOS, Docker, Kubernetes.
- Can I use Firestore for free?
- Both have a free tier, so you can try either at no cost before committing.
- What is Firestore best used for?
- Firestore is most often used for storing structured application data with realtime listeners, backing mobile and web apps with a serverless document database, building offline first apps that sync when connectivity returns. Of those, storing structured application data with realtime listeners and backing mobile and web apps with a serverless document database are not what Vitess is typically brought in for.
- What can Firestore do that Vitess cannot?
- Firestore covers Document Model, Real-time Updates, Offline Support, ACID Transactions. Vitess covers Horizontal Sharding, Connection Pooling, Query Routing, Online Schema Changes.
Answered from the vendors’ own pages
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.
SourceVitess: Is Vitess free to use?
Yes. Vitess is completely free and open source under the Apache 2.0 license. It is a graduated CNCF project with no licensing costs or pricing tiers.
SourceFirestore: 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.
SourceVitess: What databases does Vitess support?
Vitess supports MySQL and MariaDB as backend databases. It acts as a middleware layer that adds sharding and orchestration capabilities on top of these databases.
SourceFirestore: 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.
SourceVitess: Does Vitess require Kubernetes to run?
No. Vitess can run on Kubernetes using the Vitess Operator, but it can also be deployed on traditional infrastructure. Kubernetes integration is optional and provides additional automation benefits.
SourceFirestore: 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.
SourceVitess: How does Vitess handle cross-shard transactions?
Vitess supports distributed transactions across shards, but they require queries to be routed through the sharding key. Transactions without a proper sharding key can result in slower performance.
SourceVitess: Does Vitess enforce foreign key constraints?
Vitess does not enforce foreign key constraints across shards by default. Referential integrity must be managed at the application layer, though per-database support can be enabled with limitations.
SourceRelated pages
Other head to heads
- Firestore vs PostgreSQL
- Firestore vs Airtable
- Firestore vs Cockroach Labs
- Firestore vs Amazon Aurora
- Firestore vs Couchbase
- Firestore vs CouchDB
- Firestore vs RavenDB
- Firestore vs Estuary
- Firestore vs ArangoDB
- Firestore vs ClickHouse
- Firestore vs OpenSearch
- Firestore vs Qdrant
- Firestore vs SingleStore
- Firestore vs TiDB
- Firestore vs Tinybird
- Firestore vs Typesense
- Firestore vs Apache Pinot
- Firestore vs Apache Kafka
- Firestore vs Readyset
- Firestore vs NATS
- Firestore vs RabbitMQ
- Firestore vs Azure SQL
- Firestore vs MariaDB
- Firestore vs Oracle Database
- Firestore vs IBM Db2
- Firestore vs Instaclustr
- Firestore vs Knack
- Firestore vs LanceDB
- Firestore vs Marqo
- Firestore vs Nile
- Firestore vs Amazon Redshift
- Vitess vs PostgreSQL
- Vitess vs Airtable
- Vitess vs Cockroach Labs
- Vitess vs Amazon Aurora
- Vitess vs Couchbase
- Vitess vs CouchDB
- Vitess vs RavenDB
- Vitess vs Estuary
- Vitess vs ArangoDB
- Vitess vs ClickHouse
- Vitess vs OpenSearch
- Vitess vs Qdrant
- Vitess vs SingleStore
- Vitess vs TiDB
- Vitess vs Tinybird
- Vitess vs Typesense
- Vitess vs Apache Pinot
- Vitess vs Apache Kafka
- Vitess vs Readyset
- Vitess vs NATS
- Vitess vs RabbitMQ
- Vitess vs Azure SQL
- Vitess vs MariaDB
- Vitess vs Oracle Database
- Vitess vs IBM Db2
- Vitess vs Instaclustr
- Vitess vs Knack
- Vitess vs LanceDB
- Vitess vs Marqo
- Vitess vs Nile
- Vitess vs Amazon Redshift
