Estuary
WEBINARS
  • Estuary 101 Webinar
    Watch Estuary 101
PricingConnectors
SUCCESS STORIES
Together AI

See how Together AI built a near-real-time inference analytics pipeline in one week with Estuary.

Resend

Discover how Resend scaled their product analytics and cut costs by switching to Estuary.

Glossier

Glossier slashes data costs by 50% and unlocks real-time supply chain and marketing analytics with Estuary.

View all success stories
READ
Blog
Blog
Product Updates
Product Updates
Docs & Guides
About us
About us
Status
Status
The Right Time Data Manifesto
The Right Time Data Manifesto
LISTEN
Podcasts
Podcasts
Webinars
Webinars
Youtube
YouTube
Video Hub
Video Hub
DEMO
  • Estuary Demo
    Play Interactive Demo
  • Deploy CDC and Streaming ETL in Minutes Using Estuary
    Real-time 101 (30 min)
    Log inTry it Free
    Log inTry it Free

    Stream into MotherDuck with your free account

    Deliver data from databases, SaaS apps, APIs, files, and streaming systems into MotherDuck using Estuary's pre-built connectors. Run pipelines from real-time streaming to scheduled batch based on connector capabilities.

    • <100ms to batch
    • 200+ connectors
    • Managed data pipelines
    Try it freeWatch Demo
    01. Select a source02. Transform in-flight03. Deliver to MotherDuck
    MotherDuck logo
    take a tour
    MotherDuck logo

    MotherDuck connector details

    The MotherDuck connector from Estuary brings data collections into MotherDuck tables with cloud-native efficiency. Data is staged in Amazon S3 or Google Cloud Storage, then seamlessly loaded into MotherDuck for low-latency querying and analytics. By supporting both merge operations and delta updates, the connector makes it easy to power CDC pipelines while optimizing for cost and performance.

    • Materializes data collections into MotherDuck tables for real-time insights
    • Uses S3 or GCS as a scalable, temporary staging layer
    • Supports delta updates for CDC-style replication and merges for consistency
    • Flexible sync scheduling to balance freshness with resource usage
    • Secure integration with MotherDuck Service Token authentication
    Surface Ventures logo

    See how Surface Ventures uses MotherDuck

    For more details about the MotherDuck connector, check out the documentation page.

    How to connect your data source to MotherDuck in 3 easy steps

    1. 1

      Connect your data source

      Select from more than 100 supported databases and SaaS platforms including PostgreSQL, MySQL, SQL Server, MongoDB, and Kafka.

    2. 2

      Prepare and transform your data

      Apply transformations and schema mapping as data moves whether you are streaming in real time or loading in batches.

    3. 3

      Sync to MotherDuck

      Continuously or periodically deliver data into your destination with support for change data capture and reliable delivery for accurate insights.

    Learn more with some related videos

    Dive deeper into MotherDuck with tutorials and walkthroughs from our YouTube channel.

    Get Started Free

    Trusted by data teams worldwide

    All data connections are fully encrypted in transit and at rest. Estuary also supports private cloud and BYOC deployments for maximum security and compliance.

    4.8/5

    HIGH THROUGHPUT

    Distributed, event-driven architecture scales for demanding data workloads.

    DURABLE COLLECTIONS

    Store data as it moves so you can transform, replay, and deliver it downstream.

    FLEXIBLE LATENCY

    From <100ms CDC and real-time streaming to scheduled batch, depending on connector capabilities.

    From <100ms to batch

    Estuary supports CDC, real-time streaming, incremental syncs, and scheduled batch across its connector ecosystem. Bring data from databases, SaaS apps, APIs, files, and event streams into MotherDuck, with capture and delivery cadence based on connector capabilities and pipeline configuration.

    • Connect data from operational databases, SaaS applications, APIs, files, and streaming systems to MotherDuck through Estuary.
    • Transform and route data through Estuary collections before delivering it to MotherDuck.

    See what you can connect to MotherDuck:

    Details

    or choose from these popular data sources:

    PostgreSQL logo
    PostgreSQL
    MySQL logo
    MySQL
    SQL Server via CDC logo
    SQL Server via CDC
    MongoDB logo
    MongoDB
    Apache Kafka logo
    Apache Kafka
    BigQuery logo
    BigQuery
    Snowflake Data Cloud logo
    Snowflake Data Cloud

    Don't see a connector?Request and our team will get back to you in 24 hours

    Pipelines as fast as Kafka, easy as managed ELT/ETL, cheaper than building it.

    Feature Comparison

    EstuaryBatch ELT/ETLDIY PythonKafka
    Price$$$-$$$$$-$$$$$-$$$$
    Latency<100ms to scheduled5min+Varies<100ms
    EaseAnalysts can manageAnalysts can manageData EngineerSenior Data Engineer
    Scale
    Maintenance EffortLowMediumHighHigh

    One platform for real-time and batch data pipelines

    Detailed Comparison

    Deliver real-time and batch data from DBs, SaaS, APIs, and more

    Build Free PipelineJoin Our Slack Community
    Connection-1

    Popular sources/destinations you can sync your data with

    Choose from more than 100 supported databases and SaaS applications. Click any source/destination below to open the integration guide and learn how to sync your data in real time or batches.

    Frequently asked questions

      Do I need a staging bucket to load data into MotherDuck with Estuary?

      Yes. Estuary’s MotherDuck connector stages data in object storage before loading it into MotherDuck tables. You can use Amazon S3, Google Cloud Storage, Azure Blob Storage, or S3-compatible storage like Cloudflare R2. An S3 bucket in us-east-1 is recommended for the best performance and lowest costs, since MotherDuck is hosted in that region. See the MotherDuck connector documentation for full setup steps.

      Yes. Estuary continuously materializes your collections into MotherDuck tables as source data changes. You can also configure a sync schedule to batch updates at a set frequency, which helps control MotherDuck compute usage when sub-second freshness isn’t required.