MotherDuck + Bruin

SourceDestination

Ingest data from MotherDuck or push enriched data back — with quality checks, lineage, and scheduling. Defined in YAML, version-controlled in Git.

For business teams

What you get

100+ sources into ${pn}
Pull from any tool, database, or API directly into MotherDuck. One YAML file per source, all managed by Bruin.
Data quality you can trust
Column-level and custom SQL checks on any MotherDuck table. Bad data gets blocked before it reaches dashboards.
Full lineage visibility
Trace data from ingestion through transforms to final reports. When something breaks, find the cause in seconds.
SQL + Python in one pipeline
Build transforms in MotherDuck with both SQL and Python. Bruin resolves dependencies across languages automatically.

For data & engineering teams

How it works

100+ managed connectors
Ingest from any source directly into MotherDuck with one YAML file per source. Bruin manages connections and scheduling.
YAML-defined, Git-versioned
Every pipeline is a YAML file. Review in PRs, deploy with CI/CD, roll back with git revert.
SQL + Python assets
Build transformation layers in MotherDuck with SQL and Python. Bruin resolves dependencies and handles materialization.
Quality gates between stages
Quality checks run between ingestion and transformation. Bad data gets blocked before it reaches downstream models.

Before you start

MotherDuck account

Authentication token

Step 1

Add your MotherDuck connection

Connect using MotherDuck authentication token. Add this to your Bruin environment file — credentials are stored securely and referenced by name in your pipeline YAML.

Parameters

tokenMotherDuck authentication token

connections:
  motherduck:
    type: motherduck
    uri: "motherduck:///?token=<token>"

Step 2

Create your pipeline

Define a YAML asset that tells Bruin what to pull from MotherDuck and where to land it. This file lives in your Git repo — reviewable, version-controlled, and deployable with CI/CD.

name: raw.motherduck_data
type: ingestr

parameters:
  source_connection: motherduck
  source_table: 'data'
  destination: bigquery

Step 3

Add quality checks

Add column-level and custom SQL checks to your MotherDuck data. If a check fails, the pipeline stops — bad data never reaches downstream models or dashboards.

Validate data freshness on every sync

Ensure IDs are unique across tables

Block bad data before it reaches downstream models

columns:
  - name: id
    checks:
      - name: not_null
      - name: unique

custom_checks:
  - name: freshness check
    query: |
      SELECT MAX(updated_at) >
        TIMESTAMP_SUB(CURRENT_TIMESTAMP(), INTERVAL 24 HOUR)
      FROM raw.motherduck_data

Step 4

Run it

One command. Bruin connects to MotherDuck, pulls data incrementally, runs your quality checks, and lands clean data in your warehouse. If a check fails, the pipeline stops — bad data never reaches downstream.

Backfill historical data with --start-date

Schedule with cron or trigger from CI/CD

Full lineage from MotherDuck to your dashboards

$ bruin run .

Running pipeline...

  motherduck_data
    ✓ Fetched 2,847 new records
    ✓ Quality: campaign_id not_null     PASSED
    ✓ Quality: spend not_null           PASSED
    ✓ Quality: no negative ad spend     PASSED
    ✓ Loaded into bigquery

  Completed in 12s

Other Data Warehouse integrations

Amazon Redshift

AWS Athena

AWS EMR Serverless

Databricks

GCP Dataproc Serverless

Google BigQuery

Ready to connect MotherDuck?

Start for free, or book a demo to see how Bruin handles ingestion, quality, lineage, and scheduling for your entire data stack.

Book a demo Read the docs