Database

Connect Citus to any app with two-way sync.

Two-way sync Citus across all your CRMs, databases, data warehouses, EDI systems, and AI tools, with custom workflows tailored to your data.

SOC 2 and 6 other compliance frameworks
POC with real engineers in minutes

Live sync

stacksync.com

Citus

Any system

<1s: latency
2-way: sync
100M+: records

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

Object catalog

What Stacksync syncs in Citus.

These objects sync between Citus and any connected system, with field-level mapping and conflict resolution. Custom fields are picked up from the live schema where Citus exposes them.

Distributed tables: Tables sharded across worker nodes by a distribution column; the main sync target for large datasets.
Reference tables: Small lookup tables replicated to every node, synced like ordinary Postgres tables.
Local tables: Coordinator-only tables that behave exactly like standard PostgreSQL tables.
Schemas: Standard Postgres namespaces used to scope what a sync user can read and write.
Views: Curated projections over distributed data, often used as read-only sync sources.
Sequences: Key generators that matter when external writes must not collide with application inserts.

API surface

How Stacksync connects to Citus.

The connector runs on Citus's native API. Stacksync manages authentication, rate limits, retries, and schema changes so your team does not maintain integration code.

Connection: 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

Sync directions

Read Supported
Write Supported
Change data capture Supported
Webhooks Not available

What ships with Citus

Connect Citus for flexible, real-time data sync.

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

Real-time

Two-way sync

Changes in Citus instantly reflect across connected systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions.

Use cases

What teams run on the Citus connector.

Citus is adopted by engineering and data teams whose PostgreSQL workloads outgrow a single node - multi-tenant SaaS backends, real-time analytics on event and time-series data, and microservices using schema-based sharding. As a Postgres extension (and the engine behind Azure Cosmos DB for PostgreSQL), it keeps sharding logic in the database rather than the application, so the cluster typically holds large operational datasets that applications and BI query directly.

Data engineering
Database administrators
Platform engineering

Sync high-volume event or tenant data from a Citus cluster into a warehouse for cross-tenant analytics.
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.
Consolidate per-tenant rows from distributed tables into per-customer reporting databases.
Replicate operational data from CRMs or ERPs into distributed tables so tenant-scoped application queries and dashboards run against scaled-out Postgres.
Maintain reference tables (lookup and dimension data) from an upstream system of record so every worker node joins against current values.

Good to know

Citus is a PostgreSQL extension, not a fork: clients connect with ordinary Postgres drivers and SQL, and the coordinator routes queries to shards.
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.
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).
The managed cloud offering is Azure Cosmos DB for PostgreSQL, which is Citus under a Microsoft brand.
Any standard Postgres driver connects to the coordinator, but table type matters: distributed tables require a distribution column, joins perform best when co-located, and some SQL features behave differently than single-node Postgres. Decide up front which synced tables are distributed, reference, or local.

All Citus integrations

Pick the system you need to keep in sync with Citus. Each page covers the sync setup, field mapping, and common workflows for that pair.

Database · 15

Data warehouse · 8

Accounting and finance · 13

How it works

Set up Citus in minutes, without APIs.

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 with its 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

OAuth 2.0
SSH tunnel
SSL certificate
VPC peering
02
Choose tables

Pick the Citus objects to sync — Stacksync auto-detects the schema, 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

Customers 12,480
Sales Orders 8,213
Invoices 5,902
Items 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.
- Auto-map
- Type casting
- Transforms
Citus database

Company company_name text
Email email text
Amount amount numeric
Created created_at timestamp

Try interactive demo

FAQ

Citus connector FAQ

What can I sync with the Citus connector?

Citus's core objects — Distributed tables, Reference tables, Local tables, Schemas and custom fields — can sync with any of 302 other systems. Every integration is real-time and bidirectional, with field-level mapping and conflict resolution.

How does Stacksync connect to Citus?

Via PostgreSQL wire protocol; any standard Postgres driver connects to the coordinator node, authenticated with Database credentials (standard PostgreSQL authentication; managed deployments add cloud IAM options). Changes are detected as follows — postgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres. Stacksync manages rate limits, retries, and schema changes automatically.

Is the Citus connector two-way?

Yes. Changes made in Citus propagate to the connected system and vice versa, in milliseconds. One-way flows are also supported when a direction should stay read-only.

How long does a Citus integration take to set up?

Most Citus integrations go live in minutes: authenticate Citus and the other system, pick objects and fields, and enable the sync. No code and no infrastructure to manage.

Is Citus data secure in transit?

Stacksync is SOC 2 Type II, ISO 27001, GDPR and HIPAA compliant. Citus data is encrypted in transit, and a zero-persistent-storage architecture means records are not retained after a sync operation.

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.

Learn more about security

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:

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

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

Connect Citus to any app with two-way sync.

Adopted by fast-scaling companies moving mission-critical data in real time

What Stacksync syncs in Citus.