---
title: "Airbyte"
description: "Airbyte is an open-source data integration platform, available self-hosted or as a managed cloud service, that moves data from hundreds of sources into a destination using a large catalog of connectors."
canonical: "https://motherduck.com/glossary/airbyte/"
related:
  - title: "Airbyte + MotherDuck Integration | DuckDB Analytics"
    url: "https://motherduck.com/ecosystem/airbyte/"
  - title: "DuckLake Architecture Deep Dive"
    url: "https://motherduck.com/blog/ducklake-architecture-deep-dive/"
  - title: "Airbyte | MotherDuck Docs"
    url: "https://motherduck.com/docs/integrations/ingestion/airbyte/"
gated_asset:
  title: "DuckLake on MotherDuck"
  url: "https://motherduck.com/product/ducklake/"
---

# Airbyte

> Airbyte is an open-source data integration platform, available self-hosted or as a managed cloud service, that moves data from hundreds of sources into a destination using a large catalog of connectors.

## Overview

Airbyte is a data integration (ELT) platform built around an open-source core and a large, community-extendable catalog of connectors. It positions itself as an open alternative to closed, proprietary ELT vendors: the connector framework and most connectors are open source, and teams can self-host Airbyte or use Airbyte Cloud, the managed offering. Airbyte provides the **Connector Development Kit (CDK)**, a framework for building new connectors (including low-code and no-code builder options), which is a major driver of the size of its connector catalog compared to closed platforms.

<glossary-callout video="agentic-data-engineering-pipelines-ai" />

## How it works

- **Source connector**: extracts data from a system (database, SaaS API, file store, event stream).
- **Destination connector**: loads that data into a target system (data warehouse, lake, or database). Airbyte maintains an official DuckDB destination connector, which writes data either to a local DuckDB file or to a MotherDuck-hosted database by supplying an `md:` connection string in the destination configuration.
- **Connection**: pairs a source and destination with a sync schedule and mode (full refresh, incremental, with or without deletion detection).
- **Airbyte Protocol**: the underlying spec connectors implement to communicate records, state, and schema information, similar in spirit to (and influenced by) the Singer specification.

## Example: syncing to DuckDB/MotherDuck

A connection configured with a DuckDB destination and an `md:<token>` style connection string in `destination_path` lands synced records directly in a MotherDuck database, which can then be queried immediately:

```sql
SELECT source, COUNT(*)
FROM airbyte_internal.raw_orders
GROUP BY source;
```

## Why it matters

Airbyte's open-source model gives teams the option to self-host for cost or data-residency reasons, and to build or modify connectors when an off-the-shelf integration doesn't exist or needs customization — something not possible with fully closed platforms. The tradeoff is that self-hosting requires operating the Airbyte infrastructure (or paying for Airbyte Cloud), whereas fully managed vendors remove that operational burden entirely.