Two-way sync
Changes in MotherDuck or Supabase instantly reflect in both systems. No stale data, no manual imports.
Keep MotherDuck and Supabase 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 Supabase'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 Supabase where the services that read from it get them at normal query latency.
Stacksync covers both directions with one connection. Tables or collections in Supabase sync into MotherDuck in real time, and result tables in MotherDuck sync back into Supabase, with schema and type mapping between the two systems handled for you.
Point analytical queries at the synced copy in MotherDuck and keep Supabase focused on its operational workload.
Rows from Supabase land in MotherDuck as they change, replacing hand-built CDC and batch extract jobs.
Aggregates or model outputs computed in MotherDuck sync into Supabase, where whatever reads from that database gets them without querying the warehouse.
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 | Supabase objects | |
|---|---|---|
| Attached Local DuckDB Databases Local files attached alongside cloud databases for hybrid queries. | Schemas Namespaces (public and custom) that scope sync access. | |
| Databases Cloud-hosted DuckDB databases that scope a sync's reads and writes. | auth.users Managed authentication users, often mirrored into CRM or support systems. | |
| Schemas Namespaces within a database used to organize synced tables. | Row Level Security Policies Row-level access rules that govern what the REST layer exposes. | |
| Tables The main landing target for synced records and source for analysis. | JSONB Columns Semi-structured payloads such as event properties or nested objects. | |
| Views Modeled projections used as outbound sync sources. | Database Functions Postgres functions that can transform or validate synced rows. | |
| Database Shares Read-only copies of a database shared with other users or teams. | Storage Object Metadata File metadata rows that can be joined to synced application data. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every MotherDuck–Supabase connection.
Changes in MotherDuck or Supabase instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever MotherDuck or Supabase 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 Supabase record.
Track your MotherDuck ⇄ Supabase sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between MotherDuck and Supabase.
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 Supabase 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 Supabase 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 Supabase: authenticate both systems, choose the objects to sync (such as MotherDuck's Attached Local DuckDB Databases and Databases), map fields visually, and changes propagate both ways in milliseconds — no code required.
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. Supabase: Direct PostgreSQL wire protocol connection, plus an auto-generated REST API (PostgREST). Authentication: Database credentials (connection string) for SQL access; API keys (anon / service role) for the REST layer. Stacksync manages authentication, retries, and rate limits on both sides.
MotherDuck: Hybrid execution can split a query between the local DuckDB process and cloud compute. Supabase: Every Supabase project is a full PostgreSQL database, so standard Postgres drivers, SQL tooling, and log-based CDC apply directly. Stacksync's field mapping accounts for these differences between MotherDuck and Supabase without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means MotherDuck and Supabase records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed MotherDuck and Supabase connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom MotherDuck–Supabase integration in-house.
Yes — Stacksync ships production-grade connectors for both MotherDuck and Supabase. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
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 Supabase.