Softwr

Databases · head to head

Dremio vs turbopuffer

Dremio logo

Dremio

Databases

SQL query engine and lakehouse layer over Iceberg tables in object storage

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 Dremio has a free tier, so it costs nothing to try first.
  • Each has a real cost: Dremio reflections consume compute and storage to build and refresh continuously, so a team that enables them widely discovers that background maintenance rather than user queries drives the DCU bill.; 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: Dremio covers Arrow-based execution, turbopuffer covers Object storage architecture.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Dremio and turbopuffer actually diverge.

Attributes where Dremio and turbopuffer differ
AttributeDremioturbopuffer
Starting priceFree$16/month
Pricing modelPer Dremio Compute Unit consumedsubscription
Free tierYesNo
PlatformsLinux, Kubernetes, Cloud, DockerWeb

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 Dremio

  • Arrow-based execution
  • Reflections
  • Semantic layer
  • Iceberg catalogue
  • Federated queries
  • Autonomous management
  • Fine-grained access control
  • BI connectors

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.

Dremio

  • A company with petabytes of Parquet in S3 that wants BI dashboards without duplicating it into a warehousenot turbopuffer
  • A data platform team standardising on Apache Iceberg and needing a SQL engine plus catalogue that does not lock the tables innot turbopuffer
  • An analytics group accelerating slow lake queries with Reflections instead of hand-built aggregate tablesnot turbopuffer
  • A regulated enterprise that must keep data on premises but wants a modern lakehouse SQL layernot turbopuffer

turbopuffer

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

Where each one falls short

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

Dremio

  • Reflections consume compute and storage to build and refresh continuously, so a team that enables them widely discovers that background maintenance rather than user queries drives the DCU bill.
  • Self-managing Dremio on Kubernetes requires real platform engineering capacity for tuning executors, memory and coordinator sizing, and it is not comparable in effort to running a managed warehouse.
  • The Community Edition lacks the security and governance features most enterprises require, so the free tier is a trial path rather than a viable production option for regulated buyers.
  • Dremio Cloud is AWS-first, which leaves Azure and Google Cloud customers on the self-managed path with the operational burden that entails.
  • Query performance without Reflections on raw, poorly laid out files is often unremarkable, so the promise of querying the lake as is depends on file layout work you still have to do.

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

Dremio

Free
  • Community EditionFree
    • Self-managed on your own hardware
    • SQL engine and semantic layer
    • No vendor support
  • Dremio Cloud$0.2/hour
    • Billed at $0.20 per Dremio Compute Unit
    • Includes query execution, Reflections and background processing
    • 400 dollar trial credit for 30 days
  • Enterprise$undefined/year
    • Self-managed on Kubernetes, on premises or any cloud
    • Enterprise security, SSO and governance
    • Vendor support with SLA

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

  • You need arrow-based execution.
  • You want to start without paying.
  • You work on Linux, Kubernetes, Cloud, Docker.
  • You also want reflections.
Dremio review

Choose turbopuffer if

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

Questions people ask

Is Dremio or turbopuffer better?
Neither clearly leads. Dremio 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, Dremio or turbopuffer?
Dremio has a free tier; the other does not. Paid plans start at Free for Dremio and $16/month for turbopuffer.
Does Dremio or turbopuffer run on more platforms?
Dremio runs on Linux, Kubernetes, Cloud, Docker. turbopuffer runs on Web.
Can I use Dremio for free?
Yes. Dremio has a free tier, so you can try it without paying. turbopuffer starts at $16/month.
What is Dremio best used for?
Dremio is most often used for a company with petabytes of parquet in s3 that wants bi dashboards without duplicating it into a warehouse, a data platform team standardising on apache iceberg and needing a sql engine plus catalogue that does not lock the tables in, an analytics group accelerating slow lake queries with reflections instead of hand-built aggregate tables, a regulated enterprise that must keep data on premises but wants a modern lakehouse sql layer. Of those, a company with petabytes of parquet in s3 that wants bi dashboards without duplicating it into a warehouse and a data platform team standardising on apache iceberg and needing a sql engine plus catalogue that does not lock the tables in are not what turbopuffer is typically brought in for.
What can Dremio do that turbopuffer cannot?
Dremio covers Arrow-based execution, Reflections, Semantic layer, Iceberg catalogue. turbopuffer covers Object storage architecture, Namespaces, Vector search, Full-text search.

Answered from the vendors’ own pages

Dremio: How is Dremio Cloud billed?

At 0.20 US dollars per Dremio Compute Unit, which counts query execution, Reflection building and platform overhead, not just user queries.

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.

Dremio: Is there a free version?

Yes, a Community Edition you self-manage, but it omits the enterprise security and governance features and comes with no support.

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.

Dremio: Does it lock in my data?

No, tables stay in Apache Iceberg or Parquet in your own object storage and can be read by Spark, Trino or other engines.

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.

Dremio: Do I still need a warehouse?

Often not for analytics, but Dremio is not a transactional store and high-concurrency operational serving is not its strength.

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 Dremio

More on turbopuffer

Keep looking

Other head to heads