Two-way sync
Changes in InterSystems IRIS or MotherDuck instantly reflect in both systems. No stale data, no manual imports.
Keep InterSystems IRIS 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 InterSystems IRIS'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 InterSystems IRIS where the services that read from it get them at normal query latency.
Stacksync covers both directions with one connection. Tables or collections in InterSystems IRIS sync into MotherDuck in real time, and result tables in MotherDuck sync back into InterSystems IRIS, with schema and type mapping between the two systems handled for you.
Rows from InterSystems IRIS land in MotherDuck as they change, replacing hand-built CDC and batch extract jobs.
Aggregates or model outputs computed in MotherDuck sync into InterSystems IRIS, 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.
| InterSystems IRIS objects | MotherDuck objects | |
|---|---|---|
| Persistent Classes Object-model classes project to tables, so class data is reachable through SQL. | Schemas Namespaces within a database used to organize synced tables. | |
| Globals The underlying multidimensional storage; typically accessed indirectly via SQL or objects in syncs. | Tables The main landing target for synced records and source for analysis. | |
| Namespaces Namespaces partition databases and determine the connection context for integrations. | Views Modeled projections used as outbound sync sources. | |
| Stored Procedures Server-side logic callable over SQL supports controlled writes and transformations. | Database Shares Read-only copies of a database shared with other users or teams. | |
| Tables Relational projections of stored data are the primary read/write surface for SQL-based syncs. | Attached Local DuckDB Databases Local files attached alongside cloud databases for hybrid queries. | |
| Views SQL views expose curated slices of data for outbound replication. | Databases Cloud-hosted DuckDB databases that scope a sync's reads and writes. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every InterSystems IRIS–MotherDuck connection.
Changes in InterSystems IRIS or MotherDuck instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever InterSystems IRIS 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 InterSystems IRIS or MotherDuck record.
Track your InterSystems IRIS ⇄ MotherDuck sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between InterSystems IRIS 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 InterSystems IRIS 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 InterSystems IRIS 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 InterSystems IRIS and MotherDuck: authenticate both systems, choose the objects to sync (such as InterSystems IRIS's Persistent Classes and Globals), map fields visually, and changes propagate both ways in milliseconds — no code required.
On the MotherDuck side: Database Shares, Attached Local DuckDB Databases, Databases, Schemas, plus custom fields where MotherDuck exposes them. On the InterSystems IRIS side: Namespaces, Stored Procedures, Tables, Views. 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 InterSystems IRIS and MotherDuck: Operational data in the warehouse, minus the pipeline; Serve warehouse results at database speed; Fresh analytics without loading windows. Rows from InterSystems IRIS land in MotherDuck as they change, replacing hand-built CDC and batch extract jobs.
InterSystems IRIS: SQL over JDBC/ODBC, plus object and REST access layers. Authentication: Database credentials. 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.
MotherDuck: MotherDuck is built on DuckDB, so integrations use DuckDB SQL and connect through standard DuckDB client libraries with an md: connection string. InterSystems IRIS: IRIS is multi-model: the same stored data can be accessed as relational tables via SQL, as persistent objects, and as multidimensional globals, so integrations usually standardize on the SQL projection. Stacksync's field mapping accounts for these differences between InterSystems IRIS and MotherDuck without custom code.
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 InterSystems IRIS and MotherDuck.