Usage-Based Pricing

Fivetran’s pricing model involves four basic principles:

Pricing is usage-based. You are charged based on what you use each month.

Your connection usage is measured in Monthly Active Rows (MAR). MAR are unique identifiers, or primary keys, that we use to track transfers from your source system to your destination each month. These keys are counted separately for each account, destination, connection, and table. Once a row is active, it is only counted once per month - no matter how many updates are made that month.

Your transformation usage is measured in monthly model runs. Monthly model runs is the total number of models successfully executed as part of your transformation jobs in a given month.

You can choose which pricing plan fits your requirements. Fivetran offers the following pricing plans:

• Free - Get all the features of our Standard plan up to 500,000 MAR and 5,000 model runs per month. We recommend this plan if you have very low data volumes or if you want to trial Fivetran on low volumes of data.
• Standard - Unlock data from your database sources. Our most popular plan, Standard is ideal for teams that need robust cross-departmental analytics.
• Enterprise - Access high-volume agent connectors, fastest sync times, and advanced user permissioning. Enterprise is ideal for data teams that need real-time data delivery and have strict governance requirements.
• Business Critical - Ensure the highest levels of data protection and compliance on Business Critical. This plan is most popular among large Enterprise businesses or anyone in the healthcare, insurance, and finance industries.

You can compare features across our five plans on our Pricing Features page. Also, to see examples of pricing in action, check out our Pricing Guide.

Plan limitations

Some features are limited to specific pricing plans. Learn more about our plans and their features on our Pricing page.

The most important plan limitations include:

• The Free plan has a maximum monthly MAR consumption of up to 0.5 million.
• The Free plan has a maximum Transformations monthly model run consumption of up to 5,000.
• Only the Enterprise and Business Critical plans offer access to enterprise database connectors and Hybrid Deployment.

Enterprise database connectors

You can sync data from the following database sources only if you are on the Enterprise or Business Critical plans:

• Oracle
• Oracle EBS
• Oracle RAC
• Oracle RDS
• SAP ERP on HANA

You can sync data using the following High-Volume Agent connectors if you are on the Enterprise or Business Critical plans:

• High-Volume Agent Oracle
• High-Volume Agent SQL Server

Hybrid Deployment

With the Hybrid Deployment model, you can process data within your own network while Fivetran acts as a unified control plane for all your data movements. This model is designed for organizations who must keep their data local for security or compliance reasons but still want to benefit from Fivetran's managed service.

We support Hybrid Deployment for multiple connectors and destinations. Learn more in our Hybrid Deployment documentation.

Plan renewal

If you are on our Standard plan and are using the enterprise database connectors, you must upgrade to the Enterprise plan during account renewal.

We apply these billing rules in the following plan-renewal scenarios:

Plan conversions

You can change your pricing plan in the Billing & Usage section in your Fivetran dashboard. We will detail the changes that you will gain or lose with a Confirm upgrade or Confirm downgrade prompt.

NOTE: Plan conversions are not available for Sales-assisted accounts and accounts that pay through a marketplace.

NOTE: We bill you the cheapest plan rate for the whole month when you switch pricing plans.

Plan upgrades

Plan upgrades may only require payment submission. You will have to enter your payment information if upgrading from the Free plan.

Plan downgrades

Plan downgrades require acknowledging and consenting to losing features. We will outline the features that you will be losing when downgrading an account.

If you are currently using features that only exist on your pricing plan, such as more than ten users on an account, you will have to manually undo that feature before downgrading.

You will need to confirm your consent to losing certain features.

Billing options

You can sign up for Fivetran on an annual subscription or a monthly pay-as-you-go model.

The 14-day free trials for all new accounts can help you determine whether Fivetran meets your requirements before making any commitments.

Annual contracted spend model

The contracted spend model is a subscription-based plan that requires an annual upfront purchase of contracted spend in bulk. Contracted spend is the total amount purchased as listed in the Order Form. Your contracted spend is consumed depending on your MAR usage for the month. The rate of consumption varies by your plan. See the rate of consumption for your plan in the Service Consumption Table.

With this model, Standard, Enterprise, and Business Critical plans are available by default.

Discounts with annual contracts

We use a transparent discounting system for all customers signing up for annual contracts. The discount percentage is determined based on the total annual list price of your contract and the plan you opt for. Discounts start at 5%, with greater discounts available for contracts with a higher annual list price.

NOTE: Your list price is the price before any discounts are applied. Discounts for annual contracts can be estimated using our Pricing Estimator.

