Fivetran HVR and Fivetran Hybrid Deployment are the parts of the Fivetran platform that run as downloaded software in the customer’s own environment. HVR is a self-hosted database replication product that Fivetran now sells on its consumption model. Hybrid Deployment lets a local agent process data inside the customer’s network while Fivetran runs the control plane. Under the Master Subscription Agreement both are “On-Prem Software”, a downloadable component installed on premise or in the customer’s private cloud.[6]
The On-Prem Software licence
The MSA grants, for the subscription term of an Order Form, a “limited, non-exclusive, non-transferable” licence to install, integrate and use On-Prem Software for internal business purposes on the Source and Target Systems named in the Order Form.[6] Those systems are defined as the permitted type and number of computer hardware systems, storage platforms and computer frameworks.[6] Customers must not redistribute, sublicense or allow third parties, other than contractors who are Users, to use On-Prem Software.[9]
For metering, if a customer’s system configuration stops Fivetran from determining the monthly amounts owed, Fivetran may ask for a monthly report with a breakdown of Users, data sources and destinations, separating internal use from Powered by Fivetran use.[6] The MSA does not set out an audit clause for On-Prem Software in the text reviewed. Compliance is therefore driven by the usage data that the software sends.
Fivetran HVR
Consumption model and plan
Fivetran prices HVR on the same Monthly Active Rows measure as the SaaS service. It calculates consumption from the MAR across all source and target locations of each HVR Hub System, where MAR is the number of distinct primary keys synced from a source location to a target location in a month.[1] Rules in the HVR documentation include:
- multiple hub systems can be registered to one Fivetran account;
- when one source feeds several destinations, MAR is counted for each destination;
- MAR is calculated the same way for cloud and on-premise connections, in UTC;
- one budget can be shared between Fivetran and HVR.[1]
Fivetran offers a single plan for HVR, Business Critical, in which it manages consumption tracking and licence renewal.[1] The older Private Deployment plan and usage-based subscription licensing model were deprecated on 1 March 2025, and Private Deployment accounts must move to Business Critical or another available plan when their contract renews.[2] The Business Critical plan also gives full access to HVR, including change data capture, compare and repair, and a REST API, according to the Marketplace Terms plan description.[11]
Registration and the licence key
A customer must register each HVR hub with Fivetran. Fivetran then provides a generic licence key, not tied to one hub, that permits use as specified in the Order Form.[3] Under consumption licensing the key is valid for seven days and renews automatically each day, so a hub registered on 10 March has an expiry of 17 March that becomes 18 March the next day.[2] If the registration is deleted from a hub, HVR stops sending consumption data and the automatic renewal stops, so the licence expires after seven days.[1]
Operationally the hub needs outbound access to Fivetran addresses on port 443 and a browser path to fivetran.com for registration.[1] HVR sends a MAR data file hourly and a hub snapshot every 30 days. The MAR file holds hub and location names, table names, hashes of changed primary keys and HyperLogLog records, and the snapshot holds a week of events and statistics, channel definitions and job state, but not replicated table content.[1]
HVR connections, trial and troubleshooting window
An HVR connection is defined by the combination of registration ID, hub ID, source location name, target location name and channel name. Each new connection with the same hub ID, source and target location names starts a 14-day free trial.[1] Table refreshes get a 5-day troubleshooting window from the first refresh of a table in a month, after which refreshes count as paid MAR. Where enhanced re-sync detection is enabled (HVR 6.2.0/13 and later) the window is not required.[1]
Security and support
For HVR the SaaS security and data processing provisions of the MSA do not apply, and the customer is responsible for the security of its environment.[3] The Support Policy has additional HVR terms: a Minor Version is supported for three years from General Availability, patch releases do not extend that period, and two further years of Extended Support can be bought for the final Minor Version of each Major Version. Customers agree to install Updates within 60 days, and Fivetran gives twelve months’ notice if it discontinues a Major or Minor Version.[7] Initial response targets for HVR customers are in the same table as Enterprise and Business Critical: one hour for Severity 1.[7]
Hybrid Deployment
Architecture
Under Hybrid Deployment a Hybrid Deployment Agent hosted on the customer’s infrastructure keeps contact with Fivetran’s managed SaaS control plane and runs the sync locally. The customer owns and manages temporary storage buckets, and the agent sends only metadata, including sync metrics, MAR information and logs, to the Fivetran cloud.[5] Hybrid Deployment is supported for a subset of connectors and destinations, marked with a hybrid-capable icon in the dashboard.[5]
Deployment limits
Docker and Podman hosts may run only one agent each. In Kubernetes several agents may share a cluster if each runs in its own namespace, one agent per namespace.[5] These are product requirements, not price metrics: there is no per-agent fee in the documents reviewed, and usage is billed as MAR under the plan.
Plan eligibility and terms
Only Enterprise and Business Critical offer Hybrid Deployment.[8] The Requirements for Hybrid Deployment treat the downloaded components as On-Prem Software and the Fivetran Cloud Platform as a SaaS Product. The customer is responsible for the security of its systems. Fivetran bears no security or data processing obligations for the On-Prem Software processing data in the customer’s environment, and is not liable if the customer’s systems do not meet the documented minimum technical requirements.[4]
The agent downloads updates automatically; the customer must not configure it to prevent that and must install any manual update within 60 days of release. If it does not, Fivetran is not obliged to give support under the Support Policy until the update is applied.[4] Updates to the Requirements take effect on renewal or a new Order Form enabling Hybrid Deployment, though Fivetran may apply some changes during the term, for example to comply with laws or for new features.[4] The SLA covers Hybrid Deployment’s web application and API as Core Services, while data delivery guarantees apply unless failures come from the customer’s replication servers.[10]
Software asset management points
- Inventory every HVR hub and every Hybrid Deployment agent, and tie each to an Order Form with the permitted Source and Target Systems.
- Keep the hub registration alive, because a deleted registration lets the licence lapse within seven days.
- Track update deadlines (60 days for HVR and Hybrid Deployment) and HVR version lifecycles (3 years plus optional 2).
- Count MAR per destination for HVR, which can multiply usage when one source feeds several targets.
- Treat a Standard plan customer who adopts Oracle, SAP or HVA connectors, or Hybrid Deployment, as a candidate for an Enterprise plan uplift at renewal.[8]
Out of scope
The supported connector and destination lists for Hybrid Deployment, HVR installation and high-availability documentation and negotiated On-Prem Software addenda are not covered.