MotherDuck integration

Your models, in MotherDuck.

A built-in ingestr destination: load modelled tables into MotherDuck.

name: out.motherduck
type: ingestr
parameters:
  source_connection: postgres
  source_table: analytics.daily_revenue
  destination: motherduck

$ bruin run assets/out/motherduck.asset.yml

  1. extract · postgres analytics.daily_revenue
  2. load · MotherDuckreplace

Delivered to MotherDuck.

How it connects

Connected in three steps.

Cloud-native data warehouse built on DuckDB, providing serverless analytics with the performance of DuckDB in a managed cloud environment.

  1. 01

    Add a MotherDuck connection.

  2. 02

    Point an ingestion asset at MotherDuck as its destination.

  3. 03

    Bruin loads it on your schedule and checks every load.

Connection parameters

token
MotherDuck authentication token

Every way MotherDuck works with Bruin

  • DestinationBuilt-in ingestr destinationDocs →
  • Query engineRuns SQL and Python assetsDocs →

The platform

Part of the Bruin platform.

Data in, ready for everything downstream: the models, the checks, the lineage and the AI layer.

Frequently asked

Questions about MotherDuck.

Does Bruin have a built-in MotherDuck integration?

Yes. Built-in ingestr destination. Runs SQL and Python assets.

How fresh is the data?

As fresh as your schedule. Incremental loads append, merge or replace a time window, every few minutes if you like.

Do we need Bruin Cloud?

No. The Bruin CLI and ingestr run locally, in CI or in your own orchestrator. Bruin Cloud adds scheduling, lineage, alerts and the AI data analyst on top.

Ready to connect MotherDuck?

$100 in credits and 50 AI tasks. No credit card.

A demo walks through your own data.

Sign up to our newsletter

Practical updates on open-source data pipelines, AI analysts, governance, and what we are shipping at Bruin.

The signup form is hosted by Brevo. Allow marketing cookies to load it.