Two-way sync
Changes in MotherDuck or Tinybird instantly reflect in both systems. No stale data, no manual imports.
Keep MotherDuck and Tinybird in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Companies end up with two warehouses for practical reasons: a migration in progress, teams that standardized on different platforms, an acquisition, or tools that only connect to one of them. The result is the same dataset maintained twice, with duplicated pipelines and numbers that almost match.
Stacksync syncs tables between MotherDuck and Tinybird continuously, in either or both directions. Rows changed on one platform appear on the other within seconds, with schema and type mapping handled, so both warehouses answer questions with the same data.
When one platform is replacing the other, keep tables mirrored while workloads move over gradually, and cut over with nothing to backfill.
Mirror the datasets a BI tool, notebook, or application needs onto the platform it can actually reach.
Where different teams run different warehouses, sync the curated tables both rely on so their metrics agree by construction.
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.
| MotherDuck objects | Tinybird objects | |
|---|---|---|
| Databases Cloud-hosted DuckDB databases that scope a sync's reads and writes. | Materialized Views Pipes materialized into new Data Sources for pre-aggregation at ingest time. | |
| Schemas Namespaces within a database used to organize synced tables. | Workspaces Project boundary that scopes Data Sources, Pipes, and tokens for a sync. | |
| Tables The main landing target for synced records and source for analysis. | Tokens Scoped credentials that control read and append rights per resource. | |
| Views Modeled projections used as outbound sync sources. | Data Sources ClickHouse-backed tables that receive ingested rows; the write target for syncs into Tinybird. | |
| Database Shares Read-only copies of a database shared with other users or teams. | Pipes Chained SQL nodes that transform Data Sources into query-ready results. | |
| Attached Local DuckDB Databases Local files attached alongside cloud databases for hybrid queries. | API Endpoints Published Pipe outputs exposed as parameterized HTTP queries; the main read surface. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every MotherDuck–Tinybird connection.
Changes in MotherDuck or Tinybird instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever MotherDuck or Tinybird data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single MotherDuck or Tinybird record.
Track your MotherDuck ⇄ Tinybird sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between MotherDuck and Tinybird.
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 MotherDuck and Tinybird 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 MotherDuck and Tinybird 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 MotherDuck and Tinybird: authenticate both systems, choose the objects to sync (such as MotherDuck's Databases and Schemas), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on MotherDuck: Polling; no log-based CDC or webhook surface is exposed. On Tinybird: Append-oriented ingestion; reads are pulled by querying published endpoints, no outbound CDC. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the MotherDuck side: Schemas, Tables, Views, Database Shares, plus custom fields where MotherDuck exposes them. On the Tinybird side: Pipes, API Endpoints, Materialized Views, Workspaces. 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 MotherDuck and Tinybird: Migration without a big bang; Serve tools that only connect to one platform; Shared datasets across teams. When one platform is replacing the other, keep tables mirrored while workloads move over gradually, and cut over with nothing to backfill.
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. Tinybird: REST API (Events API for ingestion, published query endpoints) with a ClickHouse SQL dialect. Authentication: Scoped auth tokens. Stacksync manages authentication, retries, and rate limits on both sides.
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 MotherDuck and Tinybird.