The table below outlines discount rates that Fivetran offers depending on the annual list price of your purchase. The discount that will apply to your specific purchase will be displayed on your purchasing document.

NOTE: On all plans, greater discounts are available for annual contracts with a higher annual list price.

Monthly pay-as-you-go (PAYG)

The monthly PAYG plan is not subscription-based. You are billed monthly in arrears for usage during the prior monthly period. This plan offers flexibility as you can cancel anytime, and there is no MAR consumption minimum. With this plan, the Free, Standard, and Enterprise plans are available by default.

You can purchase a monthly PAYG plan from:

• The Billing tab
• AWS Marketplace
• Azure Marketplace
• Google Cloud Marketplace

Differences between annual contracted spend and PAYG

Both billing options have distinct advantages as we strive to suit the needs of a diverse range of customer requirements. The table below lists the most crucial differences between the annual and PAYG billing models:

Billing conversions

We apply these billing rules if you switch from a monthly pay-as-you-go plan to annual contracted spend, and vice versa:

• We bill you the annual rate for the whole month when you switch from the monthly pay-as-you-go plan to the annual contracted spend model.
• We bill you the pay-as-you-go rate for the whole month when you switch from the annual contracted spend model to the monthly pay-as-you-go plan.
• We bill you the pay-as-you-go rate for the whole month and pull usage from your remaining balance if you have a remaining balance when you switch from the annual contracted spend model to the monthly pay-as-you-go plan. We also expire any balance that would have been left over after the annual contract expired.

Monthly Active Rows

MAR is the number of distinct primary keys synced from the source system to your destination in a given calendar month. A primary key is a unique identifier that specifies a distinct row within a table. We separately count primary keys by account, destination, connection, and table. If a primary key is not available, we create a synthetic (hashed) primary key to ensure consistency. Fivetran uses a hash sampling re-sync detection algorithm to detect and classify row changes.

We only count a row once per month, even if it syncs multiple times. It doesn’t matter how many times a row is updated in a month; you don’t pay multiple times for updates on the same row in the same month. For example, if we sync a distinct primary key more than once in a month, then the distinct primary key counts as only a single MAR.

Monthly active rows are similar to total monthly synced rows but are less prone to variation and outliers. For example, a distinct primary key synced 30 times during a month counts as one MAR. Row-based pricing models, such as monthly synced rows, would charge you multiple times in that situation. Fivetran does not.

To understand what monthly active rows mean, and how they differ from monthly synced rows, consider the following simplified example:

Suppose you have a small table with a primary key id and one attribute, counter:

You update counter from 3 to 4 in row c:

This operation generates 1 active row. Now suppose you update the same counter again in the same month:

This is still just 1 active row for this month. On the other hand, if you update row a, then you have 2 active rows:

We sync most connections using incremental updates where we only update the new or updated rows each sync. Thus, you only pay for a subset of the data in the source every month. What percentage of a table or a connection is imported per month depends on how you use your source system. For example:

• If you opt to modify only new records, we import only a small percentage of the table or connection per month that causes a small percentage of the tables to have MAR.
• If you opt to modify years-old historical records every sync, we re-import the complete source data that may cause a very high percentage of the tables to have MAR depending on the number of changes in your source system.

Monitor your MAR usage

Monitor your usage from your Fivetran dashboard or by using the Fivetran Platform Connector.

NOTE: We calculate MAR usage in the UTC timezone.

Fivetran dashboard

The Fivetran dashboard allows you to monitor your usage both account-wide and for specific connections.

Account-wide MAR usage

In Fivetran, go to Account Settings > Billing & Usage to see the billing and MAR usage details for your account. These tabs offer visual representations of your usage and are updated daily.

The Billing tab displays your current and past spend details. You can also view and change your plan and payment details. For more information about the Billing tab, see Account Settings: Billing & Usage.

The Usage tab displays your connection and transformations usage. For more information about the Usage tab, see Account Settings: Billing & Usage.

Connection-specific MAR usage

The Usage tab on the Connection Details page displays the MAR usage for a given connection and its tables. For more information about the Usage tab, see Connections: Usage.

Fivetran Platform Connector

The Fivetran Platform Connector loads your MAR data into your destination, where you can run analyses on it just like you do with any other data. To understand what is driving the overall MAR within your account, use our sample queries to review MAR at the table level.

HVR

Fivetran's pricing for HVR varies based on the pricing plan and licensing model. Users must subscribe to the Business Critical pricing plans. Moreover, users must use consumption-based or usage-based pricing depending on their pricing plan. Read our documentation on pricing plans for HVR and licensing for HVR to learn more.

