Real-time
Two-way sync
Changes in Citus or Exasol instantly reflect in both systems. No stale data, no manual imports.
Database ⇄ Data warehouse
Citus to Exasol integration — real-time, two-way sync
Keep Citus and Exasol 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 Exasol
Connect Citus and Exasol with one live, two-way sync: operational rows flow into the warehouse, and computed results flow back where systems can read them fast.
Operational databases and analytical warehouses want the same data at different moments. Analysts want Citus's rows in Exasol, current and joinable, without a change-data-capture pipeline to maintain. Engineers want the outputs of warehouse work, such as aggregates, features, and segments, available in Citus where the services that read from it get them at normal query latency.
Stacksync covers both directions with one connection. Tables or collections in Citus sync into Exasol in real time, and result tables in Exasol sync back into Citus, with schema and type mapping between the two systems handled for you.
Common use cases
- 01 Keep dimension tables such as customers and products aligned with the systems of record.
- 02 Load CRM and ERP records into Exasol tables on a schedule so analysts query fresh operational data.
- 03 Write CRM or billing records into reference tables so distributed queries can join operational context locally on every node.
- 04 Use a Citus cluster as the scalable operational store behind a customer-facing app while syncing summaries back to internal tools.
Common sync patterns
Operational data in the warehouse, minus the pipeline
Rows from Citus land in Exasol as they change, replacing hand-built CDC and batch extract jobs.
Serve warehouse results at database speed
Aggregates or model outputs computed in Exasol sync into Citus, where whatever reads from that database gets them without querying the warehouse.
Fresh analytics without loading windows
Because changes stream continuously, analysts query current data instead of waiting for last night's load.
What you can sync between Citus and Exasol
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 | Exasol objects | How this pairing syncs | |
|---|---|---|---|
| Schemas Standard Postgres namespaces used to scope what a sync user can read and write. | Schemas Namespaces that group the tables a sync reads from or writes into. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Views Curated projections over distributed data, often used as read-only sync sources. | Views Read-only query surfaces often used as curated sources for reverse ETL. | 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. | UDF scripts In-database functions that can transform synced data after load. | Distributed tables is specific to Citus and UDF scripts to Exasol — 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. | Users and roles Grant read/write access for the dedicated integration account. | Reference tables is specific to Citus and Users and roles to Exasol — each maps to any object or custom field on the other side. | |
| Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. | Tables Primary sync target; columnar relational tables written with standard SQL. | Local tables is specific to Citus and Tables to Exasol — each maps to any object or custom field on the other side. | |
| Sequences Key generators that matter when external writes must not collide with application inserts. | Virtual schemas Federated views over external sources; useful for deciding what needs physical replication. | Sequences is specific to Citus and Virtual schemas to Exasol — each maps to any object or custom field on the other side. |
How changes propagate between Citus and Exasol
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 Exasol 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 Exasol as a row-level write, with types converted between the two schemas.
Exasol Citus Interval-based propagation
DetectionStacksync polls Exasol for changes on an incremental schedule, reading only records changed since the previous pass. Polling with timestamp or key columns.
DeliveryEach detected change is applied to Citus as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- Exasol: No API quota; concurrency is bounded by cluster resources and session limits.
What ships with Citus ⇄ Exasol
Connect Citus and Exasol for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Citus–Exasol connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Citus or Exasol 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 Exasol record.
Observability
Monitoring
Track your Citus ⇄ Exasol 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 Exasol.
How the Citus and Exasol 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
Exasol
- Integration surface
- SQL over JDBC/ODBC drivers and a WebSocket-based client protocol
- Authentication
- Database credentials (username and password)
- Change detection
- Polling with timestamp or key columns; Exasol does not expose a transaction-log change feed to clients
- Capabilities
- read · write
- Rate limits
- No API quota; concurrency is bounded by cluster resources and session limits
How it works
How to connect Citus to Exasol — 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 Exasol 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
Exasol
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Citus and Exasol 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 ⇄ ExasolCustomers 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 ExasolCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Citus and Exasol integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Citus and Exasol: authenticate both systems, choose the objects to sync (such as Citus's Schemas and Views), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Common patterns for Citus and Exasol: Operational data in the warehouse, minus the pipeline; Serve warehouse results at database speed; Fresh analytics without loading windows. Rows from Citus land in Exasol as they change, replacing hand-built CDC and batch extract jobs.
-
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). Exasol: SQL over JDBC/ODBC drivers and a WebSocket-based client protocol. Authentication: Database credentials (username and password). Stacksync manages authentication, retries, and rate limits on both sides.
-
Exasol: Bulk loading uses the IMPORT statement, which is more efficient than row-by-row inserts for sync workloads. Citus: The managed cloud offering is Azure Cosmos DB for PostgreSQL, which is Citus under a Microsoft brand. Stacksync's field mapping accounts for these differences between Citus and Exasol 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 Exasol records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Citus and Exasol connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Citus–Exasol integration in-house.
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 360 integrations available for Citus and Exasol.
Popular · 3 of 360
No integrations match .
