Airbyte pricing per Cloud credit, plan costs and what a sync really bills

How does Airbyte pricing work?

Airbyte pricing works on three models: metered credits on Airbyte Cloud Standard and Plus, custom capacity-based pricing through Data Workers on Pro and Enterprise Flex, and a self-managed Community edition with no license fee. On the metered plans each sync consumes credits based on how much data it moves, so the invoice tracks volume rather than seats.

The credit rates are published. API and custom sources consume 6 credits per million rows. Database and file sources consume 4 credits per GB observed. At $5 per credit, our arithmetic puts that at about $30 per million API rows and about $20 per GB from a database or file source. How many rows count depends on the sync mode: a Full Refresh sync charges every row it syncs, while an incremental API sync charges only the rows added, edited, or deleted since the last run.

The split between self-hosted and Cloud matters because the two models fail in opposite directions. Self-hosting has no license line and a real cost in the servers, upgrades, and on-call time it takes to keep 600+ connectors running. Cloud removes that operational load and replaces it with a meter that moves every time your data does. A team with spare engineering time and steady volume leans self-hosted. A team that wants no infrastructure and has lumpy volume leans Cloud, and watches the meter.

Above the metered plans sit Pro and Enterprise Flex. They drop the per-credit meter and charge for sync capacity through a unit Airbyte calls a Data Worker, quoted by sales. That model is aimed at teams whose volume is high enough that paying per row stops making sense.

How much does Airbyte cost per month?

Airbyte Cloud costs $20 a month on Standard, which includes 5 credits, plus $5 for each extra credit. Plus starts at $189 a month for 40 credits, with packages up to $4,999 a month for 2,000 credits and $5.00 per credit in overage. Pro and Enterprise Flex are custom quotes. New accounts get a 30-day trial with 400 credits, which Airbyte values at $2,000.

To put the included credits in context, here is our arithmetic using Airbyte's published consumption rates. The 5 credits in Standard cover roughly 830,000 API rows or 1.25 GB from a database or file source. The 40 credits in the entry Plus package cover roughly 6.7 million API rows or 10 GB. Anything beyond that is billed at $5 per credit.

Plan	Price	Billing unit	Sync frequency	Who it fits
Standard	$20 a month, 5 credits included, extra credits $5 each	Credits (volume-based)	Not listed as a plan feature; 15-minute syncs start on Plus	Small pipelines that want a fully managed cloud, with portal support 7am to 7pm EST
Plus	From $189 a month for 40 credits, packages up to $4,999 a month for 2,000 credits, $5.00 per credit overage	Credits (volume-based)	Down to 15 minutes	Teams that need SSO, field renaming, 2 workspaces, and 24-hour SLA support
Pro	Custom	Capacity (Data Workers)	Down to 5 minutes	Teams that need RBAC, custom mappings, and fresher data at higher volume
Enterprise Flex	Custom	Capacity (Data Workers)	Set by contract	Organizations that need in-boundary, on-prem, or multi-region deployment

The self-managed Community edition sits outside this table. It has no license fee, and you pay for your own servers and engineer time instead.

The honest read: at genuinely low volume, Standard is hard to undercut, because $20 a month with a few extra credits is a small bill. The number gets interesting when volume grows or spikes, which is the next question every buyer asks.

What happens when you run out of Airbyte credits?

When you run out of credits, Airbyte Cloud does not pause your connections. Syncs keep running and Airbyte bills the extra usage in arrears at the plan's credit rate. If usage in a billing period reaches $10,000, Airbyte charges the saved card and issues an invoice, so there is no automatic spending cap.

That behavior is kind to your pipelines and hard on your budget. A dashboard never goes stale because a credit balance hit zero, but a backfill, a new high-volume API source, or a connection that silently switched to Full Refresh can run for days before anyone looks at the usage page. At $5 per credit, our arithmetic says an unplanned 10 million row API backfill adds about $300, and a 100 GB database resync adds about $2,000.

Three habits help. Check the usage page weekly during the first months on a new plan. Size your credit package on a real month of data, not the trial. And review any connection that uses Full Refresh, because it charges every row it syncs each time it runs.

Is Airbyte cheaper than Fivetran?

It depends on your row counts and how often your rows change, because both tools bill by consumption. Airbyte Cloud meters credits against rows and gigabytes moved. Fivetran bills by Monthly Active Rows, the count of distinct rows inserted, updated, or deleted in a month. Two consumption meters, two different units, so the cheaper one is workload-specific.

The practical difference is what each meter punishes. Airbyte's volume model charges for the data you move, so a Full Refresh source or a large backfill shows up directly on the credit line. Fivetran's Monthly Active Rows model charges for rows that changed, so a table that updates the same few thousand records all day can cost less there than on a raw-volume meter, while a high-cardinality table with millions of distinct daily changes can cost more. There is no universal winner. Model both against a real month of your own data before you commit. We keep a full breakdown in the Fivetran pricing article, and if you are weighing the tools directly, the Fivetran alternative and Airbyte alternative pages lay out the tradeoffs.