Historical MAR

Historical MAR represents data that already exists in the source or was synced when the table or connection was created.

Examples of historical MAR include:

• Initial table syncs
• Table schema changes that lead to a full table re-sync (e.g., new added columns)
• Manually triggered re-syncs
• Data added during the first sync after a new account or project is added
• Periodic re-syncs of additional data to avoid data integrity issues
• Source-specific data integrity issues that require re-syncs
• Migration syncs
• Bug fixes that require re-syncs

Free MAR

Free MAR represents rows that are synced but do not count towards paid MAR. The following counts towards free MAR:

• Initial syncs
• Connection trials
• Private preview connectors (excluding destinations)
• Fivetran system tables
• Fivetran Platform connector
• Re-syncs
• HVR Troubleshooting Window
• Accounts with a legacy pricing plan
• Free plan
• Promotions

Incremental MAR

Incremental MAR represents new or updated data in the source since the last sync.

Examples of incremental MAR include:

• Overlapping incremental syncs
• Changes in re-imported table syncs
• Reporting connector rollback syncs that occur during a conversion window

Optimize your consumption

Higher usage leads to a better rate

We automatically optimize certain aspects of your MAR consumption. Your cost per row declines automatically as your monthly consumption increases. To learn more about MAR rates, see the Fivetran Service Consumption Table.

Sync frequency

Your connections’ sync frequency makes no difference to your monthly active rows because MAR is based on how many unique rows are updated, not on how many updates occur. Maintain whatever sync frequency best serves your business needs.

Block schemas or tables

You can reduce your monthly active rows by blocking schemas or tables from syncing if they don’t contain valuable information. The monthly active rows per connection chart in your billing dashboard shows you which connections have the highest usage. The Fivetran Platform Connector shows consumption by table to help guide these decisions. However, not all connectors support blocking schemas or tables.

Block columns in tables without a primary key

You can reduce your monthly active rows by blocking columns for tables without a primary key. Column blocking can make a difference because we create a synthetic primary key for these tables, you can reduce your MAR if you block a commonly-changing column that is used as part of the synthetic primary key. However, not all connectors support column blocking.

IMPORTANT: You can't block primary key columns.

MAR increases

Sharp increases in MAR can occur for the following reasons:

• It is the beginning of the month
• Changes in the source
• User error
• Connection paused and then resumed

Beginning of the month

At the beginning of each month, you may see a sudden increase in paid MAR due to frequent changes in a large number of rows. Once a row is active, it is only counted once. Any additional changes to counted rows won't count towards MAR. Any remaining data use will mostly come from new records.

We reset the count of your active rows at the end of the month. All rows go back to being inactive, and your active rows count goes back to zero. During the first sync on the first day of the month, Fivetran fetches new rows and existing rows with updated values from the source, and these rows become active. Since we only count these rows once per month, you may observe what seems like an increase in your MAR usage on the first day of each month. You may also observe what seems like an increase in MAR when most rows have frequent value changes.

You will not observe what seems like an increase in your MAR usage if the first sync doesn’t occur on the first of the month.

Changes at the source

Administrators, users, and integration teams should collaborate to understand how the data source interacts with Fivetran.

• Integration teams must know about connector-level differences.
• Administrators must understand how to provide source access.
• Users must outline their expectations from the solution. Often, increases in MAR are due to changes in the source. Adding a new column or table leads to MAR increases. It's important to communicate with your stakeholders on how their sources impact usage and ensure every table you're moving provides value to the team.

User-related errors

Unexpected data use can occur when you unpause a connection or delete a connection, then recreate it with exactly the same name. Both cases lead to an increase in MAR. To avoid unexpected data use, we recommend re-syncing paused connections. Also, every time you create a new connection, ensure you use a unique name. You can do these either through the Connection page or the REST API.

Connection paused and then resumed

MAR usage may suddenly increase if a connection was paused for a period of time and then resumed. The first sync after resuming a connection extracts and loads all the data that was updated in the source during the time the connection was paused.

Understand your MAR usage

Learn how operations in your Fivetran account impact your MAR usage.

New connections

Every new connection you create has 14 days of use at no cost.

Release phases

Every connection based on a Private Preview connector is free, excluding destinations. We charge for connections when the associated connector is in Beta or Generally Available, and pricing varies on functionality. See our core concepts documentation for more information.

Initial syncs

Initial syncs don't incur a cost for the historical data they sync, but tracked incremental updates may count towards paid MAR outside the connection free trial period.

Re-syncs

In the following scenarios, re-syncs are free:

