Softwr

Databases · head to head

Fivetran HVR vs Immuta

Fivetran HVR logo

Fivetran HVR

Databases

Log-based change data capture for database replication and synchronization

From
On request
Rated
-
Full reviewWebsite
Immuta logo

Immuta

Databases

Attribute-based access control and masking applied inside Snowflake, Databricks and BigQuery

From
On request
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: Fivetran HVR pricing not published separately; part of Fivetran's usage model; Immuta contracts commonly start around one hundred to two hundred thousand US dollars a year for mid-market deployments and exceed five hundred thousand at enterprise scale, which excludes most data teams without a regulatory mandate.
  • They diverge on capability: Fivetran HVR covers Log-based change capture, Immuta covers Attribute-based policy.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

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

Attributes where Fivetran HVR and Immuta differ
AttributeFivetran HVRImmuta
Pricing modelUsage-based, integrated with Fivetran billingquote
PlatformsData Warehouse, Data Lake, Operational DatabasesWeb, API, Cloud
Founded2012Unknown

Identical on both: starting price (On request), 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 Immuta

  • Attribute-based policy
  • Native enforcement
  • Dynamic masking
  • Row-level filtering
  • Purpose-based access
  • Sensitive data tagging
  • Audit logging
  • Multi-platform

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 Immuta
  • Maintaining operational copies for analyticsnot Immuta
  • Disaster recovery and business continuitynot Immuta
  • Feeding AI systems with fresh governed datanot Immuta

Immuta

  • A bank whose Snowflake estate has grown to tens of thousands of roles that no one can review before an auditnot Fivetran HVR
  • A healthcare analytics team that must let researchers query patient data with identifiers masked unless a specific purpose is recordednot Fivetran HVR
  • A multinational applying different residency and access rules per jurisdiction to the same tables without duplicating datasetsnot Fivetran HVR
  • An organisation running both Snowflake and Databricks that wants one policy set rather than two divergent implementationsnot 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

Immuta

  • Contracts commonly start around one hundred to two hundred thousand US dollars a year for mid-market deployments and exceed five hundred thousand at enterprise scale, which excludes most data teams without a regulatory mandate.
  • Policy is only as good as the data classification underneath it, so an organisation with poorly tagged columns will spend months on classification before Immuta enforces anything useful.
  • Native enforcement means capability varies by platform, and a feature available on Snowflake may be absent or behave differently on BigQuery, which undermines the promise of one policy set everywhere.
  • Adding an access governance layer creates a new dependency in the path to data: a misconfigured policy silently returns fewer rows rather than erroring, and analysts can act on incomplete results without noticing.
  • It governs cloud data platforms, so personal data in operational databases, files and SaaS applications sits outside its scope and needs separate controls, meaning Immuta is rarely the whole answer.

Pricing, plan by plan

Fivetran HVR

On request

No published plan breakdown. See the Fivetran HVR review.

Immuta

On request
  • Immuta Platform$undefined/year
    • Attribute-based policy authoring
    • Native enforcement in supported data platforms
    • Dynamic masking and row-level security

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

  • You need attribute-based policy.
  • You work on Web, API, Cloud.
  • You also want native enforcement.
Immuta review

Questions people ask

Is Fivetran HVR or Immuta better?
Neither clearly leads. Fivetran HVR starts at On request and Immuta at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Fivetran HVR or Immuta?
Fivetran HVR starts at On request and Immuta at On request.
Does Fivetran HVR or Immuta run on more platforms?
Fivetran HVR runs on Data Warehouse, Data Lake, Operational Databases. Immuta runs on Web, API, Cloud.
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 Immuta is typically brought in for.
What can Fivetran HVR do that Immuta cannot?
Fivetran HVR covers Log-based change capture, Real-time replication, Schema evolution handling, Multi-table consistency. Immuta covers Attribute-based policy, Native enforcement, Dynamic masking, Row-level filtering.

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
Immuta: Does Immuta sit in the query path?

No. It compiles policies into the data platform's own native controls, so queries run at normal speed through your existing tools.

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
Immuta: What does it cost?

Not published. Market data suggests roughly 100,000 to 200,000 US dollars a year for mid-market deployments and considerably more at enterprise scale.

Immuta: Is Immuta still independent?

Yes. It remains independently owned, unlike several competitors in data access governance that have been acquired.

Immuta: Does it work across more than one warehouse?

Yes, one policy set can target Snowflake, Databricks, BigQuery and Starburst, though enforcement capability varies by platform.

Share

Related pages

More on Fivetran HVR

More on Immuta

Keep looking

Other head to heads