Two-way sync
Changes in Elasticsearch or Starburst Enterprise instantly reflect in both systems. No stale data, no manual imports.
Keep Elasticsearch 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 Elasticsearch'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 Elasticsearch where the services that read from it get them at normal query latency.
Stacksync covers both directions with one connection. Tables or collections in Elasticsearch sync into Starburst Enterprise in real time, and result tables in Starburst Enterprise sync back into Elasticsearch, with schema and type mapping between the two systems handled for you.
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 Elasticsearch focused on its operational workload.
Rows from Elasticsearch land in Starburst Enterprise as they change, replacing hand-built CDC and batch extract jobs.
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.
| Elasticsearch objects | Starburst Enterprise objects | |
|---|---|---|
| Index mappings Field type definitions that determine how synced fields are indexed and queried. | Views Engine-level SQL views used to shape federated data before syncing it out. | |
| Aliases Stable read/write names that let a sync cut over between index versions without downtime. | Materialized views Precomputed results that make repeated sync reads cheaper. | |
| Data streams Append-only targets for time-series or event data pushed from source systems. | Columns Typed per the Trino type system, mapped from each source's native types. | |
| Ingest pipelines Server-side transforms applied to documents as a sync writes them. | Catalogs Each catalog maps to a connector (Iceberg, Hive, PostgreSQL, and others) exposing an external source. | |
| Index templates Reusable settings and mappings applied automatically to new indices a sync creates. | Schemas Namespaces within a catalog, mirroring the underlying source's databases or schemas. | |
| Indices Target containers for synced records; each holds a table-like collection of JSON documents. | Tables Queryable relations; writes pass through to sources whose connectors support them. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Elasticsearch–Starburst Enterprise connection.
Changes in Elasticsearch or Starburst Enterprise instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Elasticsearch 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 Elasticsearch or Starburst Enterprise record.
Track your Elasticsearch ⇄ Starburst Enterprise sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Elasticsearch 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 Elasticsearch 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 Elasticsearch 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 Elasticsearch and Starburst Enterprise: authenticate both systems, choose the objects to sync (such as Elasticsearch's Index mappings and Aliases), map fields visually, and changes propagate both ways in milliseconds — no code required.
Starburst Enterprise: A single SQL statement can join tables across catalogs, meaning one query can span several distinct backend systems. Elasticsearch: Writes are addressed by document _id, so upserts map directly onto the index API, and the _bulk endpoint batches many operations in a single request. Stacksync's field mapping accounts for these differences between Elasticsearch 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 Elasticsearch 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 Elasticsearch and Starburst Enterprise connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Elasticsearch–Starburst Enterprise integration in-house.
Yes — Stacksync ships production-grade connectors for both Elasticsearch and Starburst Enterprise. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Elasticsearch: Polling on timestamp or sequence fields; Elasticsearch does not expose a native change feed or webhooks. 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.
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 Elasticsearch and Starburst Enterprise.