Two-way sync
Changes in DuckDB or Starburst Enterprise instantly reflect in both systems. No stale data, no manual imports.
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.
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.
Aggregates or model outputs computed in Starburst Enterprise sync into DuckDB, where whatever reads from that database gets them without querying the warehouse.
Because changes stream continuously, analysts query current data instead of waiting for last night's load.
Point analytical queries at the synced copy in Starburst Enterprise and keep DuckDB focused on its operational workload.
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. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every DuckDB–Starburst Enterprise connection.
Changes in DuckDB or Starburst Enterprise instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever DuckDB or Starburst Enterprise data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single DuckDB or Starburst Enterprise record.
Track your DuckDB ⇄ Starburst Enterprise sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between DuckDB and Starburst Enterprise.
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 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.
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.
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 DuckDB and Starburst Enterprise: authenticate both systems, choose the objects to sync (such as DuckDB's External files (Parquet/CSV/JSON) and Attached databases), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on DuckDB: Polling or full re-reads; no change feed or transaction log API. On Starburst Enterprise: Query-based polling; Starburst is a query engine and exposes no change log of its own. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Starburst Enterprise side: Schemas, Tables, Views, Materialized views, plus custom fields where Starburst Enterprise exposes them. On the DuckDB side: Database files, Schemas, Tables, Views. 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 DuckDB and Starburst Enterprise: Serve warehouse results at database speed; Fresh analytics without loading windows; Offload heavy reads. Aggregates or model outputs computed in Starburst Enterprise sync into DuckDB, where whatever reads from that database gets them without querying the warehouse.
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). Starburst Enterprise: ANSI SQL over JDBC/ODBC drivers and the Trino client REST protocol. Authentication: Deployment-dependent: username/password, LDAP, OAuth 2.0, or Kerberos. Stacksync manages authentication, retries, and rate limits on both sides.
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 DuckDB and Starburst Enterprise.