Two-way sync
Changes in OpenSearch or Starburst Enterprise instantly reflect in both systems. No stale data, no manual imports.
Keep OpenSearch 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 OpenSearch'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 OpenSearch where the services that read from it get them at normal query latency.
Stacksync covers both directions with one connection. Tables or collections in OpenSearch sync into Starburst Enterprise in real time, and result tables in Starburst Enterprise sync back into OpenSearch, with schema and type mapping between the two systems handled for you.
Point analytical queries at the synced copy in Starburst Enterprise and keep OpenSearch focused on its operational workload.
Rows from OpenSearch 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 OpenSearch, 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.
| OpenSearch objects | Starburst Enterprise objects | |
|---|---|---|
| Data streams Append-oriented time-series storage for logs and events pushed from source systems | Schemas Namespaces within a catalog, mirroring the underlying source's databases or schemas. | |
| Snapshots Backup artifacts, relevant when reseeding an index from a repository | Tables Queryable relations; writes pass through to sources whose connectors support them. | |
| Indexes The core container; synced records land in indexes with defined mappings | Views Engine-level SQL views used to shape federated data before syncing it out. | |
| Documents JSON records written via the index and bulk APIs and read via search queries | Materialized views Precomputed results that make repeated sync reads cheaper. | |
| Index aliases Stable names over rotating indexes, used for zero-downtime reindex during backfills | Columns Typed per the Trino type system, mapped from each source's native types. | |
| Index templates Mapping and settings presets applied to new indexes a sync creates | 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 OpenSearch–Starburst Enterprise connection.
Changes in OpenSearch or Starburst Enterprise instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever OpenSearch 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 OpenSearch or Starburst Enterprise record.
Track your OpenSearch ⇄ Starburst Enterprise sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between OpenSearch 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 OpenSearch 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 OpenSearch 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 OpenSearch and Starburst Enterprise: authenticate both systems, choose the objects to sync (such as OpenSearch's Data streams and Snapshots), map fields visually, and changes propagate both ways in milliseconds — no code required.
OpenSearch: REST API over HTTP(S) with JSON payloads. Authentication: Basic authentication with the security plugin, or AWS IAM request signing on Amazon OpenSearch Service. 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. OpenSearch: Amazon OpenSearch Service domains typically authenticate with IAM request signing, while self-managed clusters use the security plugin's basic auth or certificates. Stacksync's field mapping accounts for these differences between OpenSearch 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 OpenSearch 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 OpenSearch and Starburst Enterprise connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom OpenSearch–Starburst Enterprise integration in-house.
Yes — Stacksync ships production-grade connectors for both OpenSearch 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 OpenSearch and Starburst Enterprise.