Airbyte is an open-source ELT platform for syncing data from sources to warehouses, lakes, and databases using connectors and CDC. It supports custom connectors, schema management, and both self-hosted and Airbyte Cloud deployment. Suited for engineering teams building reproducible data pipelines and integrations.
Use this profile to understand the building block briefly, place it in the model, and open related building blocks.
Usable application software: supports people in a task.
Concrete cog in the system that works inside larger relationships.
Airbyte is an open-source ELT platform that syncs data from many sources into warehouses, lakes, or databases through modular connectors, with CDC support for incremental transfers.
Airbyte was founded in San Francisco in January 2020 by Michel Tricot and John Lafleur. It emerged from the practical problem of connecting many source systems to different target systems in a repeatable way without building a separate integration for every pairing. The platform organizes connectors, ELT flows, and later cloud and self-hosted operation into reusable building blocks.
Think of Airbyte as an adapter layer between source systems and target systems. On the left are APIs, files, or databases; on the right are warehouses, lakes, or operational tools. A sync reads through a connector, writes to the destination, and can follow changes incrementally through CDC. Schema management reconciles structural changes, while status and logs show where a run is blocked.
Source systems are read in a controlled way and transferred into a target system instead of being tightly coupled directly.
A connector encapsulates access, authentication, and the concrete integration for a specific source or target system.
Change Data Capture moves only new or changed records and reduces full reloads.
Field names, data types, and structural changes are detected and mapped to the target schema.
Airbyte can be self-hosted or used as a cloud service; that shifts control, maintenance, and responsibility.
Airbyte is useful when data from many sources must flow reliably into analytical or operational targets and repeatable syncs matter more than one-off scripts. It is especially suitable for changing sources, incremental loading patterns, and a need for standardized connectors. Limits include connector quality, schema drift, CDC dependencies, and the extra operational effort of self-hosting.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.