Real-time
Two-way sync
Changes in InterSystems IRIS or Postgres Heroku instantly reflect in both systems. No stale data, no manual imports.
Database
InterSystems IRIS to Postgres Heroku integration — real-time, two-way sync
Keep InterSystems IRIS and Postgres Heroku in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
- SOC 2 and 6 other compliance frameworks
- POC with real engineers in minutes
Adopted by fast-scaling companies moving mission-critical data in real time
Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect InterSystems IRIS and Postgres Heroku
Keep InterSystems IRIS and Postgres Heroku synchronized in real time, across engines, regions, or services, in one or both directions.
Two databases that must agree is one of the oldest problems in engineering: different engines for different workloads, separate services with overlapping reference data, a migration in flight, or regional instances that share a subset of records. Hand-rolled replication across systems means change capture, conflict handling, and type mapping, all built and maintained by your team.
Stacksync syncs tables or collections between InterSystems IRIS and Postgres Heroku continuously and bi-directionally, translating types between the two engines and resolving conflicts by rules you configure. Rows written on either side appear on the other within seconds.
Common use cases
- 01 Sync operational tables in IRIS bi-directionally with a CRM so business teams work on IRIS-backed data without SQL access
- 02 Consolidate IRIS data with other databases in an analytics warehouse for cross-system reporting
- 03 Expose CRM objects as Postgres tables the Heroku application can query and join directly
- 04 Sync Heroku Postgres into a warehouse for reporting without running ETL dynos
Common sync patterns
Cross-engine sync
Keep the same dataset live in both InterSystems IRIS and Postgres Heroku, so each workload runs on the engine that suits it.
Migration with zero-downtime cutover
When one database is replacing the other, sync both directions during the transition and switch traffic when ready, without a freeze window.
Shared reference data between services
Services that own separate databases stay consistent on the records they share, without a custom replication layer.
What you can sync between InterSystems IRIS and Postgres Heroku
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 | Postgres Heroku objects | How this pairing syncs | |
|---|---|---|---|
| Tables Relational projections of stored data are the primary read/write surface for SQL-based syncs. | Tables Standard Postgres tables; the primary two-way sync target for app data. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Views SQL views expose curated slices of data for outbound replication. | Views Read-side projections exposed to outbound syncs. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Schemas Schema organization scopes which tables a sync connection can see. | Schemas Namespaces that scope which tables a sync reads and writes. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Persistent Classes Object-model classes project to tables, so class data is reachable through SQL. | JSONB Columns Semi-structured payloads for nested SaaS objects and metadata. | Persistent Classes is specific to InterSystems IRIS and JSONB Columns to Postgres Heroku — each maps to any object or custom field on the other side. | |
| Globals The underlying multidimensional storage; typically accessed indirectly via SQL or objects in syncs. | Sequences Generate surrogate keys for rows created by inbound syncs. | Globals is specific to InterSystems IRIS and Sequences to Postgres Heroku — each maps to any object or custom field on the other side. | |
| Namespaces Namespaces partition databases and determine the connection context for integrations. | Follower Databases Heroku-managed read replicas usable as low-impact sync sources. | Namespaces is specific to InterSystems IRIS and Follower Databases to Postgres Heroku — each maps to any object or custom field on the other side. |
How changes propagate between InterSystems IRIS and Postgres Heroku
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.
InterSystems IRIS Postgres Heroku Interval-based propagation
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 Postgres Heroku as a row-level write, with types converted between the two schemas.
Postgres Heroku InterSystems IRIS Interval-based propagation
DetectionStacksync polls Postgres Heroku for changes on an incremental schedule, reading only records changed since the previous pass. Trigger-based capture or polling in most configurations.
DeliveryEach detected change is applied to InterSystems IRIS as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- InterSystems IRIS: Constrained by database resources rather than published API rate limits.
- Postgres Heroku: No API rate limits; connection counts and performance are bounded by the Heroku Postgres plan.
What ships with InterSystems IRIS ⇄ Postgres Heroku
Connect InterSystems IRIS and Postgres Heroku for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every InterSystems IRIS–Postgres Heroku connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever InterSystems IRIS or Postgres Heroku data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
At scale
Event queues
Handle millions of events per minute without losing a single InterSystems IRIS or Postgres Heroku record.
Observability
Monitoring
Track your InterSystems IRIS ⇄ Postgres Heroku sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between InterSystems IRIS and Postgres Heroku.
How the InterSystems IRIS and Postgres Heroku connectors work
InterSystems IRIS
- Integration surface
- SQL over JDBC/ODBC, plus object and REST access layers
- Authentication
- Database credentials
- Change detection
- Polling (timestamp or query-based); no standard webhook surface
- Capabilities
- read · write
- Rate limits
- Constrained by database resources rather than published API rate limits
Postgres Heroku
- Integration surface
- SQL wire protocol (standard PostgreSQL)
- Authentication
- Database credentials from the Heroku DATABASE_URL config var; SSL required
- Change detection
- Trigger-based capture or polling in most configurations; log-based logical replication availability depends on plan and Heroku's managed server settings
- Capabilities
- read · write
- Rate limits
- No API rate limits; connection counts and performance are bounded by the Heroku Postgres plan
How it works
How to connect InterSystems IRIS to Postgres Heroku — three steps, no code
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.
- 01
Connect your apps
Authenticate InterSystems IRIS and Postgres Heroku with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
InterSystems IRIS
connected
Postgres Heroku
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the InterSystems IRIS and Postgres Heroku 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.
objects · InterSystems IRIS ⇄ Postgres HerokuCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
InterSystems IRIS Postgres HerokuCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
InterSystems IRIS and Postgres Heroku integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between InterSystems IRIS and Postgres Heroku: authenticate both systems, choose the objects to sync (such as InterSystems IRIS's Tables and Views), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both InterSystems IRIS and Postgres Heroku. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on InterSystems IRIS: Polling (timestamp or query-based); no standard webhook surface. On Postgres Heroku: Trigger-based capture or polling in most configurations; log-based logical replication availability depends on plan and Heroku's managed server settings. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the InterSystems IRIS side: Schemas, Persistent Classes, Globals, Namespaces, plus custom fields where InterSystems IRIS exposes them. On the Postgres Heroku side: Tables, Views, Materialized Views, Schemas. 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 Postgres Heroku: Cross-engine sync; Migration with zero-downtime cutover; Shared reference data between services. Keep the same dataset live in both InterSystems IRIS and Postgres Heroku, so each workload runs on the engine that suits it.
SECURITY
Security teams trust Stacksync
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.
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS
SSO & SCIM
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Alerts
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Secure connection options
Securely connects to your systems with:
Related integrations
Every pair below is a real-time, two-way sync. Search all 411 integrations available for InterSystems IRIS and Postgres Heroku.
Popular · 4 of 411
-
InterSystems IRIS ⇄ Oracle DB -
InterSystems IRIS ⇄ RavenDB -
InterSystems IRIS ⇄ Redis Enterprise -
InterSystems IRIS ⇄ SAP ASE (Sybase)
No integrations match .
