Real-time
Two-way sync
Changes in Citus or YugabyteDB instantly reflect in both systems. No stale data, no manual imports.
Database
Citus to YugabyteDB integration — real-time, two-way sync
Keep Citus and YugabyteDB 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 YugabyteDB
Keep Citus and YugabyteDB 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 YugabyteDB 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 Write CRM or billing records into reference tables so distributed queries can join operational context locally on every node.
- 02 Use a Citus cluster as the scalable operational store behind a customer-facing app while syncing summaries back to internal tools.
- 03 Sync reference data such as pricing or entitlements from an ERP into YugabyteDB for globally distributed low-latency reads.
- 04 Consolidate data from regional YugabyteDB clusters into one reporting store.
Common sync patterns
Cross-engine sync
Keep the same dataset live in both Citus and YugabyteDB, 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 Citus and YugabyteDB
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 | YugabyteDB objects | How this pairing syncs | |
|---|---|---|---|
| Schemas Standard Postgres namespaces used to scope what a sync user can read and write. | Schemas Postgres-style namespaces in YSQL used to organize synced data. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Sequences Key generators that matter when external writes must not collide with application inserts. | Sequences ID generation objects relevant when syncing writes into YSQL tables. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Distributed tables Tables sharded across worker nodes by a distribution column; the main sync target for large datasets. | Indexes Global secondary indexes maintained transactionally alongside table writes. | Distributed tables is specific to Citus and Indexes to YugabyteDB — each maps to any object or custom field on the other side. | |
| Reference tables Small lookup tables replicated to every node, synced like ordinary Postgres tables. | Materialized Views Precomputed query results available in YSQL for read-side shaping. | Reference tables is specific to Citus and Materialized Views to YugabyteDB — each maps to any object or custom field on the other side. | |
| Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. | CDC Streams Change streams over the storage-layer WAL consumed through logical replication or Debezium-compatible connectors. | Local tables is specific to Citus and CDC Streams to YugabyteDB — each maps to any object or custom field on the other side. | |
| Views Curated projections over distributed data, often used as read-only sync sources. | Databases and Keyspaces Top-level containers for the YSQL (Postgres-style) and YCQL (Cassandra-style) APIs respectively. | Views is specific to Citus and Databases and Keyspaces to YugabyteDB — each maps to any object or custom field on the other side. |
How changes propagate between Citus and YugabyteDB
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.
Citus YugabyteDB Sub-second propagation
DetectionChanges in Citus are captured at the source via change data capture — no polling loop against its API. PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres.
DeliveryEach detected change is applied to YugabyteDB as a row-level write, with types converted between the two schemas.
YugabyteDB Citus Sub-second propagation
DetectionChanges in YugabyteDB are captured at the source via change data capture — no polling loop against its API. Native CDC from the write-ahead log via PostgreSQL logical replication or Debezium-compatible connectors.
DeliveryEach detected change is applied to Citus as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- YugabyteDB: No API rate limits; throughput scales with cluster nodes and tablet distribution.
What ships with Citus ⇄ YugabyteDB
Connect Citus and YugabyteDB for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Citus–YugabyteDB connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Citus or YugabyteDB 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 YugabyteDB record.
Observability
Monitoring
Track your Citus ⇄ YugabyteDB 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 YugabyteDB.
How the Citus and YugabyteDB 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
YugabyteDB
- Integration surface
- SQL wire protocol (PostgreSQL-compatible YSQL) plus a Cassandra-compatible YCQL API
- Authentication
- Database credentials
- Change detection
- Native CDC from the write-ahead log via PostgreSQL logical replication or Debezium-compatible connectors
- Capabilities
- read · write · CDC
- Rate limits
- No API rate limits; throughput scales with cluster nodes and tablet distribution.
How it works
How to connect Citus to YugabyteDB — 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 Citus and YugabyteDB with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Citus
connected
YugabyteDB
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Citus and YugabyteDB 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 · Citus ⇄ YugabyteDBCustomers 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.
Citus YugabyteDBCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Citus and YugabyteDB integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Citus and YugabyteDB: authenticate both systems, choose the objects to sync (such as Citus's Schemas and Sequences), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Citus: Because shard data lives on worker nodes, log-based CDC is more involved than on single-node Postgres and depends on the Citus version and hosting (including the Azure managed service). YugabyteDB: A second, Cassandra-compatible API (YCQL) is available alongside YSQL on the same cluster. Stacksync's field mapping accounts for these differences between Citus and YugabyteDB 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 Citus and YugabyteDB records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Citus and YugabyteDB connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Citus–YugabyteDB integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Citus and YugabyteDB. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Citus: PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres. On YugabyteDB: Native CDC from the write-ahead log via PostgreSQL logical replication or Debezium-compatible connectors. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
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 357 integrations available for Citus and YugabyteDB.
Popular · 4 of 357
No integrations match .
