Softwr

Databases · head to head

Estuary vs turbopuffer

Estuary logo

Estuary

Databases

Real-time data integration combining streaming, CDC, and batch

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 Estuary has a free tier, so it costs nothing to try first.
  • Each has a real cost: Estuary per-GB pricing adds up quickly for high-volume scenarios; 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: Estuary covers Real-time data delivery, turbopuffer covers Object storage architecture.
  • Prices and features above were last checked on 30 August 2026.

Where they differ

Only the attributes on which Estuary and turbopuffer actually diverge.

Attributes where Estuary and turbopuffer differ
AttributeEstuaryturbopuffer
Starting priceFree$16/month
Pricing modelUsage-based per GB plus per-connector costsubscription
Free tierYesNo
PlatformsCloud, Private Cloud, BYOCWeb
Founded2019Unknown

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 Estuary

  • Real-time data delivery
  • Change data capture
  • Batch processing
  • Data transformation
  • Pre-built connectors
  • Multiple deployments
  • RBAC and monitoring

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.

Estuary

  • Real-time data replication to data warehousesnot turbopuffer
  • Change data capture from operational databasesnot turbopuffer
  • Feeding analytics and BI systems with fresh datanot turbopuffer
  • Powering real-time AI and ML data pipelinesnot turbopuffer

turbopuffer

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

Where each one falls short

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

Estuary

  • Per-GB pricing adds up quickly for high-volume scenarios
  • No transparent per-connector volume discounts below 6 connectors
  • Limited to data movement; transformation capabilities are basic
  • BYOC and private deployment requires enterprise plan
  • Smaller ecosystem compared to established alternatives

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

Estuary

Free
  • DeveloperFree
    • 10 GB per month
    • 2 connector instances maximum
    • No credit card required
  • Cloud$0.5/GB
    • $0.50 per GB of data moved
    • $100 per connector monthly (6+ connectors $50 each)
    • 200+ connectors
  • Enterprise$null/custom
    • Volume-based discounts
    • SOC 2 and HIPAA compliance
    • SSO authentication

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

  • You need real-time data delivery.
  • You want to start without paying.
  • You work on Cloud, Private Cloud, BYOC.
  • You also want change data capture.
Estuary review

Choose turbopuffer if

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

Questions people ask

Is Estuary or turbopuffer better?
Neither clearly leads. Estuary 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, Estuary or turbopuffer?
Estuary has a free tier; the other does not. Paid plans start at Free for Estuary and $16/month for turbopuffer.
Does Estuary or turbopuffer run on more platforms?
Estuary runs on Cloud, Private Cloud, BYOC. turbopuffer runs on Web.
Can I use Estuary for free?
Yes. Estuary has a free tier, so you can try it without paying. turbopuffer starts at $16/month.
What is Estuary best used for?
Estuary is most often used for real-time data replication to data warehouses, change data capture from operational databases, feeding analytics and bi systems with fresh data, powering real-time ai and ml data pipelines. Of those, real-time data replication to data warehouses and change data capture from operational databases are not what turbopuffer is typically brought in for.
What can Estuary do that turbopuffer cannot?
Estuary covers Real-time data delivery, Change data capture, Batch processing, Data transformation. turbopuffer covers Object storage architecture, Namespaces, Vector search, Full-text search.

Answered from the vendors’ own pages

Estuary: What is included in the free Developer plan?

Developer plan ($0/month) includes 10 GB of data per month and up to 2 connector instances, no credit card required.

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.

Estuary: How is data pricing calculated on Cloud plan?

Cloud plan charges $0.50 per GB of data moved plus $100/month per connector for the first 6 connectors, then $50/month for additional connectors.

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.

Estuary: What discount is available when adding 6+ connectors?

When using 6 or more connectors, the per-connector cost drops to $50/month from $100/month, saving $50 per additional connector.

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 Estuary

More on turbopuffer

Keep looking

Other head to heads