Skip to content
Database ⇄ Data warehouse

DuckDB to Starburst Enterprise integration — real-time, two-way sync

Keep DuckDB and Starburst Enterprise 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 Starburst Enterprise

Connect DuckDB and Starburst Enterprise with one live, two-way sync: operational rows flow into the warehouse, and computed results flow back where systems can read them fast.

Operational databases and analytical warehouses want the same data at different moments. Analysts want DuckDB's rows in Starburst Enterprise, 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 DuckDB where the services that read from it get them at normal query latency.

Stacksync covers both directions with one connection. Tables or collections in DuckDB sync into Starburst Enterprise in real time, and result tables in Starburst Enterprise sync back into DuckDB, with schema and type mapping between the two systems handled for you.

Common use cases

  • Write curated or reconciled results back to lakehouse tables through connectors that support inserts
  • Read federated views that join warehouse, lake, and database tables, then sync the result into operational tools like a CRM
  • Sync SaaS data to Parquet on object storage and query it with DuckDB without standing up a warehouse.
  • Push aggregates computed in DuckDB out to a CRM or business tools so analysis results reach operational systems.

Serve warehouse results at database speed

Aggregates or model outputs computed in Starburst Enterprise sync into DuckDB, where whatever reads from that database gets them without querying the warehouse.

Fresh analytics without loading windows

Because changes stream continuously, analysts query current data instead of waiting for last night's load.

Offload heavy reads

Point analytical queries at the synced copy in Starburst Enterprise and keep DuckDB focused on its operational workload.

What you can sync between DuckDB and Starburst Enterprise

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 Starburst Enterprise objects
External files (Parquet/CSV/JSON) Files DuckDB queries in place without loading, common as a sync interchange format. Columns Typed per the Trino type system, mapped from each source's native types.
Attached databases Additional database files or external systems attached into one session for cross-source queries. Catalogs Each catalog maps to a connector (Iceberg, Hive, PostgreSQL, and others) exposing an external source.
Database files Single-file .duckdb databases that jobs read and write directly on disk or object storage. Schemas Namespaces within a catalog, mirroring the underlying source's databases or schemas.
Schemas Namespaces within a database used to organize tables in sync outputs. Tables Queryable relations; writes pass through to sources whose connectors support them.
Tables Columnar tables created via SQL; the destination for materialized sync data. Views Engine-level SQL views used to shape federated data before syncing it out.
Views SQL views used to shape or filter data for downstream consumers. Materialized views Precomputed results that make repeated sync reads cheaper.
What ships with DuckDB ⇄ Starburst Enterprise

Connect DuckDB and Starburst Enterprise for flexible, real-time data sync.

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

Real-time

Two-way sync

Changes in DuckDB or Starburst Enterprise instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your DuckDB ⇄ Starburst Enterprise 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 Starburst Enterprise.

How the DuckDB and Starburst Enterprise 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

Starburst Enterprise

Integration surface
ANSI SQL over JDBC/ODBC drivers and the Trino client REST protocol
Authentication
Deployment-dependent: username/password, LDAP, OAuth 2.0, or Kerberos
Change detection
Query-based polling; Starburst is a query engine and exposes no change log of its own
Capabilities
read · write
Rate limits
Throughput is governed by cluster sizing and resource groups rather than API quotas
How it works

How to connect DuckDB to Starburst Enterprise — 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.

  1. 01

    Connect your apps

    Authenticate DuckDB and Starburst Enterprise with each platform's 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
    Starburst Enterprise connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the DuckDB and Starburst Enterprise 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · DuckDB ⇄ Starburst Enterprise
    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 Starburst Enterprise
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

DuckDB and Starburst Enterprise integration FAQ

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 Starburst Enterprise.

Popular · 8 of 386
Coworkers laughing in front of a laptop in a casual office setting

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