Softwr

Databases · head to head

Dragonfly vs turbopuffer

Dragonfly logo

Dragonfly

Databases

High-performance Redis-compatible in-memory datastore with 25x better throughput

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 Dragonfly has a free tier, so it costs nothing to try first.
  • Each has a real cost: Dragonfly flex tier starting at $36/month may be underpriced, requiring careful usage monitoring; 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: Dragonfly covers Redis API compatibility, turbopuffer covers Object storage architecture.
  • Prices and features above were last checked on 30 August 2026.

Where they differ

Only the attributes on which Dragonfly and turbopuffer actually diverge.

Attributes where Dragonfly and turbopuffer differ
AttributeDragonflyturbopuffer
Starting priceFree$16/month
Pricing modelUsage-based cloud pricing with flexible tierssubscription
Free tierYesNo
PlatformsCloud, AWS, GCP, AzureWeb

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 Dragonfly

  • Redis API compatibility
  • Thread-per-core architecture
  • High-performance caching
  • Memory efficiency
  • Real-time leaderboards
  • Message queue support
  • ML feature serving
  • Cloud deployment

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.

Dragonfly

  • High-throughput caching for web applicationsnot turbopuffer
  • Real-time leaderboards and rankingsnot turbopuffer
  • Message queue and event processingnot turbopuffer
  • ML model feature serving at millisecond latenciesnot turbopuffer
  • Gaming session state and player data storagenot turbopuffer

turbopuffer

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

Where each one falls short

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

Dragonfly

  • Flex tier starting at $36/month may be underpriced, requiring careful usage monitoring
  • Business tier $2,000/month represents significant jump in cost
  • Limited to in-memory storage, not suitable for cold data or archival
  • Bring-your-own-cloud requirement on Business tier adds operational complexity
  • Cloud availability dependent on AWS/GCP/Azure uptime

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

Dragonfly

Free
  • Free TierFree
    • 100 cloud credits for new signups
    • Equivalent to free trial
  • Business$2000/month
    • Starting price for enterprise offering
    • Bring-your-own-cloud deployment
    • Auto-scaling with custom SLAs
  • Enterprise$undefined/custom
    • Custom pricing
    • Any-cloud deployment
    • Custom instances and sizing

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

  • You need redis api compatibility.
  • You want to start without paying.
  • You work on Cloud, AWS, GCP, Azure.
  • You also want thread-per-core architecture.
Dragonfly review

Choose turbopuffer if

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

Questions people ask

Is Dragonfly or turbopuffer better?
Neither clearly leads. Dragonfly 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, Dragonfly or turbopuffer?
Dragonfly has a free tier; the other does not. Paid plans start at Free for Dragonfly and $16/month for turbopuffer.
Does Dragonfly or turbopuffer run on more platforms?
Dragonfly runs on Cloud, AWS, GCP, Azure. turbopuffer runs on Web.
Can I use Dragonfly for free?
Yes. Dragonfly has a free tier, so you can try it without paying. turbopuffer starts at $16/month.
What is Dragonfly best used for?
Dragonfly is most often used for high-throughput caching for web applications, real-time leaderboards and rankings, message queue and event processing, ml model feature serving at millisecond latencies. Of those, high-throughput caching for web applications and real-time leaderboards and rankings are not what turbopuffer is typically brought in for.
What can Dragonfly do that turbopuffer cannot?
Dragonfly covers Redis API compatibility, Thread-per-core architecture, High-performance caching, Memory efficiency. turbopuffer covers Object storage architecture, Namespaces, Vector search, Full-text search.

Answered from the vendors’ own pages

Dragonfly: How much faster is Dragonfly than Redis?

Dragonfly achieves 3.97M queries per second compared to Redis's 718K QPS, representing a 25x improvement. Memory efficiency is also 30% better.

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.

Dragonfly: Can I migrate from Redis to Dragonfly without code changes?

Yes. Dragonfly maintains full API compatibility with Redis and Memcached, allowing drop-in replacement with minimal to no code modifications.

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.

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 Dragonfly

More on turbopuffer

Keep looking

Other head to heads