Real-time
Two-way sync
Changes in CockroachDB or Starburst Enterprise instantly reflect in both systems. No stale data, no manual imports.
Database ⇄ Data warehouse
CockroachDB to Starburst Enterprise integration — real-time, two-way sync
Keep CockroachDB 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 CockroachDB and Starburst Enterprise
Connect CockroachDB 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 CockroachDB'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 CockroachDB where the services that read from it get them at normal query latency.
Stacksync covers both directions with one connection. Tables or collections in CockroachDB sync into Starburst Enterprise in real time, and result tables in Starburst Enterprise sync back into CockroachDB, with schema and type mapping between the two systems handled for you.
Common use cases
- Consolidate reads from multiple databases behind a single connection instead of maintaining one integration per source
- Write curated or reconciled results back to lakehouse tables through connectors that support inserts
- Consolidate data from several SaaS tools into one distributed SQL store that survives zone failures.
- Write application events from CockroachDB back to CRM fields to give go-to-market teams product context.
Serve warehouse results at database speed
Aggregates or model outputs computed in Starburst Enterprise sync into CockroachDB, 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 CockroachDB focused on its operational workload.
What you can sync between CockroachDB 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.
| CockroachDB objects | Starburst Enterprise objects | |
|---|---|---|
| Databases Logical containers a sync connects to, addressed like PostgreSQL databases. | Materialized views Precomputed results that make repeated sync reads cheaper. | |
| Schemas Namespaces within a database used to isolate synced tables from application tables. | Columns Typed per the Trino type system, mapped from each source's native types. | |
| Tables The core read/write target; rows sync bi-directionally with SaaS objects or other databases. | Catalogs Each catalog maps to a connector (Iceberg, Hive, PostgreSQL, and others) exposing an external source. | |
| Views Read-only projections used as curated sync sources. | Schemas Namespaces within a catalog, mirroring the underlying source's databases or schemas. | |
| Indexes Secondary indexes that keep sync lookup queries fast on key columns. | Tables Queryable relations; writes pass through to sources whose connectors support them. | |
| Sequences ID generators that matter when writes originate from an external system. | Views Engine-level SQL views used to shape federated data before syncing it out. |
What ships with CockroachDB ⇄ Starburst Enterprise
Connect CockroachDB and Starburst Enterprise for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every CockroachDB–Starburst Enterprise connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever CockroachDB 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 CockroachDB or Starburst Enterprise record.
Observability
Monitoring
Track your CockroachDB ⇄ 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 CockroachDB and Starburst Enterprise.
How the CockroachDB and Starburst Enterprise connectors work
CockroachDB
- Integration surface
- SQL wire protocol (PostgreSQL-compatible)
- Authentication
- Database credentials with TLS; client certificates or SCRAM password auth
- Change detection
- CDC via changefeeds, which stream row-level changes; polling as a fallback
- Capabilities
- read · write · CDC
- Rate limits
- No API rate limits in the SaaS sense; throughput is bounded by cluster capacity
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 CockroachDB 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.
- 01
Connect your apps
Authenticate CockroachDB 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.
CockroachDB
connected
Starburst Enterprise
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the CockroachDB 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.
objects · CockroachDB ⇄ Starburst EnterpriseCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
CockroachDB Starburst EnterpriseCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
CockroachDB and Starburst Enterprise integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between CockroachDB and Starburst Enterprise: authenticate both systems, choose the objects to sync (such as CockroachDB's Databases and Schemas), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both CockroachDB and Starburst Enterprise. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on CockroachDB: CDC via changefeeds, which stream row-level changes; polling as a fallback. 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: Views, Materialized views, Columns, Catalogs, plus custom fields where Starburst Enterprise exposes them. On the CockroachDB side: Views, Indexes, Sequences, Changefeeds. 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 CockroachDB 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 CockroachDB, where whatever reads from that database gets them without querying the warehouse.
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 CockroachDB and Starburst Enterprise.
Popular · 8 of 386
-
CockroachDB ⇄ Teradata Vantage -
CockroachDB ⇄ Tinybird -
CockroachDB ⇄ Vertica -
CockroachDB ⇄ Yellowbrick -
Starburst Enterprise ⇄ Oracle DB -
Starburst Enterprise ⇄ RavenDB -
Starburst Enterprise ⇄ Redis Enterprise -
Starburst Enterprise ⇄ SAP ASE (Sybase)
No integrations match .
