Skip to content
Database

Citus to OpenSearch integration — real-time, two-way sync

Keep Citus and OpenSearch 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 Citus and OpenSearch

Keep Citus and OpenSearch 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 Citus and OpenSearch 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

  • Write CRM or billing records into reference tables so distributed queries can join operational context locally on every node.
  • Use a Citus cluster as the scalable operational store behind a customer-facing app while syncing summaries back to internal tools.
  • Stream CRM records such as accounts, contacts, and tickets into OpenSearch to power internal search across customer data.
  • Sync product catalogs from an ERP or database into the indexes that back storefront search.

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.

Cross-engine sync

Keep the same dataset live in both Citus and OpenSearch, so each workload runs on the engine that suits it.

What you can sync between Citus and OpenSearch

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.

Citus objects OpenSearch objects
Reference tables Small lookup tables replicated to every node, synced like ordinary Postgres tables. Indexes The core container; synced records land in indexes with defined mappings
Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. Documents JSON records written via the index and bulk APIs and read via search queries
Schemas Standard Postgres namespaces used to scope what a sync user can read and write. Index aliases Stable names over rotating indexes, used for zero-downtime reindex during backfills
Views Curated projections over distributed data, often used as read-only sync sources. Index templates Mapping and settings presets applied to new indexes a sync creates
Sequences Key generators that matter when external writes must not collide with application inserts. Ingest pipelines Server-side processors that transform documents as they are written
Distributed tables Tables sharded across worker nodes by a distribution column; the main sync target for large datasets. Data streams Append-oriented time-series storage for logs and events pushed from source systems
What ships with Citus ⇄ OpenSearch

Connect Citus and OpenSearch for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Citus–OpenSearch connection.

Real-time

Two-way sync

Changes in Citus or OpenSearch instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Citus or OpenSearch 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 Citus or OpenSearch record.

Observability

Monitoring

Track your Citus ⇄ OpenSearch sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Citus and OpenSearch.

How the Citus and OpenSearch connectors work

Citus

Integration surface
PostgreSQL wire protocol; any standard Postgres driver connects to the coordinator node
Authentication
Database credentials (standard PostgreSQL authentication; managed deployments add cloud IAM options)
Change detection
PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres
Capabilities
read · write · CDC

OpenSearch

Integration surface
REST API over HTTP(S) with JSON payloads
Authentication
basic authentication with the security plugin, or AWS IAM request signing on Amazon OpenSearch Service
Change detection
no native change feed; reads rely on queries with scroll or point-in-time polling
Capabilities
read · write
Rate limits
throughput bounded by cluster sizing rather than fixed API quotas
How it works

How to connect Citus to OpenSearch — 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.

  1. 01

    Connect your apps

    Authenticate Citus and OpenSearch with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Citus connected
    OpenSearch connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Citus and OpenSearch 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Citus ⇄ OpenSearch
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Citus OpenSearch
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Citus and OpenSearch integration FAQ

SECURITY

Security teams love 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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 386 integrations available for Citus and OpenSearch.

Popular · 8 of 386
All Citus integrations All OpenSearch integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own