Real-time
Two-way sync
Changes in DuckDB or Supabase instantly reflect in both systems. No stale data, no manual imports.
Database
DuckDB to Supabase integration — real-time, two-way sync
Keep DuckDB 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.
- SOC 2 and 6 other compliance frameworks
- POC with real engineers in minutes
Adopted by fast-scaling companies moving mission-critical data in real time
Case study
Migrated from Mulesoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect DuckDB and Supabase
Keep DuckDB and Supabase synchronized in real time, across engines, regions, or services, in one or both directions.
Two databases that must agree is one of the oldest problems in engineering: different engines for different workloads, separate services with overlapping reference data, a migration in flight, or regional instances that share a subset of records. Hand-rolled replication across systems means change capture, conflict handling, and type mapping, all built and maintained by your team.
Stacksync syncs tables or collections between DuckDB and Supabase continuously and bi-directionally, translating types between the two engines and resolving conflicts by rules you configure. Rows written on either side appear on the other within seconds.
Common use cases
- Push aggregates computed in DuckDB out to a CRM or business tools so analysis results reach operational systems.
- Use DuckDB as a transform step: read synced Parquet exports, aggregate with SQL, and write results back to an operational database.
- Consolidate Supabase project data into a warehouse for analytics while keeping the app database as the system of record
- Sync application tables in Supabase with the CRM two-way so new signups appear as contacts and sales edits flow back to the app
Migration with zero-downtime cutover
When one database is replacing the other, sync both directions during the transition and switch traffic when ready, without a freeze window.
Shared reference data between services
Services that own separate databases stay consistent on the records they share, without a custom replication layer.
Regional or environment copies
Mirror selected tables to another region or environment continuously, filtered to just the rows that should travel.
What you can sync between DuckDB and Supabase
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 | Supabase objects | |
|---|---|---|
| Tables Columnar tables created via SQL; the destination for materialized sync data. | auth.users Managed authentication users, often mirrored into CRM or support systems. | |
| Views SQL views used to shape or filter data for downstream consumers. | Row Level Security Policies Row-level access rules that govern what the REST layer exposes. | |
| External files (Parquet/CSV/JSON) Files DuckDB queries in place without loading, common as a sync interchange format. | JSONB Columns Semi-structured payloads such as event properties or nested objects. | |
| Attached databases Additional database files or external systems attached into one session for cross-source queries. | Database Functions Postgres functions that can transform or validate synced rows. | |
| Database files Single-file .duckdb databases that jobs read and write directly on disk or object storage. | Storage Object Metadata File metadata rows that can be joined to synced application data. | |
| Schemas Namespaces within a database used to organize tables in sync outputs. | Tables Standard Postgres tables; the primary two-way sync target. |
What ships with DuckDB ⇄ Supabase
Connect DuckDB and Supabase for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every DuckDB–Supabase connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever DuckDB or Supabase data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
At scale
Event queues
Handle millions of events per minute without losing a single DuckDB or Supabase record.
Observability
Monitoring
Track your DuckDB ⇄ Supabase sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between DuckDB and Supabase.
How the DuckDB and Supabase connectors work
DuckDB
- Integration surface
- 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)
- Change detection
- Polling or full re-reads; no change feed or transaction log API
- Capabilities
- read · write
- Rate limits
- No API rate limits; throughput is bounded by local compute and I/O
Supabase
- Integration surface
- 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
- Change detection
- Log-based CDC via Postgres logical replication, the same WAL feed that powers Supabase Realtime; database webhooks can also fire on row changes
- Capabilities
- read · write · CDC · webhooks
- Rate limits
- SQL access is bounded by connection limits (pooled connections are provided); the REST layer is subject to the platform's limits
How it works
How to connect DuckDB to Supabase — three steps, no code
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.
- 01
Connect your apps
Authenticate DuckDB 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.
DuckDB
connected
Supabase
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the DuckDB 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.
objects · DuckDB ⇄ SupabaseCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
DuckDB SupabaseCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
DuckDB and Supabase integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between DuckDB and Supabase: authenticate both systems, choose the objects to sync (such as DuckDB's Tables and Views), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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 DuckDB and Supabase records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed DuckDB and Supabase connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom DuckDB–Supabase integration in-house.
-
Yes — Stacksync ships production-grade connectors for both DuckDB and Supabase. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on DuckDB: Polling or full re-reads; no change feed or transaction log API. On Supabase: Log-based CDC via Postgres logical replication, the same WAL feed that powers Supabase Realtime; database webhooks can also fire on row changes. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the DuckDB side: Attached databases, Database files, Schemas, Tables, plus custom fields where DuckDB exposes them. On the Supabase side: Schemas, auth.users, Row Level Security Policies, JSONB Columns. Stacksync auto-detects both schemas and converts types between the two systems.
SECURITY
Security teams love Stacksync
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.
SOC 2 type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS
SSO & SCIM
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Alerts
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Secure connection options
Securely connects to your systems with:
Related integrations
Every pair below is a real-time, two-way sync. Search all 386 integrations available for DuckDB and Supabase.
Popular · 8 of 386
-
DuckDB ⇄ Azure SQL Database -
DuckDB ⇄ Citus -
DuckDB ⇄ Couchbase -
DuckDB ⇄ Elasticsearch -
Supabase ⇄ SingleStore -
Supabase ⇄ Amazon Aurora -
Supabase ⇄ Amazon Lightsail -
Supabase ⇄ Apache Cassandra
No integrations match .
