Skip to content
Database

Connect DuckDB to any app with two-way sync.

Two-way sync DuckDB across all your CRMs, databases, data warehouses, EDI systems, and AI tools, with custom workflows tailored to your data.

  • 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
Object catalog

What Stacksync syncs in DuckDB.

These objects sync between DuckDB and any connected system, with field-level mapping and conflict resolution. Custom fields are picked up from the live schema where DuckDB exposes them.

Database files
Single-file .duckdb databases that jobs read and write directly on disk or object storage.
Schemas
Namespaces within a database used to organize tables in sync outputs.
Tables
Columnar tables created via SQL; the destination for materialized sync data.
Views
SQL views used to shape or filter data for downstream consumers.
External files (Parquet/CSV/JSON)
Files DuckDB queries in place without loading, common as a sync interchange format.
Attached databases
Additional database files or external systems attached into one session for cross-source queries.
API surface

How Stacksync connects to DuckDB.

The connector runs on DuckDB's native API. Stacksync manages authentication, rate limits, retries, and schema changes so your team does not maintain integration code.

Connection
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
Rate limits
No API rate limits; throughput is bounded by local compute and I/O

Sync directions

  • Read Supported
  • Write Supported
  • Change data capture Not available
  • Webhooks Not available
What ships with DuckDB

Connect DuckDB for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every connection.

Real-time

Two-way sync

Changes in DuckDB instantly reflect across connected systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever 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 DuckDB record.

Observability

Monitoring

Track your DuckDB sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions.

Use cases

What teams run on the DuckDB connector.

DuckDB is adopted by data engineers, analytics engineers, and software engineers as an in-process OLAP engine: SQL runs inside the application via client libraries, with no server to operate. The project positions it around simplicity, speed, and openness (MIT license), querying Parquet, CSV, JSON, Iceberg, and Delta files in place. Data gravity is deliberately low - it usually queries External files where they live or holds working Tables in a single database file inside a pipeline, notebook, or embedded app.

  • Data engineering
  • Analytics engineering
  • Software engineers
  • Data scientists
  1. Materialize warehouse or Postgres data into DuckDB files for local analytics, notebooks, and CI test fixtures.

  2. Use DuckDB as a transform step: read synced Parquet exports, aggregate with SQL, and write results back to an operational database.

  3. Sync SaaS data to Parquet on object storage and query it with DuckDB without standing up a warehouse.

  4. Push aggregates computed in DuckDB out to a CRM or business tools so analysis results reach operational systems.

  5. Hydrate Tables in a DuckDB database file with operational records so local analytics, tests, or an embedded app query fresh data without a warehouse.

  6. Publish the results of DuckDB transformations - Tables or Views - back to operational systems once a pipeline run completes.

All DuckDB integrations

Pick the system you need to keep in sync with DuckDB. Each page covers the sync setup, field mapping, and common workflows for that pair.

How it works

Set up DuckDB in minutes, without APIs.

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.

  1. 01

    Connect your apps

    Authenticate DuckDB with its native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    DuckDB connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the DuckDB objects to sync — Stacksync auto-detects the schema, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · DuckDB
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    DuckDB database
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp

FAQ

DuckDB connector FAQ

What can I sync with the DuckDB connector?

DuckDB's core objects — Database files, Schemas, Tables, Views and custom fields — can sync with any of 302 other systems. Every integration is real-time and bidirectional, with field-level mapping and conflict resolution.

How does Stacksync connect to DuckDB?

Via In-process SQL engine via client libraries (Python, Node.js, JDBC, CLI); no server or network API by default, authenticated with None built in; access control is file-system level (MotherDuck adds token auth for its hosted service). Changes are detected as follows — polling or full re-reads; no change feed or transaction log API. Stacksync manages rate limits, retries, and schema changes automatically.

Is the DuckDB connector two-way?

Yes. Changes made in DuckDB propagate to the connected system and vice versa, in milliseconds. One-way flows are also supported when a direction should stay read-only.

How long does a DuckDB integration take to set up?

Most DuckDB integrations go live in minutes: authenticate DuckDB and the other system, pick objects and fields, and enable the sync. No code and no infrastructure to manage.

Is DuckDB data secure in transit?

Stacksync is SOC 2 Type II, ISO 27001, GDPR and HIPAA compliant. DuckDB data is encrypted in transit, and a zero-persistent-storage architecture means records are not retained after a sync operation.

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:

Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.