Service Consumption Tables

V.1.0.1 Effective August 1, 2023

These Service Consumption Terms are effective as of May 1, 2023 (the "Effective Date") and apply to all customers on Stacksync’s consumption based pricing model.

Stacksync provides automated cloud data pipelines (“Connectors”, “Apps”) to its customers (each a “Customer”, “you”, “your”) as a service which transports data from various sources and centralizes this data into a specific destination (the “Stacksync Service”). The sync can be unidirectional or bidirectional. The Stacksync Service is available in several different plans (“Plans”) and hosted in different geographical regions (“Regions”) by certain third-party cloud providers (“Cloud Providers”), as described more fully in your agreement with Stacksync (“Agreement”). Event-based actions (“Triggers”) can also be triggered based on data activity in Connectors.


  • Workspace: The customer’s collaborative space attached to a subscription. Each workspace has exactly one active subscription. Workspace contains Connectors and Destinations grouped into Bases.

  • Base: two or more apps connected together with data in sync. A base may be active, paused or deleted. Bases are organized within workspaces.

  • Account: The Customer’s account on Stacksync. An Account may own or have access to multiple workspaces. An Account contains personal data about the customer.

  • Arrears: For Capacity Purchases (defined below) only, this means any additional usage after the initial purchase has been used, but before the end of the original term. The Arrears period ensures you are able to continue using the Stacksync Services, even if the original Contracted Spend has already been consumed. You will be alerted by Stacksync when you are in Arrears.

  • Subscription: a paid plan attached to a workspace.

  • Billing Period: A calendar month running from the first to the last day of the month.

  • Capacity Purchase: A subscription-based plan which requires an annual upfront purchase of Contracted Spend in bulk.

  • Contracted Spend: The total dollar amount purchased as listed in the Order Form. Contracted Spend is shown on an annual basis.

  • Destination: A destination is a data warehouse, database, data lake, or data lake house where the data is delivered.

  • Incremental Spend: The price charged for the next thousand MAR (or portion of the next thousand MAR) consumed after surpassing the MAR Threshold for the month in question.

  • Initial Sync: The first time that a connector completes a historical sync.

  • Monthly Purchase: A plan which is not subscription based, whereby a Customer is billed monthly in-arrears for their usage during the prior Billing Period. Monthly plans are available to purchase at (i) user interface or through the (ii) AWS, (iii) GCP, or (iv) Azure marketplaces.

  • Monthly Active Rows (“MAR”): The number of distinct Primary Keys synced via Stacksync, calculated on a per-Base basis. We only count a row once per Billing Period, even if it syncs multiple times.

  • MAR Threshold: The minimum MAR usage requirement to receive the consumption rates on the Service Consumption Table below.

  • Monthly Spend: The dollar amount consumed each Billing Period from your Contracted Spend based on your actual monthly usage.

  • Total Monthly Spend: Total Monthly Spend is the sum of Monthly Spend on Connectors and any other applicable uses of the Stacksync platform and Services.

  • Order Form: The form used to purchase Contracted Spend from Stacksync. For Capacity Purchase customers, this is an order form document. For Monthly customers, this may be an order form document or may be the terms attached to a Monthly Purchase through one of the marketplaces identified above.

  • Plan: The bundle of features included as a part of your Stacksync Service and outlined here. Plans may be Capacity Purchase plans ( subscription-based) or may be Monthly Purchase plans (do not require annual subscriptions).

  • Primary Key: A unique identifier that specifies a distinct row within a table. In bidirectional sync mode, the primary keys of the rows in the synced apps are mapped together. In this context, the Primary Key corresponds to a unique mapping. For instance, a corresponding row in synced apps within the same base results in only one Primary Key.

What is a Monthly Active Row (MAR)

‍MAR are similar to total monthly synced rows but are less prone to variation and less prone to outliers. MAR is calculated as the number of distinct Primary Keys transported through the Stacksync Service for a Workspace in a given Billing Period. Primary Keys are counted separately by Stacksync Base; therefore, if a distinct Primary Key is synced more than once in a given Billing Period then the distinct Primary Key counts as only a single MAR. For example, a distinct Primary Key synced 30 times during a Billing Period will count as one MAR. If a Primary Key is not available, we create a synthetic (hashed) Primary Key to ensure consistent tracking. One exception to this is that we exclude up to 50% of the MAR associated with the Initial Sync for each new Base added.

In order to calculate MAR, usage data is sent to Stacksync. For downloadable software, it may be necessary for Customer to troubleshoot network issues or access permissions to allow Stacksync to receive usage data and for Customer to access the software.

MAR Computation

Monthly Active Rows (MAR) serve as billing units and are determined within a billing period of one month. MAR are calculated based on the following actions:

  • Creation, update, or deletion of a record at least once during the billing period. If the same record is updated multiple times within the same period, it only counts as one MAR.

  • Trigger execution that meets the filtering conditions. Each trigger that successfully fires up counts as an additional MAR independently. For instance, if a record is updated five times during the billing period, and two of those updates activate triggers, only one MAR will be counted for the five record updates, and two MARs will be counted for the triggered actions. Thus, a total of three MARs will be billed for that scenario.

  • Inactive records synced in tables that require full crawling of data to detect changes, as incremental change detection through webhooks is not feasible or not implemented by Stacksync, will also be counted as MARs. For example, some systems such as Hubspot do not support data change notifications being pushed to Stacksync for all tables, or it may not be technically possible in certain cases. In these scenarios, Stacksync employs efficient data processes to detect changes and only publish the incremental changes to synced systems. All synced records will be counted at least once as MAR within a billing period if they exist. However, even if the full data crawling occurs multiple times during the billing period, the records will only count as one MAR. Furthermore, if these same records are updated during the period, they will not count twice as MAR since they were already counted once within that period.

  • API proxy - standard calls: free within the included quota per plan. Additional usage counts 1 MAR per API call

  • API proxy - AI insights: free within the included quota per plan. Additional usage counts 15 MAR per API call.

