Databases · head to head
Firestore vs Valkey

Firestore
Databases
Flexible, scalable NoSQL cloud database from Firebase
- 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; Valkey younger project, so its track record is short even though the codebase is not
- They diverge on capability: Firestore covers Document Model, Valkey covers Redis-compatible.
- Prices and features above were last checked on 30 August 2026.
Where they differ
Only the attributes on which Firestore and Valkey 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 Valkey
- Redis-compatible
- BSD licensed
- Rich data structures
- Replication and persistence
What people use each for
The jobs each tool is most often brought in to do.
Firestore
- Storing structured application data with realtime listenersnot Valkey
- Backing mobile and web apps with a serverless document databasenot Valkey
- Building offline first apps that sync when connectivity returnsnot Valkey
Valkey
- Continuing on a permissively licensed in-memory store after the Redis licence changenot Firestore
- Caching and session storage where a foundation-governed project is a procurement requirementnot Firestore
- Migrating from Redis without rewriting application codenot 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
Valkey
- Younger project, so its track record is short even though the codebase is not
- Divergence from Redis grows over time, so compatibility is strongest near the fork point and weakens as both evolve
- Ecosystem tooling and documentation still frequently assume Redis, leaving translation work
Pricing, plan by plan
Firestore
Free- SparkFree
- 1GB storage
- 50K reads/day
- 20K writes/day
- BlazeFree
- Pay as you go
- Unlimited operations
- Multi-region
Valkey
Free- ValkeyFree
- Full functionality
- Self-hosted
- No usage limits
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 Valkey if
- You need redis-compatible.
- You want to start without paying.
- You work on Linux, macOS, Docker, Self-hosted.
- You also want bsd licensed.
Questions people ask
- Is Firestore or Valkey better?
- Neither clearly leads. Firestore starts at Free and Valkey at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Firestore or Valkey?
- Firestore starts at Free and Valkey at Free.
- Does Firestore or Valkey run on more platforms?
- Firestore runs on Web, Ios, Android, Flutter. Valkey runs on Linux, macOS, Docker, Self-hosted.
- 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 Valkey is typically brought in for.
- What can Firestore do that Valkey cannot?
- Firestore covers Document Model, Real-time Updates, Offline Support, ACID Transactions. Valkey covers Redis-compatible, BSD licensed, Rich data structures, Replication and persistence.
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.
SourceValkey: Is Valkey free?
Yes, BSD-licensed open source under the Linux Foundation.
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.
SourceValkey: Why does Valkey exist?
Redis changed its licence away from BSD in 2024. Valkey is the community fork continuing under permissive terms, backed by AWS, Google Cloud and Oracle among others.
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.
SourceValkey: Can I switch from Redis to Valkey?
At the fork point it is drop-in compatible with existing clients and data. The further both projects move from that point, the more you should verify the specific features you use.
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.
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 Dragonfly
- Firestore vs Memcached
- Firestore vs MariaDB
- Firestore vs Aiven
- Firestore vs Redpanda
- Firestore vs Timeplus
- Firestore vs RabbitMQ
- Firestore vs Meilisearch
- Firestore vs NATS
- Firestore vs DataGrip
- Firestore vs Apache Airflow
- Firestore vs Apache Pulsar
- Firestore vs Cassandra
- Valkey vs PostgreSQL
- Valkey vs Airtable
- Valkey vs Cockroach Labs
- Valkey vs Amazon Aurora
- Valkey vs Couchbase
- Valkey vs CouchDB
- Valkey vs RavenDB
- Valkey vs Estuary
- Valkey vs ArangoDB
- Valkey vs ClickHouse
- Valkey vs OpenSearch
- Valkey vs Qdrant
- Valkey vs SingleStore
- Valkey vs TiDB
- Valkey vs Tinybird
- Valkey vs Typesense
- Valkey vs Apache Pinot
- Valkey vs Apache Kafka
- Valkey vs Dragonfly
- Valkey vs Memcached
- Valkey vs MariaDB
- Valkey vs Aiven
- Valkey vs Redpanda
- Valkey vs Timeplus
- Valkey vs RabbitMQ
- Valkey vs Meilisearch
- Valkey vs NATS
- Valkey vs DataGrip
- Valkey vs Apache Airflow
- Valkey vs Apache Pulsar
- Valkey vs Cassandra