• Historical data from adding a column
• Unchanged rows in re-import tables
• History mode unchanged rows
• Post-trial MAR that was already seen in the trial
• All other historical syncs

New tables

New tables are treated like an initial sync. See our MAR for new tables troubleshooting article to learn more.

New columns

When you sync a new column of an existing table, you don't incur MAR usage. This is true even when the value is backfilled in all rows of the table.

Automated schema migrations

When we automatically add a column to a connector schema as part of an automated schema migration, rows in the table that are backfilled with data don't count towards MAR.

Primary key data type changes

If the data type of primary key changes, it doesn't affect your MAR.

Similarly, in a table without a primary key, if the data type of columns from which we generate synthetic (hash) primary key changes, it doesn't affect your MAR.

Tables without a primary key

If a table doesn’t have a primary key, we create a synthetic (hash) primary key. The synthetic primary key is a hash of values of the columns defined for that table, so if those columns change, the primary key changes. We calculate the MAR for these tables based on their synthetic primary keys. The composition of this primary key differs by source.

In a table without a primary key, adding or removing columns that we use to generate the synthetic primary key does affect MAR. Each row in the table counts towards MAR.

Fivetran system tables

The following connector-specific system tables count towards free MAR:

• FIVETRAN_QUERY
• FIVETRAN_API_CALL
• FIVETRAN_FORMULA
• FIVETRAN_FORMULA_MODEL

History mode tables

Every time a record's value in a source table with history mode enabled changes, we insert a new row in the destination table. This new row counts towards MAR when changed, and your usage depends on the number of changes.

Re-import tables

We re-import tables in full during every sync as part of the sync strategy for some of your connections. During a re-import sync, we apply the same logic as for incremental tables that only activate changed rows.

For example, let's say that you have a re-import table with 100 rows from the previous month with zero changes. Fivetran will sync all 100 rows but considering there weren't any changes, it won't count towards MAR. Then, there is another sync 24 hours later and there are 20 new rows. During this second sync, Fivetran re-imports the full 120 rows but the MAR usage is just 20.

Multiple connections based on the same connector

Each connection in your account contributes towards your monthly active rows. It is not the connector but the instance of the connection that matters. Even if the connections sync the same data from the same source (with the same primary keys), they contribute separately to your MAR.

Same source, multiple destinations

If you have two or more connections of the same type that sync from one source to multiple destinations, we count each connection’s active monthly rows separately. For example, if you have two Salesforce connections, where one syncs to your staging destination and the other to production, we count the MAR of the connections separately. The sum of rows synced through each connection counts towards your MAR.

Data blocking

You can block specific columns and tables from replicating to your destination. However, you can't block primary key columns. If you update a blocked column that is not a primary key column in your source table, the update counts towards your MAR.

Deletes in the source

If a connector supports the Capture Deletes feature, and you delete data from your source, it does not count towards MAR usage. We soft delete the corresponding data in your destination by setting the system column _fivetran_deleted to TRUE.

Deletes in the destination

If you delete data in your destination and later sync it again from your source, it counts towards your MAR.

Rollback syncs

If your connection performs a rollback sync as part of its sync strategy, the sync may fetch additional data from the previous month. We consider these past records as new unique records for the current month, and these rows count towards your MAR.

Phantom updates

In some rare scenarios, the source attempts to update rows that do not exist in the destination. We define these updates as phantom updates. Phantom updates are not visible in the destination, but they contribute to MAR since we capture these updates. Phantom updates occur when we try to mark the _fivetran_deleted column TRUE for deleted records in the source.

For example, consider that you have a table TARGET in the destination, with column id as its primary key, and there is no record in the table with id = 2. Now, consider that you create a record with id = 2 in the source and then delete it before your connection syncs the record. The source marks the record with id = 2 as deleted. In the subsequent sync, we retrieve the record with id = 2 with the deleted status. We try to update the _fivetran_deleted column to TRUE in the TARGET table. We can't update the record because the record with id = 2 does not exist in the destination. In the process, we capture a new unique (deleted) row, and this row counts towards MAR.

Transformations

Transformation usage does not count towards monthly active rows (MAR). Instead, we measure transformation usage in monthly model runs. We only count successful monthly model runs as usage.

Each month, we offer 5,000 free model runs. Once your usage goes past 5,000 monthly model runs, we start charging for transformations usage. Additionally, the higher your paid usage is, the lower is the price per model run. See our Transformations Pricing and Transformations Pricing FAQ documentation for more details and instructions on how to monitor and optimize your monthly model runs consumption.

* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.