Two-way sync
Changes in Elasticsearch or MotherDuck instantly reflect in both systems. No stale data, no manual imports.
Keep Elasticsearch and MotherDuck 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 MotherDuck, 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 MotherDuck in real time, and result tables in MotherDuck 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 MotherDuck and keep Elasticsearch focused on its operational workload.
Rows from Elasticsearch land in MotherDuck 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 | MotherDuck objects | |
|---|---|---|
| Ingest pipelines Server-side transforms applied to documents as a sync writes them. | Database Shares Read-only copies of a database shared with other users or teams. | |
| Index templates Reusable settings and mappings applied automatically to new indices a sync creates. | Attached Local DuckDB Databases Local files attached alongside cloud databases for hybrid queries. | |
| Indices Target containers for synced records; each holds a table-like collection of JSON documents. | Databases Cloud-hosted DuckDB databases that scope a sync's reads and writes. | |
| Documents The unit of sync; JSON records created, updated, and deleted by _id. | Schemas Namespaces within a database used to organize synced tables. | |
| Index mappings Field type definitions that determine how synced fields are indexed and queried. | Tables The main landing target for synced records and source for analysis. | |
| Aliases Stable read/write names that let a sync cut over between index versions without downtime. | Views Modeled projections used as outbound sync sources. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Elasticsearch–MotherDuck connection.
Changes in Elasticsearch or MotherDuck instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Elasticsearch or MotherDuck 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 MotherDuck record.
Track your Elasticsearch ⇄ MotherDuck sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Elasticsearch and MotherDuck.
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 MotherDuck 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 MotherDuck 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 MotherDuck: authenticate both systems, choose the objects to sync (such as Elasticsearch's Ingest pipelines and Index templates), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on Elasticsearch: Polling on timestamp or sequence fields; Elasticsearch does not expose a native change feed or webhooks. On MotherDuck: Polling; no log-based CDC or webhook surface is exposed. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the MotherDuck side: Views, Database Shares, Attached Local DuckDB Databases, Databases, plus custom fields where MotherDuck exposes them. On the Elasticsearch side: Index templates, Indices, Documents, Index mappings. 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 Elasticsearch and MotherDuck: Fresh analytics without loading windows; Offload heavy reads; Operational data in the warehouse, minus the pipeline. Because changes stream continuously, analysts query current data instead of waiting for last night's load.
Elasticsearch: REST API (JSON over HTTP). Authentication: API keys or basic authentication; Elastic Cloud also issues service account tokens. MotherDuck: SQL through DuckDB clients and drivers using a MotherDuck (md:) connection. Authentication: Access token created in MotherDuck (Settings > General > Create Token), pasted into Stacksync; database name and schema configurable if not using defaults. 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 Elasticsearch and MotherDuck.