Pricing Plans
This section briefly describes the pricing plans for Fivetran HVR and explains the most recent pricing updates.
Our pricing model is based on consumption (usage). You are charged based on how much data is replicated or consumed by a target/destination. For more information, see our pricing documentation.
Fivetran calculates your consumption (usage) based on the number of Monthly Active Rows (MAR) across all source and target locations within your HVR Hub System(s). MAR is the number of distinct primary keys synced/replicated from a source location to a target location in a given calendar month.
Fivetran offers the Business Critical pricing plan for HVR. In the Business Critical plan, Fivetran automatically handles the consumption tracking and license renewal.
Pricing Plan Updates
Fivetran has made the following pricing updates:
- We've introduced an enhanced re-sync detection mechanism. The new mechanism more precisely determines changes in data. This eliminates the need for restricting free refreshes within the 5-day troubleshooting window because we charge you only for changed rows, whenever the change occurs.
- We've moved away from account-level tiering to channel-level usage tiers. The cost of HVR per monthly active row decreases for a single channel as your usage grows for that particular channel. Previously, usage was calculated on an account level.
- We've deprecated the Private Deployment pricing plan. All HVR accounts on the Private Deployment plan must transition to the Business Critical or other plans upon contract renewal.
- We introduced discounts for annual contracts based on commitment levels. Once you have upgraded your HVR Hub and Agent to version 6.2.0/14 or newer and we have one month of usage data, see the Pricing Estimator for an estimate of your annual discount. The discount applies once you renew your contract.
As of April 24, 2025, you can transition to the updated pricing by completing the following two actions:
- Renew your annual contract
- Upgrade your HVR Hub and Agent to version 6.2.0/14 or newer (or on 6.1.0, 6.1.0/76+ or on 6.2.5, 6.2.5/5+)
You must complete both actions to get the benefit of re-sync detection.
Re-sync detection is not available for HVR when using SAP HANA as the Source.
Improved Re-sync Detection
To enable support for enhanced re-sync detection on your account, you need to upgrade your HVR Hub and HVR Agent to version 6.2.0/14 or newer (or on 6.1.0, 6.1.0/76+ or on 6.2.5, 6.2.5/5+). Once upgraded, you must renew your annual contract to start benefiting from re-sync detection.
You can transition to the updated pricing without upgrading your Hub and Agent, but in that case the improved re-sync detection mechanism won't be enabled. Without re-sync detection, you will still have to rely on the 5-day troubleshooting window for free refreshes.
You can upgrade your HVR Hub and Agent without transitioning to the updated pricing if you have an ongoing annual contract. Once you upgrade and we have one full month of usage data, we will provide you with an estimate of your usage with re-sync detection in our Pricing Estimator. That will help you make a more informed decision when renewing your contract.
Re-sync detection stores up to 50 MB of sample data per replicated table on the system where the HVR Hub System is hosted. Samples are stored in the HVR_CONFIG/metering directory for every channel containing the table, per source/target location pair.
Business Critical
This is a pricing plan where HVR can be deployed on-premise. The HVR Hub System should be connected to the Fivetran server for automatically sending the consumption/usage data and receiving the license. The consumption/usage data are sent in the form of two data files - MAR Data and Hub Snapshot.
Each month, your consumption/usage is calculated based on the number of MAR across all source (connector) and target (destination) locations in your account.
Once the HVR Hub System is registered with a Fivetran account, HVR securely begins transmitting consumption/usage data to Fivetran, which is encrypted and stored on AWS S3. The consumption/usage data does not include any personally identifiable information about the user.
HVR uploads MAR data file hourly, and Fivetran sends back a 7-day license key daily as part of this data exchange. HVR purges the MAR data after 24 hours.
HVR uploads the hub snapshot every 30 days.
The MAR data is stored on the disk of the hub server machine in hour granularity buckets per table prior to being sent to Fivetran. One week's worth of storage provisioning on hub machine is required, but the actual use is one or two days' worth of data because HVR automatically purges the MAR data a day after it is sent to Fivetran. Automatic purging of MAR data can also be disabled using the repository property Metering_Purge_Frequency. For more information about the MAR storage, see Storage Requirements for MAR.
If the Fivetran account registration is deleted from a hub system, HVR immediately stops sending usage data to Fivetran, and the automatic license renewal is stopped (the license expires after 7 days).
To view the hourly MAR data that is sent to Fivetran:
Execute the command hvrlicense in the CLI:
hvrlicense -m filename -B now-1hUse a text editor to open the file and view the data.
Prerequisites
For the Business Critical plan, you must:
- Enable outbound access from the web browser that you will use to register the HVR Hub System to the IP address 35.236.237.87 (fivetran.com).
- Enable outbound access from the system running the HVR Hub Server to the following IP addresses (on port 443). This is required for sending usage data to the Fivetran server:
- 34.110.137.135
- 34.120.211.189
- Register your HVR Hub System. You must create a Fivetran account or log in to fivetran.com with an account Administrator role.
- If you are using proxy server to connect HVR Hub System with Fivetran, then ensure to configure the proxy server setup.
If you have multiple HVR Hub Systems, you must register each hub system individually.
Consumption Data
The consumption/usage data (metadata) that are sent to Fivetran is used for calculating the MAR for your HVR Hub System(s). Following are the two data files that contain consumption/usage details:
For the Business Critical plan, the consumption/usage data (MAR) is automatically sent to Fivetran daily. The Hub Snapshot is sent to Fivetran every 30 days.
The MAR data or snapshot file sent to Fivetran does not contain any data from replicated tables or any confidential or secret data.
MAR Data
The MAR data that HVR sends to Fivetran contains information such as Hub Name, Hub ID, Hub Description, Hub Server URL, Channel Name, Location Name, Location Description, Location Type, Table Name, Base Name, Refresh Events (including the timestamp and metadata), hashes of primary keys changed, and HLL records for Integrate and Refresh jobs.
| Column in MAR File | Description |
|---|---|
| month | Month and year for which the MAR data is applicable. |
| hub_name | Name of the hub. |
| hub_id | Unique identifier of the HVR Hub System. |
| chn_name | Name of the channel. |
| src_loc_name | Name of the source location. |
| tgt_loc_name | Name of the target location. |
| mar | Total sum of MAR for the month. |
| mar_daily | List of incremental MAR values per day. |
| src_loc_type | Type (e.g. Oracle, SQL Server) of source location. |
| tgt_loc_type | Type (e.g. Oracle, SQL Server) of target location. |
| table_count_estimate | Estimate of the number of tables seen per source-target connection in a channel. The estimate has the same error rate as regular MAR, so usually +- 2%. |
| integ_mar_signature | Serialized form of the raw internal HLL structure which is used to track MAR data. |
| refr_mar_signature | Serialized form of the raw internal HLL structure which is used to track MAR data. |
Storage Requirements for MAR
HVR uses a special data structure called HyperLogLog (HLL) to track MAR. These data structures are stored on disk in the HVR Hub System, before sending it to Fivetran, in hour granularity buckets per table. HVR uses a hash value from the primary keys to update the data structure. HVR stores these data structures for a maximum of 1 month.
Each data structure is approximately 2 KB. Every day the amount of data stored is 24 (hour) * 2 (KB) * number of active tables; so the disk space needed per day is 48 (KB) * number of active tables.
For Business Critical plan, we recommend allocating a week's worth of storage capacity on the HVR Hub System for storing MAR data. The actual storage allocation required for MAR data on the HVR Hub System is typically only one or two days' worth of data, as HVR automatically purges the MAR data one day after it is sent to Fivetran. Automatic purging of MAR data can also be disabled using the repository property Metering_Purge_Frequency.
For Private Deployment plan, two types of MAR data are generated - daily and monthly. For daily MAR data, we recommend allocating a month's worth of storage capacity on the HVR Hub System. The daily MAR data is automatically purged after 30 days. For monthly aggregate MAR data, we recommend allocating the storage capacity of approximately 5MB per month. The monthly aggregate MAR data is never purged automatically. To purge the monthly aggregate MAR data, you need to manually delete the folders/files available in the hvr_config/metering directory.
The original primary keys can not be retrieved from the HLL data structure. In addition, HVR does not store the primary keys directly, but instead uses their hashes to update this structure. The hashes are irreversible and can not be retrieved.
Hub Snapshot
The hub snapshot contains information about the system configuration or usage such as Channel definitions, Events, Statistics, and Job state. On receiving a request from the Fivetran server, HVR uploads a usage snapshot per hub every 30 days. The hub snapshot is encrypted and stored on AWS S3. The hub snapshot file is stored on the disk of the hub machine prior to sending it to Fivetran. HVR automatically purges it a day after it is sent to Fivetran.
The hub snapshot file contains the following details:
- a week of events
- a week of statistics
- channel definitions
- job state
The snapshot does not contain log files, history, or transaction files.
The automatic generation of hub snapshot is similar to manually executing the command hvrsnapshotsave for saving the snapshot data into a zip file:
hvrsnapshotsave -r "Usage snapshot for account_id my_account_id" -e now-1w -s now-1w -l none -t none -V redact hub_name snapshot_filename.zip
Private Deployment
We've deprecated the Private Deployment pricing plan as of March 1, 2025. HVR accounts on the Private Deployment plan must transition to the Business Critical or other available plans upon contract renewal. See Pricing Plan Updates for more information.
This is a usage-based subscription plan where HVR can be deployed on-premises, in a virtual private cloud, or air-gapped in your secure network. There is no direct connection between the HVR Hub System and the Fivetran server.
Each quarter (91 days), your consumption is calculated based on the number of MAR across all source (connector) and target (destination) locations in your account. You are required to manually send the consumption data ([MAR]) via email to Fivetran at least once every 91 days from the effective date of your contract.
After purchasing the software, Fivetran technical support team will send you the license file via email. If you have not received the license file or have questions regarding it, contact Fivetran support. The license is valid for 6 months or until the end of your contract, whichever is sooner.
In this plan, there are two types of Monthly Active Rows (MAR) data:
Daily MAR: Auto-generated for the Hub System. This data is not sent to the Fivetran server. This MAR data is automatically purged after 30 days, so the storage requirement is limited to one month`s worth of data. You can disable automatic purging using the repository property Metering_Purge_Frequency.
Monthly Aggregate MAR: Also auto-generated for the Hub System. This MAR data is not purged automatically. Each monthly file is less than 5 MB in size.
For more information about the MAR storage, see Storage Requirements for MAR.
If you have multiple installations of the HVR Hub System on a hub machine, each Hub System must be registered individually with your Fivetran account.
Manually Send Consumption Data to Fivetran
For the Private Deployment plan, you must manually send your consumption (usage) data (only MAR data) via email to Fivetran at least once per quarter.
To manually send the MAR data:
Run the hvrlicense command in the CLI to generate a MAR data file in CSV format. The following command generates a CSV file with consumption data for the past 3 months:
hvrlicense -M .Command examples
Example 1 - Generate MAR file with custom name
hvrlicense -M filename.csvExample 2 - Generate MAR file with data from a specified date and time (e.g., 2022-03-30 18:00:00)
hvrlicense -B '2022-03-20 18:00:00' -M .Example 3 - Generate MAR file from remote machine
hvrlicense -R http://hubserverhost:4343/ -M .Email the generated CSV file to privatedeployment@fivetran.com.