Two-way sync
Changes in Citus or Starburst Enterprise instantly reflect in both systems. No stale data, no manual imports.
Keep Citus 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 Citus'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 Citus where the services that read from it get them at normal query latency.
Stacksync covers both directions with one connection. Tables or collections in Citus sync into Starburst Enterprise in real time, and result tables in Starburst Enterprise sync back into Citus, with schema and type mapping between the two systems handled for you.
Point analytical queries at the synced copy in Starburst Enterprise and keep Citus focused on its operational workload.
Rows from Citus land in Starburst Enterprise as they change, replacing hand-built CDC and batch extract jobs.
Aggregates or model outputs computed in Starburst Enterprise sync into Citus, where whatever reads from that database gets them without querying the warehouse.
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.
| Citus objects | Starburst Enterprise objects | |
|---|---|---|
| Schemas Standard Postgres namespaces used to scope what a sync user can read and write. | Schemas Namespaces within a catalog, mirroring the underlying source's databases or schemas. | |
| Views Curated projections over distributed data, often used as read-only sync sources. | Tables Queryable relations; writes pass through to sources whose connectors support them. | |
| Sequences Key generators that matter when external writes must not collide with application inserts. | Views Engine-level SQL views used to shape federated data before syncing it out. | |
| Distributed tables Tables sharded across worker nodes by a distribution column; the main sync target for large datasets. | Materialized views Precomputed results that make repeated sync reads cheaper. | |
| Reference tables Small lookup tables replicated to every node, synced like ordinary Postgres tables. | Columns Typed per the Trino type system, mapped from each source's native types. | |
| Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. | Catalogs Each catalog maps to a connector (Iceberg, Hive, PostgreSQL, and others) exposing an external source. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Citus–Starburst Enterprise connection.
Changes in Citus or Starburst Enterprise instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Citus 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 Citus or Starburst Enterprise record.
Track your Citus ⇄ Starburst Enterprise sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Citus 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 Citus 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 Citus 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 Citus and Starburst Enterprise: authenticate both systems, choose the objects to sync (such as Citus's Schemas and Views), map fields visually, and changes propagate both ways in milliseconds — no code required.
Citus: PostgreSQL wire protocol; any standard Postgres driver connects to the coordinator node. Authentication: Database credentials (standard PostgreSQL authentication; managed deployments add cloud IAM options). 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.
Starburst Enterprise: It is built on open-source Trino, so Trino drivers, clients, and SQL semantics apply. Citus: Because shard data lives on worker nodes, log-based CDC is more involved than on single-node Postgres and depends on the Citus version and hosting (including the Azure managed service). Stacksync's field mapping accounts for these differences between Citus and Starburst Enterprise without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Citus and Starburst Enterprise records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Citus and Starburst Enterprise connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Citus–Starburst Enterprise integration in-house.
Yes — Stacksync ships production-grade connectors for both Citus and Starburst Enterprise. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
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 Citus and Starburst Enterprise.