Real-time
Two-way sync
Changes in CockroachDB or DuckDB instantly reflect in both systems. No stale data, no manual imports.
Database
CockroachDB to DuckDB integration — real-time, two-way sync
Keep CockroachDB and DuckDB 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 CockroachDB and DuckDB
Keep CockroachDB and DuckDB 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 CockroachDB and DuckDB 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
- 01 Use changefeeds to propagate row changes from a multi-region cluster into a warehouse or search index.
- 02 Keep reference data consistent between CockroachDB and regional application databases.
- 03 Sync SaaS data to Parquet on object storage and query it with DuckDB without standing up a warehouse.
- 04 Push aggregates computed in DuckDB out to a CRM or business tools so analysis results reach operational systems.
Common sync patterns
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 CockroachDB and DuckDB
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.
| CockroachDB objects | DuckDB objects | How this pairing syncs | |
|---|---|---|---|
| Schemas Namespaces within a database used to isolate synced tables from application tables. | Schemas Namespaces within a database used to organize tables in sync outputs. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Tables The core read/write target; rows sync bi-directionally with SaaS objects or other databases. | Tables Columnar tables created via SQL; the destination for materialized sync data. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Views Read-only projections used as curated sync sources. | Views SQL views used to shape or filter data for downstream consumers. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Databases Logical containers a sync connects to, addressed like PostgreSQL databases. | Database files Single-file .duckdb databases that jobs read and write directly on disk or object storage. | Databases is specific to CockroachDB and Database files to DuckDB — each maps to any object or custom field on the other side. | |
| Indexes Secondary indexes that keep sync lookup queries fast on key columns. | External files (Parquet/CSV/JSON) Files DuckDB queries in place without loading, common as a sync interchange format. | Indexes is specific to CockroachDB and External files (Parquet/CSV/JSON) to DuckDB — each maps to any object or custom field on the other side. | |
| Sequences ID generators that matter when writes originate from an external system. | Attached databases Additional database files or external systems attached into one session for cross-source queries. | Sequences is specific to CockroachDB and Attached databases to DuckDB — each maps to any object or custom field on the other side. |
How changes propagate between CockroachDB and DuckDB
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
CockroachDB DuckDB Sub-second propagation
DetectionChanges in CockroachDB are captured at the source via change data capture — no polling loop against its API. CDC via changefeeds, which stream row-level changes.
DeliveryEach detected change is applied to DuckDB as a row-level write, with types converted between the two schemas.
DuckDB CockroachDB Interval-based propagation
DetectionStacksync polls DuckDB for changes on an incremental schedule, reading only records changed since the previous pass. Polling or full re-reads.
DeliveryEach detected change is applied to CockroachDB as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- CockroachDB: No API rate limits in the SaaS sense; throughput is bounded by cluster capacity.
- DuckDB: No API rate limits; throughput is bounded by local compute and I/O.
What ships with CockroachDB ⇄ DuckDB
Connect CockroachDB and DuckDB for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every CockroachDB–DuckDB connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever CockroachDB or DuckDB 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 CockroachDB or DuckDB record.
Observability
Monitoring
Track your CockroachDB ⇄ DuckDB sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between CockroachDB and DuckDB.
How the CockroachDB and DuckDB connectors work
CockroachDB
- Integration surface
- SQL wire protocol (PostgreSQL-compatible)
- Authentication
- Database credentials with TLS; client certificates or SCRAM password auth
- Change detection
- CDC via changefeeds, which stream row-level changes; polling as a fallback
- Capabilities
- read · write · CDC
- Rate limits
- No API rate limits in the SaaS sense; throughput is bounded by cluster capacity
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
How it works
How to connect CockroachDB to DuckDB — 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 CockroachDB and DuckDB with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
CockroachDB
connected
DuckDB
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the CockroachDB and DuckDB 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 · CockroachDB ⇄ DuckDBCustomers 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.
CockroachDB DuckDBCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
CockroachDB and DuckDB integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between CockroachDB and DuckDB: authenticate both systems, choose the objects to sync (such as CockroachDB's Schemas and Tables), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the CockroachDB side: Views, Indexes, Sequences, Changefeeds, plus custom fields where CockroachDB 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 CockroachDB and DuckDB: Migration with zero-downtime cutover; Shared reference data between services; Regional or environment copies. When one database is replacing the other, sync both directions during the transition and switch traffic when ready, without a freeze window.
-
CockroachDB: SQL wire protocol (PostgreSQL-compatible). Authentication: Database credentials with TLS; client certificates or SCRAM password auth. 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). Stacksync manages authentication, retries, and rate limits on both sides.
-
CockroachDB: Multi-region clusters let operators pin table data to specific regions while keeping a single logical database. 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 CockroachDB and DuckDB without custom code.
SECURITY
Security teams trust 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
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 385 integrations available for CockroachDB and DuckDB.
Popular · 3 of 385
No integrations match .
