Real-time
Two-way sync
Changes in PostgreSQL or Reltio instantly reflect in both systems. No stale data, no manual imports.
Database
PostgreSQL to Reltio integration — real-time, two-way sync
Keep PostgreSQL and Reltio 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 PostgreSQL and Reltio
Keep PostgreSQL and Reltio 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 PostgreSQL and Reltio 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 Consolidate data from several microservice databases into one operational Postgres store
- 02 Feed reporting and BI from a continuously synced Postgres replica instead of scheduled ETL scripts
- 03 Sync Relations (affiliations, hierarchies, households) between Reltio and a CRM or graph so account and affiliation structures stay aligned.
- 04 Feed Interactions (transactions, visits, events) into Reltio to enrich entity profiles, then read them back for 360-degree reporting.
Common sync patterns
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.
Regional or environment copies
Mirror selected tables to another region or environment continuously, filtered to just the rows that should travel.
What you can sync between PostgreSQL and Reltio
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.
| PostgreSQL objects | Reltio objects | How this pairing syncs | |
|---|---|---|---|
| Materialized Views Precomputed result sets synced outward on a refresh schedule. | Reference Data (RDM) Managed lookup and reference values (country codes, standardized values, hierarchies); read and updated so downstream systems share consistent reference data. | Materialized Views is specific to PostgreSQL and Reference Data (RDM) to Reltio — each maps to any object or custom field on the other side. | |
| Schemas Namespaces that scope which tables a sync reads and writes. | Entities Golden records for each configured entity type (for example Organization, Individual/Contact, Location, or Product); full CRUD via /entities, so records are created, updated, and deleted, and Reltio matches and merges them by survivorship rules. | Schemas is specific to PostgreSQL and Entities to Reltio — each maps to any object or custom field on the other side. | |
| Columns Field-level mapping targets; types are mapped to the connected system's field types. | Relations Typed relationships between two entities (affiliations, hierarchies, employment, households); read and written via /relations to keep account hierarchies and affiliation graphs aligned across systems. | Columns is specific to PostgreSQL and Relations to Reltio — each maps to any object or custom field on the other side. | |
| Primary and Unique Keys Used as match keys for idempotent upserts and conflict resolution. | Crosswalks Per-entity references to the source systems and their record IDs; written when loading records so Reltio ties each source contribution to a golden record, and read to trace lineage back to origin systems. | Primary and Unique Keys is specific to PostgreSQL and Crosswalks to Reltio — each maps to any object or custom field on the other side. | |
| JSONB Columns Hold semi-structured payloads such as nested SaaS objects or metadata. | Interactions Transactional or event records linked to entities (purchases, visits, activities); read and written via /interactions to enrich profiles and power 360-degree reporting. | JSONB Columns is specific to PostgreSQL and Interactions to Reltio — each maps to any object or custom field on the other side. | |
| Sequences Generate surrogate keys for rows created by inbound syncs. | Matches (Potential Matches) Candidate duplicate pairs produced by match rules; read to review, and resolved with merge, unmerge, or not-a-match actions to control survivorship. | Sequences is specific to PostgreSQL and Matches (Potential Matches) to Reltio — each maps to any object or custom field on the other side. |
How changes propagate between PostgreSQL and Reltio
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.
PostgreSQL Reltio Sub-second propagation
DetectionChanges in PostgreSQL are captured at the source via change data capture — no polling loop against its API. Logical replication (wal_level = logical) for change data capture via the "Postgres" connector.
DeliveryEach detected change is written to Reltio through its API, with automatic retries and rate-limit backoff.
Reltio PostgreSQL Interval-based propagation
DetectionStacksync polls Reltio for changes on an incremental schedule, reading only records changed since the previous pass. Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored.
DeliveryEach detected change is applied to PostgreSQL as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- PostgreSQL: No API rate limits; throughput is bounded by connection limits, instance resources, and replication slot throughput.
- Reltio: Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.
What ships with PostgreSQL ⇄ Reltio
Connect PostgreSQL and Reltio for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every PostgreSQL–Reltio connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever PostgreSQL or Reltio 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 PostgreSQL or Reltio record.
Observability
Monitoring
Track your PostgreSQL ⇄ Reltio sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between PostgreSQL and Reltio.
How the PostgreSQL and Reltio connectors work
PostgreSQL
- Integration surface
- SQL wire protocol (PostgreSQL frontend/backend protocol)
- Authentication
- Database credentials (connection string or parameters), with optional SSL root certificate upload and optional SSH tunnel (SSH user + host); a least-privilege DB user
- Change detection
- Logical replication (wal_level = logical) for change data capture via the "Postgres" connector; database triggers (TRIGGER grant + stacksync_logging schema) via the trigger-based "Postgres Heroku" connector where
- Capabilities
- read · write · CDC
- Rate limits
- No API rate limits; throughput is bounded by connection limits, instance resources, and replication slot throughput
Reltio
- Integration surface
- Reltio REST API (Data API) — /entities, /relations, /interactions, /activities, plus Match, RDM (reference data), and Data Change Request endpoints; base URL https://{environment}.reltio.com/reltio/api/{tenantId}
- Authentication
- OAuth 2.0 bearer tokens obtained from Reltio's central auth server (POST https://auth.reltio.com/oauth/token, client-credentials or password grant, application/x-www-form-urlencoded) and sent as Authorization: Bearer <token>; access tokens expire after about 60 minutes and are renewed with a refresh token, and are scoped per API (entities_api, relations_api, interactions_api, configuration_api, graphs_api)
- Change detection
- Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored watermark. Reltio has no CDC log external tools consume; separately, Reltio's event streaming can publish entity change events (created, changed, removed) to a customer-configured message queue (Amazon SQS/SNS, Google Pub/Sub, Azure Service Bus, or Kafka), which is a queue feed rather than HTTP webhooks.
- Capabilities
- read · write
- Rate limits
- Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.
How it works
How to connect PostgreSQL to Reltio — 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 PostgreSQL and Reltio with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
PostgreSQL
connected
Reltio
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the PostgreSQL and Reltio 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 · PostgreSQL ⇄ ReltioCustomers 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.
PostgreSQL ReltioCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
PostgreSQL and Reltio integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between PostgreSQL and Reltio: authenticate both systems, choose the objects to sync (such as PostgreSQL's Materialized Views and Schemas), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
PostgreSQL: SQL wire protocol (PostgreSQL frontend/backend protocol). Authentication: Database credentials (connection string or parameters), with optional SSL root certificate upload and optional SSH tunnel (SSH user + host); a least-privilege DB user. Reltio: Reltio REST API (Data API) — /entities, /relations, /interactions, /activities, plus Match, RDM (reference data), and Data Change Request endpoints; base URL https://{environment}.reltio.com/reltio/api/{tenantId}. Authentication: OAuth 2.0 bearer tokens obtained from Reltio's central auth server (POST https://auth.reltio.com/oauth/token, client-credentials or password grant, application/x-www-form-urlencoded) and sent as Authorization: Bearer <token>; access tokens expire after about 60 minutes and are renewed with a refresh token, and are scoped per API (entities_api, relations_api, interactions_api, configuration_api, graphs_api). Stacksync manages authentication, retries, and rate limits on both sides.
-
PostgreSQL: INSERT ... ON CONFLICT gives native upsert semantics, which makes inbound syncs idempotent against primary or unique keys. Reltio: Every Reltio entity carries one or more crosswalks — references to the source systems and their record IDs — which is how survivorship merges multiple source records into one golden record and how writes are attributed back to a source. Stacksync's field mapping accounts for these differences between PostgreSQL and Reltio 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 PostgreSQL and Reltio records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed PostgreSQL and Reltio connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom PostgreSQL–Reltio integration in-house.
-
Yes — Stacksync ships production-grade connectors for both PostgreSQL and Reltio. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates 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
CSA STAR
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 470 integrations available for PostgreSQL and Reltio.
Popular · 5 of 470
-
PostgreSQL ⇄ Redis Enterprise -
PostgreSQL ⇄ SAP ASE (Sybase) -
PostgreSQL ⇄ Scaleway Postgres -
PostgreSQL ⇄ TiDB -
Reltio ⇄ Elasticsearch
No integrations match .
