ingestion

Airbyte

Airbyte is a ingestion product that connectors for hundreds of sources. This profile covers what it does, how it is priced, and where it stops being the right choice.

What the product actually does

Airbyte is an open-source data integration platform. The core is a catalogue of connectors — several hundred at last count — each of which knows how to pull data from one source and write it to one destination. The open-source distribution lets you run the whole thing yourself; the cloud product removes the operational work.

The architectural choice that matters is that connectors are defined declaratively where possible. A connector described as a YAML manifest can be built and maintained by someone who is not a platform engineer, which is why the catalogue grew faster than comparable proprietary tools.

How pricing works once you are inside

The open-source version is free and you pay in engineering time. The cloud version prices on rows synced, with a free allowance and tiers above it. The rows metric is the one to model carefully: a table with a wide schema and frequent updates can consume an enormous row count even when the underlying business volume is small.

The self-hosted enterprise tier exists for organisations that cannot send data through a vendor. It is priced annually and the gap between it and cloud is substantial, so the decision is usually compliance-driven rather than cost-driven.

Where it breaks down

Connector quality is uneven. The most popular connectors are well maintained; the long tail is community-supported and can lag behind source API changes by months. A pipeline that silently stops syncing because a source changed an endpoint is the most common operational failure, and it fails quietly.

Running it yourself means owning the scheduler, the worker pool, the secrets store and the upgrade path. That is a real platform engineering job, not a weekend project, and teams consistently underestimate it.

What switching costs

Low at the data layer — the data lands in your warehouse, not in Airbyte. High at the configuration layer: connection definitions, schedules and transformation steps do not port to another tool.

Who should not use it

Teams without platform engineering capacity who also cannot use the cloud product. Self-hosting Airbyte is a commitment.

Sources

Airbyte public documentation, pricing page and connector catalogue, read October 2026.