Two-way sync
Changes in Firebolt or InterSystems IRIS instantly reflect in both systems. No stale data, no manual imports.
Keep Firebolt and InterSystems IRIS 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 Firebolt, 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 Firebolt in real time, and result tables in Firebolt sync back into InterSystems IRIS, 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 Firebolt and keep InterSystems IRIS focused on its operational workload.
Rows from InterSystems IRIS land in Firebolt 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.
| Firebolt objects | InterSystems IRIS objects | How this pairing syncs | |
|---|---|---|---|
| Tables Managed columnar tables written with SQL; the main sync destination. | Tables Relational projections of stored data are the primary read/write surface for SQL-based syncs. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Views Curated query surfaces commonly used as sources for reverse ETL. | Views SQL views expose curated slices of data for outbound replication. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Engines Compute resources that must be running for a sync to read or write. | Namespaces Namespaces partition databases and determine the connection context for integrations. | Engines is specific to Firebolt and Namespaces to InterSystems IRIS — each maps to any object or custom field on the other side. | |
| Databases Logical containers holding the tables a sync targets. | Stored Procedures Server-side logic callable over SQL supports controlled writes and transformations. | Databases is specific to Firebolt and Stored Procedures to InterSystems IRIS — each maps to any object or custom field on the other side. | |
| External tables References to files in object storage used to stage bulk loads. | Schemas Schema organization scopes which tables a sync connection can see. | External tables is specific to Firebolt and Schemas to InterSystems IRIS — each maps to any object or custom field on the other side. | |
| Aggregating indexes Precomputed rollups maintained at write time; incremental loads update them automatically. | Persistent Classes Object-model classes project to tables, so class data is reachable through SQL. | Aggregating indexes is specific to Firebolt and Persistent Classes to InterSystems IRIS — each maps to any object or custom field on the other side. |
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
DetectionStacksync polls Firebolt for changes on an incremental schedule, reading only records changed since the previous pass. Polling.
DeliveryEach detected change is applied to InterSystems IRIS as a row-level write, with types converted between the two schemas.
DetectionStacksync polls InterSystems IRIS for changes on an incremental schedule, reading only records changed since the previous pass. Polling (timestamp or query-based).
DeliveryEach detected change is applied to Firebolt as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Firebolt–InterSystems IRIS connection.
Changes in Firebolt or InterSystems IRIS instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Firebolt or InterSystems IRIS data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Firebolt or InterSystems IRIS record.
Track your Firebolt ⇄ InterSystems IRIS sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Firebolt and InterSystems IRIS.
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 Firebolt and InterSystems IRIS 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 Firebolt and InterSystems IRIS 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 Firebolt and InterSystems IRIS: authenticate both systems, choose the objects to sync (such as Firebolt's Tables and Views), map fields visually, and changes propagate both ways in milliseconds — no code required.
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 Firebolt and InterSystems IRIS records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Firebolt and InterSystems IRIS connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Firebolt–InterSystems IRIS integration in-house.
Yes — Stacksync ships production-grade connectors for both Firebolt and InterSystems IRIS. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Firebolt: Polling; Firebolt is an analytics destination and does not expose a change feed. On InterSystems IRIS: Polling (timestamp or query-based); no standard webhook surface. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Firebolt side: Engines, Databases, Tables, External tables, plus custom fields where Firebolt exposes them. On the InterSystems IRIS side: Persistent Classes, Globals, Namespaces, Stored Procedures. Stacksync auto-detects both schemas and converts types between the two systems.
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 392 integrations available for Firebolt and InterSystems IRIS.