Skip to main content

Plans & Pricing

info

In thie guide you'll find everything you need to know about how our pricing works, the plans we offer, and how you can track and manage your plan usage. For detailed plan information, visit our pricing page: View Pricing

Pricing Model: Credit-Based Usage​

Credits are the unit used to measure usage across the platform. You spend credits based on the number of rows your data pipelines process. Every time a record is synced—whether it’s a new record or an update to an existing record—it counts toward your credit usage. This includes any record that is being utilized from the source.

Credits give you flexibility to run both ELT and Reverse ETL workloads under a single usage model, scaling with how much data you actually move.

Credits per RowCredits per RowSimplified Example
ELT1 CreditIf an ELT pipeline processes 1,000,000 rows, it consumes 1,000,000 credits
Reverse ETL4 CreditsIf a Reverse ETL sync processes 250,000 rows, it consumes: 1,000,000 credits (250,000 × 4)

Why Reverse ETL Uses More Credits​

Reverse ETL workflows are more operationally intensive than ELT. The higher credit cost reflects this additional complexity and reliability as they require:

  • Data normalization and field mapping

  • Destination-specific formatting

  • API rate-limit handling and retries

  • Delivery guarantees and error handling

Free & Paid Credits​

The first 30 days for each unique data source with a live connections does not incur any credit utilization. This allows teams to refine data pull schedules, schemas, and address backfills without concern of consuming Extract credits

  • Free Period = The first 30 days since the very first successful sync of a given source on this account. Multiple logins for the same source do not provide a new free period.

  • Paid Period = Once the first 30 days since the first successful sync has elapsed, the paid period commences

  • Free Records = Any records synced during the free period

  • Paid Records = Any records synced during the paid period

  • Syncs from a Dummy Source and/or to a Dummy Destination are always excluded and don't affect free period.

Example:

  • You add Facebook on January 1st. Your first sync to a real destination (i.e. not a dummy destination) happened on January 15th.

  • You add another Facebook source on April 14th. You run a sync for that second source in the same day.

Your free period for Facebook started January 15th (your very first sync of Facebook in your account), and continues until February 14th (30 days).
Your paid period for Facebook started February 15th.
The fact you added a new Facebook source later (in April 14th) does not impact the free period duration at all.

Payment Structure​

  • You will be billed upfront for your selected plan at the start of each billing cycle.

  • If the monthly row limit is exceeded, overage charges are applied.

  • Overage charges are calculated and included in the invoice at the start of the next billing cycle.

Plan Limitations​

Each plan comes with specific limitations, including:

  1. Monthly Row Limit – Each plan has a maximum number of rows that can be synced per month.

  2. Minimum Sync Frequency – The frequency at which data can be synced is determined by your plan.

  3. Platform Users – The number of users who can access the platform is limited based on the plan.

  4. Live Connectors – The number of live connectors (active and running, not disabled) varies by plan.

Feature Access – You cannot access functionalities that are not included in your plan.

Overage Charges – Once the row cap is reached, additional usage incurs overage charges (excluding the free plan).

Plan Changes​

Upgrading Your Plan​

  • You can upgrade at any time.

  • The upgrade takes effect immediately.

  • The additional cost is calculated and billed on the same day as the upgrade.

  • If an upgrade occurs mid-billing cycle, you will be charged for the difference between the previous and new plan for the remaining cycle.

  • Changes applied immediately upon upgrade.