Airbyte is a data integration platform that syncs data from APIs, databases, and files into warehouses and lakes, available self-hosted or as a managed cloud service.
Self-hosted Airbyte runs as containers, typically on Kubernetes, with syncs scheduled in the platform or by cron and triggerable over the API, Terraform, and PyAirbyte. Airbyte Cloud is the managed option, billed by volume on Standard and by capacity on Pro. Loaded data lands raw, ready for a downstream transformation framework.
How Airbyte answers the questions Batch ELT turns on.
| How it works | |
| Authoring model | Web UI; also REST API, Terraform provider and PyAirbyte |
| Incremental sync | Incremental append or append+dedupe; log-based CDC on databases |
| Sync frequency | Manual, scheduled or cron; hourly floor on Cloud, 15 min on Pro |
| Schema drift | Detect and approve, or auto-propagate fields or whole streams |
| Running it | |
| Scheduling | Built in: scheduled or cron syncs, triggerable by API |
| Connections | |
| Source coverage | SaaS APIs, databases and files, from a large connector catalogue |
| Destinations | Warehouses, lakes, databases and object storage |
| Custom connectors | No-code Connector Builder, or the Python CDK |
| Transformations | Typing and deduping only; custom dbt removed, dbt Cloud on Cloud |
| Cost | |
| Billing unit | Volume on Standard; capacity via Data Workers on Pro |
vs Airbyte: Open source (permissive) · Self-hosted · Managed · Operational complexity: Low · Python
vs Airbyte: Managed · Self-hosted · Hybrid · Operational complexity: Low · Batch · Streaming · Rust
vs Airbyte: Commercial · Managed · Hybrid · Operational complexity: Low