Two-way sync
Changes in ClickHouse or Starburst Enterprise instantly reflect in both systems. No stale data, no manual imports.
Keep ClickHouse 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.
Companies end up with two warehouses for practical reasons: a migration in progress, teams that standardized on different platforms, an acquisition, or tools that only connect to one of them. The result is the same dataset maintained twice, with duplicated pipelines and numbers that almost match.
Stacksync syncs tables between ClickHouse and Starburst Enterprise continuously, in either or both directions. Rows changed on one platform appear on the other within seconds, with schema and type mapping handled, so both warehouses answer questions with the same data.
Bring the acquired company's warehouse data across continuously instead of through one-off dumps.
When one platform is replacing the other, keep tables mirrored while workloads move over gradually, and cut over with nothing to backfill.
Mirror the datasets a BI tool, notebook, or application needs onto the platform it can actually reach.
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.
| ClickHouse objects | Starburst Enterprise objects | |
|---|---|---|
| Databases Namespaces that group tables and scope permissions for sync users. | Views Engine-level SQL views used to shape federated data before syncing it out. | |
| Views Saved queries used as curated, read-only sync sources. | Materialized views Precomputed results that make repeated sync reads cheaper. | |
| Materialized views Insert-time transformations that reshape incoming synced rows into aggregates. | Columns Typed per the Trino type system, mapped from each source's native types. | |
| Distributed tables Query-routing tables over cluster shards in self-managed deployments. | Catalogs Each catalog maps to a connector (Iceberg, Hive, PostgreSQL, and others) exposing an external source. | |
| Dictionaries In-memory lookup structures refreshed from external sources, sometimes fed by syncs. | Schemas Namespaces within a catalog, mirroring the underlying source's databases or schemas. | |
| Tables (MergeTree family) Columnar, append-optimized tables that serve as the destination for high-volume sync loads. | Tables Queryable relations; writes pass through to sources whose connectors support them. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every ClickHouse–Starburst Enterprise connection.
Changes in ClickHouse or Starburst Enterprise instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever ClickHouse 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 ClickHouse or Starburst Enterprise record.
Track your ClickHouse ⇄ Starburst Enterprise sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between ClickHouse 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 ClickHouse 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 ClickHouse 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 ClickHouse and Starburst Enterprise: authenticate both systems, choose the objects to sync (such as ClickHouse's Databases and Views), map fields visually, and changes propagate both ways in milliseconds — no code required.
On the ClickHouse side: Distributed tables, Dictionaries, Tables (MergeTree family), Databases, plus custom fields where ClickHouse exposes them. On the Starburst Enterprise side: Catalogs, 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 ClickHouse and Starburst Enterprise: Consolidation after M&A; Migration without a big bang; Serve tools that only connect to one platform. Bring the acquired company's warehouse data across continuously instead of through one-off dumps.
ClickHouse: Native TCP protocol and HTTP interface; standard SQL dialect, with MySQL and PostgreSQL wire compatibility available. Authentication: Database credentials (username/password); ClickHouse Cloud issues per-service credentials over TLS. 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.
ClickHouse: Storage is columnar and organized by the MergeTree engine family, which makes large batched inserts far more efficient than single-row writes. Starburst Enterprise: It is built on open-source Trino, so Trino drivers, clients, and SQL semantics apply. Stacksync's field mapping accounts for these differences between ClickHouse and Starburst Enterprise without custom code.
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 ClickHouse and Starburst Enterprise.