Softwr

Databases · head to head

Fivetran HVR vs turbopuffer

Fivetran HVR logo

Fivetran HVR

Databases

Log-based change data capture for database replication and synchronization

From
On request
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

  • Each has a real cost: Fivetran HVR pricing not published separately; part of Fivetran's usage model; 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: Fivetran HVR covers Log-based change capture, turbopuffer covers Object storage architecture.
  • Prices and features above were last checked on 30 August 2026.

Where they differ

Only the attributes on which Fivetran HVR and turbopuffer actually diverge.

Attributes where Fivetran HVR and turbopuffer differ
AttributeFivetran HVRturbopuffer
Starting priceOn request$16/month
Pricing modelUsage-based, integrated with Fivetran billingsubscription
PlatformsData Warehouse, Data Lake, Operational DatabasesWeb
Founded2012Unknown

Identical on both: free tier (No), 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 Fivetran HVR

  • Log-based change capture
  • Real-time replication
  • Schema evolution handling
  • Multi-table consistency
  • Zero-impact monitoring
  • Fivetran integration

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.

Fivetran HVR

  • Real-time database replication to data warehousesnot turbopuffer
  • Maintaining operational copies for analyticsnot turbopuffer
  • Disaster recovery and business continuitynot turbopuffer
  • Feeding AI systems with fresh governed datanot turbopuffer

turbopuffer

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

Where each one falls short

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

Fivetran HVR

  • Pricing not published separately; part of Fivetran's usage model
  • Requires Fivetran relationship for implementation
  • Limited standalone documentation and community resources
  • May be overkill for simple batch replication needs
  • Competitive offerings provide more transparent per-connector pricing

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

Fivetran HVR

On request

No published plan breakdown. See the Fivetran HVR 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 Fivetran HVR if

  • You need log-based change capture.
  • You work on Data Warehouse, Data Lake, Operational Databases.
  • You also want real-time replication.
Fivetran HVR review

Choose turbopuffer if

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

Questions people ask

Is Fivetran HVR or turbopuffer better?
Neither clearly leads. Fivetran HVR starts at On request and turbopuffer at $16/month, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Fivetran HVR or turbopuffer?
Fivetran HVR starts at On request and turbopuffer at $16/month.
Does Fivetran HVR or turbopuffer run on more platforms?
Fivetran HVR runs on Data Warehouse, Data Lake, Operational Databases. turbopuffer runs on Web.
What is Fivetran HVR best used for?
Fivetran HVR is most often used for real-time database replication to data warehouses, maintaining operational copies for analytics, disaster recovery and business continuity, feeding ai systems with fresh governed data. Of those, real-time database replication to data warehouses and maintaining operational copies for analytics are not what turbopuffer is typically brought in for.
What can Fivetran HVR do that turbopuffer cannot?
Fivetran HVR covers Log-based change capture, Real-time replication, Schema evolution handling, Multi-table consistency. turbopuffer covers Object storage architecture, Namespaces, Vector search, Full-text search.

Answered from the vendors’ own pages

Fivetran HVR: What databases does Fivetran HVR support?

HVR supports major databases including Oracle, SQL Server, PostgreSQL, MySQL, and others that emit transaction logs.

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.

Fivetran HVR: Is HVR part of standard Fivetran pricing?

Yes, HVR is integrated into Fivetran's usage-based pricing model with standard per-row-synced and transformation costs.

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 Fivetran HVR

More on turbopuffer

Keep looking

Other head to heads