One more thing both models share: the bill moves with your business. That is fine when volume is steady and awkward when it is not. Our own pricing is flat by plan (Starter $49, Growth $149, Scale $399, Enterprise $798), so a heavy month and a quiet month cost the same. That is a different bet than either consumption meter, and it wins specifically when predictability matters more than paying the least on a slow week.

What is a Data Worker in Airbyte pricing?

A Data Worker is the capacity unit Airbyte uses to price the Pro and Enterprise Flex plans. Instead of paying per credit for rows and gigabytes moved, you pay for an amount of sync capacity, and the price is custom, quoted by Airbyte sales. It swaps a volume meter for a capacity commitment.

The point of capacity pricing is to remove the per-row anxiety once you are moving serious data. Instead of watching a credit counter, you size how much parallel throughput you need and run as much volume as that capacity can process inside your schedule. A team with dozens of connectors syncing on tight windows can end up cheaper here than on the metered plans, which is exactly when Airbyte steers you toward it. Pro also adds RBAC, custom mappings, and sync frequency down to 5 minutes. Enterprise Flex adds in-boundary, on-prem, and multi-region deployment.

The tradeoff is commitment and opacity. There is no public list price for either plan, so you cannot budget them from the pricing page. You also have to forecast capacity: buy too little and syncs queue, buy too much and you have paid for idle throughput. It is the right model at scale and the wrong one for a small team that would be fine on Standard.

Is self-hosting Airbyte actually free?

The license is free; the operation is not. Community edition is open source and costs nothing to download and run, with the full 600+ connector catalog and no per-row fee. What you pay instead is infrastructure (the servers or Kubernetes cluster it runs on) and engineer time to deploy, upgrade, monitor, and fix it when a connector breaks at 2 a.m.

For teams that already run Kubernetes and have platform engineers, that cost is close to marginal: full control, data that never leaves your environment, and no meter at all. For a small analytics team without an ops function, the same setup is a part-time job that competes with the work you actually want to do. The connectors update frequently, sources change their APIs, and someone has to own the upgrades.

The right way to compare is total cost of ownership, not the license line. Add up the infrastructure bill, a realistic slice of an engineer's salary for maintenance, and the cost of the incidents you will absorb, then weigh that against a managed plan. Self-hosting wins when your marginal engineering cost is low and your volume is high. It loses when a person's time is your scarcest resource. This is the same lens you would use on any data integration platform: the sticker and the true cost are rarely the same number.

How do you keep Airbyte costs predictable?

Cut the volume that does not need to move, and cap the frequency that does not need to be fast. Most surprise Airbyte bills come from Full Refresh syncs, which charge every row synced, and from aggressive schedules. Use incremental syncs so API sources charge only rows added, edited, or deleted, lengthen the interval on sources that do not need fresh data, and exclude tables nobody queries. That last point is where the two big usage meters diverge sharply, because a row re-synced repeatedly in one month is charged once by Fivetran and every time by Airbyte, compared in Fivetran vs Airbyte pricing at high volume. The counting rules for every other platform in the category sit in data integration pricing compared.

A few habits keep the meter honest. The rates below are Airbyte's published consumption rates; the dollar column is our arithmetic at $5 per credit.

Source type	Billing unit	Cost at $5 per credit
APIs and custom sources	6 credits per million rows	About $30 per million rows
Databases and files	4 credits per GB observed	About $20 per GB
Full Refresh syncs	Every row synced is charged	Re-bills the whole table on every run, so use it only when a source cannot sync incrementally
Incremental API syncs	Rows added, edited, or deleted	Tracks real change, usually far below a full table

Watch three things monthly: which connections consumed the most credits, whether any connection runs Full Refresh when it could run incrementally, and whether your sync frequency still matches how the data is used. Because Airbyte keeps syncing after credits run out, the usage page is your only brake, so check it before a backfill turns into a month-end surprise. Figures from Airbyte's pricing page and credits documentation, read 21 September 2026.

If predictable is the whole point, a flat plan removes the variable entirely: our tiers (Starter $49, Growth $149, Scale $399, Enterprise $798) cost the same whether you move a thousand rows or ten million, so a launch month and a slow month land on the same invoice. Airbyte still wins on connector breadth (600+) and on open-source control, and at low volume Standard can be cheaper, so the decision is about which risk you would rather carry. Once the data lands in your warehouse, you can ask the warehouse questions in plain English instead of writing SQL for every question. To see flat pricing mapped to your own tables, start a live demo.