Stream data from Ashby to MotherDuck
Move data from Ashby to MotherDuck in minutes using Estuary. Stream, batch, or continuously sync data with control over latency from sub-second to batch.
- No credit card required
- 30-day free trial


- 200+Of connectors
- 5500+Active users
- <100msEnd-to-end latency
- 7+GB/secSingle dataflow
How to integrate Ashby with MotherDuck in 3 simple steps
Connect Ashby as your data source
Set up a source connector for Ashby in minutes. Estuary supports streaming (including CDC where available) and batch data capture through events, incremental syncs, or snapshots — without custom pipelines, agents, or manual configuration.
Configure MotherDuck as your destination connector
Estuary supports intelligent schema handling, with schema inference and evolution tools that help align source and destination structures over time. It supports both batch and streaming data movement, reliably delivering data to MotherDuck.
Deploy and Monitor Your End-to-End Data Pipeline
Launch your pipeline and monitor it from a single UI. Estuary guarantees exactly-once delivery, handles backfills and replays, and scales with your data — without engineering overhead.

Ashby connector details
The Ashby source connector brings recruiting and hiring data from Ashby into Estuary collections using incremental synchronization. All supported resources leverage Ashby’s sync token mechanism, ensuring efficient change tracking without repeated full refreshes. It supports a wide range of hiring workflow entities, including candidates, applications, interviews, jobs, offers, and organizational metadata, enabling complete pipeline visibility for talent analytics.
- Incremental sync for all resources using Ashby sync tokens
- Captures candidates, applications, interviews, jobs, offers, and metadata
- API key authentication with scoped access control
- Automatic omission of resources without required scopes
- Configurable sync intervals per resource for controlled ingestion cadence

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

See how Surface Ventures uses MotherDuck
Estuary in action
See how to build end-to-end pipelines using no-code connectors in minutes. Estuary does the rest.
Spend 2-5x less
Estuary customers not only do 4x more. They also spend 2-5x less on ETL and ELT. Estuary's unique ability to mix and match streaming and batch loading has also helped customers save as much as 40% on data warehouse compute costs.

Ashby to MotherDuck pricing estimate
Estimated monthly cost to move 800 GB from Ashby to MotherDuck is approximately $1,000.
Data moved
Choose how much data you want to move from Ashby to MotherDuck each month.
GB
Choose number of sources and destinations.
Why pay more?
Move the same data for a fraction of the cost.



What customers are saying
Getting started with Estuary
Free account
Getting started with Estuary is simple. Sign up for a free account.
Sign upDocs
Make sure you read through the documentation, especially the get started section.
Learn moreCommunity
Join the Slack community for the easiest way to get support while getting started.
Join Slack CommunityEstuary 101
Watch the Estuary 101 webinar for a guided introduction to using Estuary.
Watch

Frequently Asked Questions
Is this integration suitable for production workloads?
Yes. Estuary pipelines are designed for production use, with exactly-once delivery semantics, automated backfills, and continuous operation at scale.
Can I control where my data runs and is processed?
Yes. Estuary offers multiple deployment options, including fully managed SaaS, private deployments, and bring-your-own-cloud (BYOC). This allows teams to control where their data plane runs and meet security, compliance, and networking requirements. Learn more about Estuary's security and deployment options.
Can I build this Ashby to MotherDuck integration manually?
Yes, it's possible to build a manual pipeline using custom scripts, scheduled jobs, or open-source tools. However, manual approaches typically require ongoing maintenance, custom error handling, schema management, and operational overhead. Estuary simplifies this by providing a managed pipeline with built-in reliability, scaling, and monitoring.
Related articles
MotherduckBuilding an AI-Ready Air Quality Analytics Pipeline with Estuary and MotherDuck

MotherduckPostgres to MotherDuck: Stream Real-Time Analytics with CDC

MotherduckSnowflake to Motherduck: 2 Methods to Stream Your Data

MotherduckWhat is DuckLake? The New Open Table Format Explained

MotherduckHow to Load Streaming Data into DuckLake with Estuary

MotherduckOffloading BigQuery Workloads to MotherDuck for Faster and Affordable Analytics

DataOps made simple
Add advanced capabilities like schema inference and evolution with a few clicks. Or automate your data pipeline and integrate into your existing DataOps using Estuary's rich CLI.





































