Softwr

Databases · head to head

Firestore vs turbopuffer

Firestore logo

Firestore

Databases

Flexible, scalable NoSQL cloud database from Firebase

From
Free
Rated
-
Full reviewWebsite
turbopuffer logo

turbopuffer

Databases

Closed-source vector and full-text search service built directly on object storage, with cold queries measured in seconds rather than milliseconds.

From
$16/month
Rated
-
Full reviewWebsite

The short version

  • Only Firestore has a free tier, so it costs nothing to try first.
  • 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; turbopuffer a cold namespace pays object storage latency on the first query, with a documented p90 around 1,214 ms on a million documents, so any interactive search box needs the data kept warm or the user waits about a second.
  • They diverge on capability: Firestore covers Document Model, turbopuffer covers Object storage architecture.
  • Prices and features above were last checked on 30 August 2026.

Where they differ

Only the attributes on which Firestore and turbopuffer actually diverge.

Attributes where Firestore and turbopuffer differ
AttributeFirestoreturbopuffer
Starting priceFree$16/month
Pricing modelfreemiumsubscription
Free tierYesNo
PlatformsWeb, Ios, Android, FlutterWeb
Founded2011Unknown

Identical on both: 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 turbopuffer

  • Object storage architecture
  • Namespaces
  • Vector search
  • Full-text search
  • Attribute filtering
  • Documented limits
  • Configurable consistency
  • Durable writes

What people use each for

The jobs each tool is most often brought in to do.

Firestore

  • Storing structured application data with realtime listenersnot turbopuffer
  • Backing mobile and web apps with a serverless document databasenot turbopuffer
  • Building offline first apps that sync when connectivity returnsnot turbopuffer

turbopuffer

  • A product with one search index per customer and thousands of customers, most of whose data is idle on any given daynot Firestore
  • Very large corpora where holding every vector in memory is the dominant cost and occasional cold-query latency is acceptablenot Firestore
  • Hybrid retrieval combining BM25 and vector search where running and synchronising two separate systems is the problem being solvednot Firestore
  • Retrieval for agent and assistant products where indexes are created and destroyed frequently and per-index overhead must be near zeronot 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

turbopuffer

  • A cold namespace pays object storage latency on the first query, with a documented p90 around 1,214 ms on a million documents, so any interactive search box needs the data kept warm or the user waits about a second.
  • Queries are eventually consistent by default, and after roughly 128 MiB of outstanding writes new data is invisible until indexed, which the vendor puts at tens of seconds for small namespaces and tens of minutes for large ones, so a bulk re-index is not immediately queryable.
  • It is closed source with no community edition, so single-tenant or bring-your-own-cloud deployment is a commercial negotiation rather than a deployment choice, and there is no path to running it yourself if the relationship ends.
  • Per-namespace ceilings, roughly 10,000 writes per second, 32 MB/s and 500 million documents per shard, mean a single enormous index has to be sharded across namespaces by your application rather than by the service.
  • It is a search engine, not a database: there are no joins, no cross-document transactions and no SQL, so it sits beside a primary datastore and keeping the two in step is work that belongs to you.

Pricing, plan by plan

Firestore

Free
  • SparkFree
    • 1GB storage
    • 50K reads/day
    • 20K writes/day
  • BlazeFree
    • Pay as you go
    • Unlimited operations
    • Multi-region

turbopuffer

$16/month
  • Launch$16/month
    • All database features
    • Multi-tenancy deployment
    • SOC2 & GDPR-ready DPA
  • Scale$256/month
    • Everything in Launch
    • HIPAA-ready BAA
    • Single Sign-On (SSO)
  • Enterprise$4096/month
    • Everything in Scale
    • Single-tenancy & BYOC deployment options
    • Private networking

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.
Firestore review

Choose turbopuffer if

  • You need object storage architecture.
  • You also want namespaces.
turbopuffer review

Questions people ask

Is Firestore or turbopuffer better?
Neither clearly leads. Firestore starts at Free and turbopuffer at $16/month, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Firestore or turbopuffer?
Firestore has a free tier; the other does not. Paid plans start at Free for Firestore and $16/month for turbopuffer.
Does Firestore or turbopuffer run on more platforms?
Firestore runs on Web, Ios, Android, Flutter. turbopuffer runs on Web.
Can I use Firestore for free?
Yes. Firestore has a free tier, so you can try it without paying. turbopuffer starts at $16/month.
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 turbopuffer is typically brought in for.
What can Firestore do that turbopuffer cannot?
Firestore covers Document Model, Real-time Updates, Offline Support, ACID Transactions. turbopuffer covers Object storage architecture, Namespaces, Vector search, Full-text search.

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.

Source
turbopuffer: Can I self-host turbopuffer?

There is no open source or community edition. Single-tenant and bring-your-own-cloud deployments exist as commercial arrangements, but there is no way to run it independently of the vendor.

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.

Source
turbopuffer: How fast is it really?

Warm queries perform comparably to in-memory search engines. Cold queries, where data is not cached, have a documented p90 around 1,214 ms on a million documents. Write p90 is around 248 ms for a 512 KB upsert because writes go straight to object storage.

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.

Source
turbopuffer: Is it consistent?

Eventually consistent by default, with the vendor reporting that over 99.8% of queries return consistent data. Strong consistency can be requested per query at a latency cost. Large write bursts have a longer visibility delay while indexing catches up.

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.

Source
turbopuffer: What is it best at?

Large numbers of namespaces where most are idle. The architecture makes cold data cheap to keep, which is exactly the shape of a multi-tenant product with a long tail of inactive customers.

turbopuffer: What are the hard limits?

Up to 128 billion documents and 256 TB per namespace, 500 million documents per shard, 64 MiB per document, 10,752 dense vector dimensions, roughly 10,000 writes per second per namespace and a maximum result set of 10,000.

Share

Related pages

More on Firestore

More on turbopuffer

Keep looking

Other head to heads