Real-time
Two-way sync
Changes in Azure Cosmos DB or Citus instantly reflect in both systems. No stale data, no manual imports.
Database
Azure Cosmos DB to Citus integration — real-time, two-way sync
Keep Azure Cosmos DB and Citus 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 Azure Cosmos DB and Citus
Keep Azure Cosmos DB and Citus 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 Azure Cosmos DB and Citus 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
- Mirror Cosmos DB items into Postgres so teams can query operational data with standard SQL.
- Two-way sync between a Cosmos DB-backed product catalog and a PIM or commerce platform.
- 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.
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 Azure Cosmos DB and Citus, 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.
What you can sync between Azure Cosmos DB and Citus
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.
| Azure Cosmos DB objects | Citus objects | |
|---|---|---|
| Stored procedures and triggers Server-side logic scoped to a partition; relevant when writes must respect existing validation. | Sequences Key generators that matter when external writes must not collide with application inserts. | |
| Databases Top-level namespaces that scope containers and throughput provisioning. | Distributed tables Tables sharded across worker nodes by a distribution column; the main sync target for large datasets. | |
| Containers The unit of partitioning and throughput; each container maps to a synced collection. | Reference tables Small lookup tables replicated to every node, synced like ordinary Postgres tables. | |
| Items (JSON documents) Schema-flexible JSON records read and written during sync; nested structures are flattened or mapped as needed. | Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. | |
| Partition keys Determine data distribution and must be included on writes for the sync to route items correctly. | Schemas Standard Postgres namespaces used to scope what a sync user can read and write. | |
| Change feed entries Ordered record of inserts and updates per partition, consumed for incremental sync. | Views Curated projections over distributed data, often used as read-only sync sources. |
What ships with Azure Cosmos DB ⇄ Citus
Connect Azure Cosmos DB and Citus for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure Cosmos DB–Citus connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Azure Cosmos DB or Citus 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 Azure Cosmos DB or Citus record.
Observability
Monitoring
Track your Azure Cosmos DB ⇄ Citus sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Azure Cosmos DB and Citus.
How the Azure Cosmos DB and Citus connectors work
Azure Cosmos DB
- Integration surface
- REST API and SDKs over HTTPS (API for NoSQL, formerly the SQL API); also MongoDB, Cassandra, Gremlin, and Table API surfaces
- Authentication
- Account keys, resource tokens, or Microsoft Entra ID role-based access
- Change detection
- Built-in change feed exposing inserts and updates in order within each partition key range
- Capabilities
- read · write · CDC
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
How it works
How to connect Azure Cosmos DB to Citus — 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 Azure Cosmos DB and Citus with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Azure Cosmos DB
connected
Citus
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Azure Cosmos DB and Citus 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 · Azure Cosmos DB ⇄ CitusCustomers 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.
Azure Cosmos DB CitusCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Azure Cosmos DB and Citus integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Azure Cosmos DB and Citus: authenticate both systems, choose the objects to sync (such as Azure Cosmos DB's Stored procedures and triggers and Databases), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Azure Cosmos DB: REST API and SDKs over HTTPS (API for NoSQL, formerly the SQL API); also MongoDB, Cassandra, Gremlin, and Table API surfaces. Authentication: Account keys, resource tokens, or Microsoft Entra ID role-based access. Citus: PostgreSQL wire protocol; any standard Postgres driver connects to the coordinator node. Authentication: Database credentials (standard PostgreSQL authentication; managed deployments add cloud IAM options). Stacksync manages authentication, retries, and rate limits on both sides.
-
Azure Cosmos DB: Throughput is provisioned in request units per container or database, which means sync read and write volume has a direct cost and throttling dimension. Citus: Distributed tables are sharded by a declared distribution column, and reference tables are fully replicated to all nodes; the table type changes how writes and joins behave. Stacksync's field mapping accounts for these differences between Azure Cosmos DB and Citus 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 Azure Cosmos DB and Citus records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Azure Cosmos DB and Citus connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Azure Cosmos DB–Citus integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Azure Cosmos DB and Citus. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
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.
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 386 integrations available for Azure Cosmos DB and Citus.
Popular · 8 of 386
-
Azure Cosmos DB ⇄ Dynamo DB -
Azure Cosmos DB ⇄ IBM Db2 -
Azure Cosmos DB ⇄ Firebase -
Azure Cosmos DB ⇄ SingleStore -
Citus ⇄ MySQL -
Citus ⇄ MariaDB -
Citus ⇄ SQL Server -
Citus ⇄ Postgres Heroku
No integrations match .
