Two-way sync
Changes in Starburst Enterprise or TimescaleDB instantly reflect in both systems. No stale data, no manual imports.
Keep Starburst Enterprise and TimescaleDB 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 TimescaleDB'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 TimescaleDB where the services that read from it get them at normal query latency.
Stacksync covers both directions with one connection. Tables or collections in TimescaleDB sync into Starburst Enterprise in real time, and result tables in Starburst Enterprise sync back into TimescaleDB, with schema and type mapping between the two systems handled for you.
Rows from TimescaleDB 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 TimescaleDB, 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.
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.
| Starburst Enterprise objects | TimescaleDB objects | |
|---|---|---|
| Materialized views Precomputed results that make repeated sync reads cheaper. | Schemas Postgres namespaces used to separate synced datasets by team or environment. | |
| Columns Typed per the Trino type system, mapped from each source's native types. | Hypertables Time-partitioned tables that hold the main time-series data; the primary read and write target in syncs. | |
| Catalogs Each catalog maps to a connector (Iceberg, Hive, PostgreSQL, and others) exposing an external source. | Chunks Time-bounded partitions of a hypertable; syncs read and write through the parent hypertable and never address chunks directly. | |
| Schemas Namespaces within a catalog, mirroring the underlying source's databases or schemas. | Continuous Aggregates Incrementally maintained rollups that serve as pre-aggregated read sources for downstream systems. | |
| Tables Queryable relations; writes pass through to sources whose connectors support them. | Regular PostgreSQL Tables Relational reference data such as devices, tenants, or accounts synced alongside the series data. | |
| Views Engine-level SQL views used to shape federated data before syncing it out. | Views Standard SQL views used to shape or filter data for consumers. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Starburst Enterprise–TimescaleDB connection.
Changes in Starburst Enterprise or TimescaleDB instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Starburst Enterprise or TimescaleDB data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Starburst Enterprise or TimescaleDB record.
Track your Starburst Enterprise ⇄ TimescaleDB sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Starburst Enterprise and TimescaleDB.
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 Starburst Enterprise and TimescaleDB 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 Starburst Enterprise and TimescaleDB 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 Starburst Enterprise and TimescaleDB: authenticate both systems, choose the objects to sync (such as Starburst Enterprise's Materialized views and Columns), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on Starburst Enterprise: Query-based polling; Starburst is a query engine and exposes no change log of its own. On TimescaleDB: Log-based capture via PostgreSQL logical decoding where the deployment allows it — hypertable changes surface on the underlying chunk tables and must be remapped to the parent — or timestamp-based polling on time columns; regular Postgres tables replicate through standard logical replication. 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: Views, Materialized views, Columns, Catalogs, plus custom fields where Starburst Enterprise exposes them. On the TimescaleDB side: Views, Schemas, Hypertables, Chunks. 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 Starburst Enterprise and TimescaleDB: Operational data in the warehouse, minus the pipeline; Serve warehouse results at database speed; Fresh analytics without loading windows. Rows from TimescaleDB land in Starburst Enterprise as they change, replacing hand-built CDC and batch extract jobs.
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. TimescaleDB: SQL wire protocol (PostgreSQL). Authentication: Database credentials. 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 Starburst Enterprise and TimescaleDB.