How does service consumption work?

The Monthly Spend on Workspaces is calculated using the number of MAR within each Base during that Billing Period. Monthly Spend is consumed based on a diminishing slope: in other words, the more unique data you sync during a Billing Period, the cheaper the incremental cost per unique Monthly Active Row.

Your usage pricing depends on the Plan you have selected and whether you are drawing down from a Capacity Purchase Plan or paying for supplemental usage. For Monthly Purchase Plans, your usage pricing is based on the prices available on our website,

Capacity Purchase Plan

If you have purchased a Capacity Purchase Plan, your consumption rates will be determined by the Service Consumption Table outlined below, subject to the terms of your specific Order Form. In the event you have multiple Workspaces on a single Capacity Purchase Plan, you may apply your Contracted Spend toward any of your Workspaces on the Stacksync Service. However, the Service Consumption Table benefits for increased volume listed below will only be applied on a Workspaces-by-Workspaces basis (volume discounts cannot be combined across Workspaces). Stacksync will provide you with monthly usage for the Billing Period just completed via the Stacksync dashboard.

Service Consumption Table

Additional Monthly Active Rows Pricing (Consumption based). The pricing increments in thousand MAR. Each thousand MAR started, even partly consumed, is due in full.

First 10k


10k → 100k


100k → 1M


1M → 10M


10M → 100M


100M → ∞


To compute the monthly spend, the formula is:

Total Monthly Spend = Monthly Base Price per Workspace + MAR consumption

For the MAR consumption, the formula is (e.g. with 200k monthly active rows):

  • First 10k = free (included in package)

  • 90k MAR = 90 * 8 = 720$

  • 100k MAR = 100 * 2 = 200$

MAR consumption = 0 + 720 + 200 = 920$

What happens when Contracted Spend is depleted?

For Capacity Purchase Customers: When the Contracted Spend on your Capacity Purchase is depleted but the Stacksync Services are still being used, you are in Arrears; however, you will be allowed to continue using the Stacksync Service for so long as you are fulfilling payment obligations and complying with the other terms of your Agreement. Beginning from the first Billing Period where you are in Arrears, and continuing until you purchase additional spend through a new Order Form, you will be charged the “Monthly Pay As You Go” rates specified above.

When Contracted Spend is depleted, Stacksync will prompt you and provide the option to purchase additional spend/usage through Stacksync if you are on a Contracted Spend plan. Likewise, Stacksync will alert you when you are in Arrears.

Expiration of Contracted Spend

You must use Contracted Spend within the subscription term in your Order Form. Contracted Spend does not roll over from one subscription term to the next. If you have a Capacity Purchase that is coming to an end, contact your account representative to arrange for a new purchase on an updated Order Form.‍

Multiple Workspaces

If you decide to have multiple Workspaces, the Stacksync Service Consumption Table will apply to the MAR within each Workspace. You cannot combine the MAR across multiple Workspaces and apply this MAR to the Stacksync Service Consumption Table to get a more favorable consumption rate. However, if you would like to merge multiple Workspaces into a single Workspace with separate Bases, you can reach out to Support through your dashboard or your Account representative to get help with this migration.

Changes to the Stacksync Service Consumption Table

Stacksync may update this Service Consumption Table from time to time. If we do make updates, we will update the “effective date” at the top of this Service Consumption Table.

Unless another agreement between the parties supersedes this Service Consumption Table, any updates will become effective for Customer upon renewal or entry into a new Order Form after the updated Service Consumption Table goes into effect. For Monthly Purchases/Plans, updates will take effect in the Billing Period immediately following the new effective date for the updated Service Consumption Table.

If we make a material update, we will use reasonable best efforts to alert you through the Stacksync Service dashboard or via email prior to the update taking effect.

Benefits per plan

These plans cover the options which are accessible to the plan subscribers.


Number of Bases




Monthly Active Rows (MAR)


10k + additional usage

10k + additional usage





Early access to Preview integrations




Collaborators per workspace




Processing region

Basic regions

Basic + Extended regions

All regions (and Custom regions)

Log retention

1 day

7 days

30 days


Community Slack

Chat Support

Email, Call and up to 24/7 Hotline

Solution Architects

On demand

On demand

Dedicated Solutions Architect for setup and monthly support





On-premise deployment




API Proxy - standard

50k calls per day

150k calls per day + additional usage


API Proxy - AI insight

10 calls per month

200 calls per month + additional usage


For the enterprise plan, every option is not necessarily included in every contract and to the same extent. Every enterprise contract is unique and tailored to the needs of every client.

API Proxy

The CRM API proxy is an additional service offered by Stacksync.

There are two types of API proxy calls: Standard and AI Insights.

API Proxy Standard calls

All calls except AI Insights calls

API Proxy AI Insights calls

All API endpoints labelled with the "ai" keyword in the URL (e.g.

For more information on how they are priced, please read our Service Consumption Table documentation.

Last updated