Real-time
Two-way sync
Changes in Citus or TimescaleDB instantly reflect in both systems. No stale data, no manual imports.
Database
Citus to TimescaleDB integration — real-time, two-way sync
Keep Citus and TimescaleDB 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 TimescaleDB
Keep Citus and TimescaleDB 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 TimescaleDB 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
- Consolidate per-tenant rows from distributed tables into per-customer reporting databases.
- Sync high-volume event or tenant data from a Citus cluster into a warehouse for cross-tenant analytics.
- Replicate subscription and billing events from operational Postgres tables into Timescale hypertables for time-series analysis.
- Keep device or asset reference tables bi-directionally in sync between TimescaleDB and an ERP.
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 TimescaleDB, 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 Citus and TimescaleDB
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 | TimescaleDB objects | |
|---|---|---|
| Sequences Key generators that matter when external writes must not collide with application inserts. | Schemas Postgres namespaces used to separate synced datasets by team or environment. | |
| Distributed tables Tables sharded across worker nodes by a distribution column; the main sync target for large datasets. | Hypertables Time-partitioned tables that hold the main time-series data; the primary read and write target in syncs. | |
| Reference tables Small lookup tables replicated to every node, synced like ordinary Postgres tables. | Chunks Time-bounded partitions of a hypertable; syncs read and write through the parent hypertable and never address chunks directly. | |
| Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. | Continuous Aggregates Incrementally maintained rollups that serve as pre-aggregated read sources for downstream systems. | |
| Schemas Standard Postgres namespaces used to scope what a sync user can read and write. | Regular PostgreSQL Tables Relational reference data such as devices, tenants, or accounts synced alongside the series data. | |
| Views Curated projections over distributed data, often used as read-only sync sources. | Views Standard SQL views used to shape or filter data for consumers. |
What ships with Citus ⇄ TimescaleDB
Connect Citus and TimescaleDB for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Citus–TimescaleDB connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Citus or TimescaleDB 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 TimescaleDB record.
Observability
Monitoring
Track your Citus ⇄ TimescaleDB 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 TimescaleDB.
How the Citus and TimescaleDB 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
TimescaleDB
- Integration surface
- SQL wire protocol (PostgreSQL)
- Authentication
- Database credentials
- Change detection
- Log-based capture via PostgreSQL logical decoding where the deployment allows it — hypertable changes surface on the underlying chunk tables and must be remapped to the parent — or timestamp-based polling on time columns; regular Postgres tables replicate through standard logical replication
- Capabilities
- read · write · CDC
- Rate limits
- No API rate limits; throughput is bounded by database resources and connection limits.
How it works
How to connect Citus to TimescaleDB — 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 TimescaleDB 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
TimescaleDB
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Citus and TimescaleDB 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 ⇄ TimescaleDBCustomers 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 TimescaleDBCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Citus and TimescaleDB integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Citus and TimescaleDB: authenticate both systems, choose the objects to sync (such as Citus's Sequences and Distributed tables), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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. TimescaleDB: Continuous aggregates materialize rollups incrementally instead of recomputing them on every query. Stacksync's field mapping accounts for these differences between Citus and TimescaleDB 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 TimescaleDB records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Citus and TimescaleDB connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Citus–TimescaleDB integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Citus and TimescaleDB. 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 TimescaleDB: Log-based capture via PostgreSQL logical decoding where the deployment allows it — hypertable changes surface on the underlying chunk tables and must be remapped to the parent — or timestamp-based polling on time columns; regular Postgres tables replicate through standard logical replication. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
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 Citus and TimescaleDB.
Popular · 8 of 386
-
Citus ⇄ Amazon Lightsail -
Citus ⇄ Apache Cassandra -
Citus ⇄ Azure Cosmos DB -
Citus ⇄ Azure SQL Database -
TimescaleDB ⇄ RavenDB -
TimescaleDB ⇄ Redis Enterprise -
TimescaleDB ⇄ SAP ASE (Sybase) -
TimescaleDB ⇄ Scaleway Postgres
No integrations match .
