Two-way sync
Changes in DuckDB or MotherDuck instantly reflect in both systems. No stale data, no manual imports.
Keep DuckDB and MotherDuck in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Operational databases and analytical warehouses want the same data at different moments. Analysts want DuckDB's rows in MotherDuck, current and joinable, without a change-data-capture pipeline to maintain. Engineers want the outputs of warehouse work, such as aggregates, features, and segments, available in DuckDB where the services that read from it get them at normal query latency.
Stacksync covers both directions with one connection. Tables or collections in DuckDB sync into MotherDuck in real time, and result tables in MotherDuck sync back into DuckDB, with schema and type mapping between the two systems handled for you.
Aggregates or model outputs computed in MotherDuck sync into DuckDB, where whatever reads from that database gets them without querying the warehouse.
Because changes stream continuously, analysts query current data instead of waiting for last night's load.
Point analytical queries at the synced copy in MotherDuck and keep DuckDB focused on its operational workload.
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| DuckDB objects | MotherDuck objects | |
|---|---|---|
| Database files Single-file .duckdb databases that jobs read and write directly on disk or object storage. | Databases Cloud-hosted DuckDB databases that scope a sync's reads and writes. | |
| Schemas Namespaces within a database used to organize tables in sync outputs. | Schemas Namespaces within a database used to organize synced tables. | |
| Tables Columnar tables created via SQL; the destination for materialized sync data. | Tables The main landing target for synced records and source for analysis. | |
| Views SQL views used to shape or filter data for downstream consumers. | Views Modeled projections used as outbound sync sources. | |
| External files (Parquet/CSV/JSON) Files DuckDB queries in place without loading, common as a sync interchange format. | Database Shares Read-only copies of a database shared with other users or teams. | |
| Attached databases Additional database files or external systems attached into one session for cross-source queries. | Attached Local DuckDB Databases Local files attached alongside cloud databases for hybrid queries. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every DuckDB–MotherDuck connection.
Changes in DuckDB or MotherDuck instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever DuckDB or MotherDuck data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single DuckDB or MotherDuck record.
Track your DuckDB ⇄ MotherDuck sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between DuckDB and MotherDuck.
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
Authenticate DuckDB and MotherDuck with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the DuckDB and MotherDuck objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between DuckDB and MotherDuck: authenticate both systems, choose the objects to sync (such as DuckDB's Database files and Schemas), map fields visually, and changes propagate both ways in milliseconds — no code required.
On the MotherDuck side: Views, Database Shares, Attached Local DuckDB Databases, Databases, plus custom fields where MotherDuck exposes them. On the DuckDB side: Tables, Views, External files (Parquet/CSV/JSON), Attached databases. Stacksync auto-detects both schemas and converts types between the two systems.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
Common patterns for DuckDB and MotherDuck: Serve warehouse results at database speed; Fresh analytics without loading windows; Offload heavy reads. Aggregates or model outputs computed in MotherDuck sync into DuckDB, where whatever reads from that database gets them without querying the warehouse.
DuckDB: In-process SQL engine via client libraries (Python, Node.js, JDBC, CLI); no server or network API by default. Authentication: None built in; access control is file-system level (MotherDuck adds token auth for its hosted service). MotherDuck: SQL through DuckDB clients and drivers using a MotherDuck (md:) connection. Authentication: Access token created in MotherDuck (Settings > General > Create Token), pasted into Stacksync; database name and schema configurable if not using defaults. Stacksync manages authentication, retries, and rate limits on both sides.
MotherDuck: MotherDuck is built on DuckDB, so integrations use DuckDB SQL and connect through standard DuckDB client libraries with an md: connection string. DuckDB: Execution is columnar and vectorized, optimized for analytical scans rather than high-frequency transactional writes. Stacksync's field mapping accounts for these differences between DuckDB and MotherDuck without custom code.
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 386 integrations available for DuckDB and MotherDuck.