Softwr

Databases · head to head

QuestDB vs turbopuffer

QuestDB logo

QuestDB

Databases

Fast open source time-series database for high throughput ingestion

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 QuestDB has a free tier, so it costs nothing to try first.
  • Each has a real cost: QuestDB open-source edition lacks high-availability, distributed architecture, and enterprise security features; 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: QuestDB covers High Throughput Ingestion, turbopuffer covers Object storage architecture.
  • Prices and features above were last checked on 30 August 2026.

Where they differ

Only the attributes on which QuestDB and turbopuffer actually diverge.

Attributes where QuestDB and turbopuffer differ
AttributeQuestDBturbopuffer
Starting priceFree$16/month
Pricing modelopen-sourcesubscription
Free tierYesNo
PlatformsDocker, Kubernetes, Cloud (AWS, Azure, GCP)Web
Founded2014Unknown

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 QuestDB

  • High Throughput Ingestion
  • SQL Support
  • Time-series Optimization
  • SIMD Vectorization
  • Column-oriented Storage
  • Built-in Web Console
  • InfluxDB Line Protocol
  • PostgreSQL

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.

QuestDB

  • Time-series analytics ingesting up to 20M rows/second from IoT sensors or financial data feedsnot turbopuffer
  • Real-time dashboarding with 32ms time-to-first-row latency for minute-level analyticsnot turbopuffer
  • Applications requiring multi-tier storage (hot ingest, real-time SQL, cold Parquet archive)not turbopuffer

turbopuffer

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

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

QuestDB

  • Open-source edition lacks high-availability, distributed architecture, and enterprise security features
  • Enterprise edition pricing not published; requires contacting sales for custom quote
  • Ingestion limit of 20M rows/sec platform-dependent; may not scale to extreme throughput requirements

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

QuestDB

Free

No published plan breakdown. See the QuestDB review.

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 QuestDB if

  • You need high throughput ingestion.
  • You want to start without paying.
  • You work on Docker, Kubernetes, Cloud (AWS, Azure, GCP).
  • You also want sql support.
QuestDB review

Choose turbopuffer if

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

Questions people ask

Is QuestDB or turbopuffer better?
Neither clearly leads. QuestDB 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, QuestDB or turbopuffer?
QuestDB has a free tier; the other does not. Paid plans start at Free for QuestDB and $16/month for turbopuffer.
Does QuestDB or turbopuffer run on more platforms?
QuestDB runs on Docker, Kubernetes, Cloud (AWS, Azure, GCP). turbopuffer runs on Web.
Can I use QuestDB for free?
Yes. QuestDB has a free tier, so you can try it without paying. turbopuffer starts at $16/month.
What is QuestDB best used for?
QuestDB is most often used for time-series analytics ingesting up to 20m rows/second from iot sensors or financial data feeds, real-time dashboarding with 32ms time-to-first-row latency for minute-level analytics, applications requiring multi-tier storage (hot ingest, real-time sql, cold parquet archive). Of those, time-series analytics ingesting up to 20m rows/second from iot sensors or financial data feeds and real-time dashboarding with 32ms time-to-first-row latency for minute-level analytics are not what turbopuffer is typically brought in for.
What can QuestDB do that turbopuffer cannot?
QuestDB covers High Throughput Ingestion, SQL Support, Time-series Optimization, SIMD Vectorization. turbopuffer covers Object storage architecture, Namespaces, Vector search, Full-text search.

Answered from the vendors’ own pages

QuestDB: How much does QuestDB Enterprise cost?

QuestDB does not publish specific pricing for the Enterprise tier. Customers must contact QuestDB via their enterprise contact form to receive a custom quote.

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.

QuestDB: Does QuestDB offer a free version?

Yes, QuestDB Open Source is completely free and recommended for evaluation, prototyping, and pilot projects. Enterprise features, high availability, security, and dedicated support require the paid Enterprise tier.

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.

QuestDB: What deployment options does QuestDB offer?

QuestDB offers open source deployment, Enterprise deployment, and Bring Your Own Cloud (BYOC) deployment. Pricing details for BYOC and Enterprise tiers are not published and require direct contact with sales.

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.

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 QuestDB

More on turbopuffer

Keep looking

Other head to heads