Real-time
Two-way sync
Changes in Citus or MySQL instantly reflect in both systems. No stale data, no manual imports.
Database
Citus to MySQL integration — real-time, two-way sync
Keep Citus and MySQL 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 MySQL
Keep Citus and MySQL 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 MySQL 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
- 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.
- Keep e-commerce orders in MySQL flowing into finance and fulfillment systems without export scripts
- Feed a warehouse from MySQL continuously using binlog-based capture instead of nightly dumps
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.
Regional or environment copies
Mirror selected tables to another region or environment continuously, filtered to just the rows that should travel.
What you can sync between Citus and MySQL
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 | MySQL objects | |
|---|---|---|
| Views Curated projections over distributed data, often used as read-only sync sources. | Views Read-side projections used as outbound sync sources. | |
| Sequences Key generators that matter when external writes must not collide with application inserts. | Columns Field-level mapping targets with engine-typed values. | |
| Distributed tables Tables sharded across worker nodes by a distribution column; the main sync target for large datasets. | Primary and Unique Keys Match keys for idempotent upserts and conflict handling. | |
| Reference tables Small lookup tables replicated to every node, synced like ordinary Postgres tables. | JSON Columns Validated semi-structured payloads for nested SaaS data. | |
| Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. | Stored Procedures Server-side logic that can post-process synced rows. | |
| Schemas Standard Postgres namespaces used to scope what a sync user can read and write. | Triggers An alternative change-capture mechanism when binlog access is unavailable. |
What ships with Citus ⇄ MySQL
Connect Citus and MySQL for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Citus–MySQL connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Citus or MySQL 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 MySQL record.
Observability
Monitoring
Track your Citus ⇄ MySQL 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 MySQL.
How the Citus and MySQL 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
MySQL
- Integration surface
- SQL wire protocol (MySQL client/server protocol)
- Authentication
- Database credentials entered as a connection string or parameters, with optional SSL root certificate upload and optional SSH tunnel (SSH user + SSH host)
- Change detection
- Database triggers — Stacksync creates deterministic triggers for internal logging and syncing (requires log_bin_trust_function_creators=ON when binary logging is enabled)
- Capabilities
- read · write · CDC
- Rate limits
- No API rate limits; throughput is bounded by connection limits and server resources
How it works
How to connect Citus to MySQL — 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 MySQL 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
MySQL
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Citus and MySQL 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 ⇄ MySQLCustomers 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 MySQLCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Citus and MySQL integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Citus and MySQL: authenticate both systems, choose the objects to sync (such as Citus's Views and Sequences), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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). MySQL: SQL wire protocol (MySQL client/server protocol). Authentication: Database credentials entered as a connection string or parameters, with optional SSL root certificate upload and optional SSH tunnel (SSH user + SSH host). Stacksync manages authentication, retries, and rate limits on both sides.
-
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. MySQL: Composite primary keys are not supported — primary key must be a single column. Stacksync's field mapping accounts for these differences between Citus and MySQL 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 MySQL records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Citus and MySQL connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Citus–MySQL integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Citus and MySQL. 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 Citus and MySQL.
Popular · 8 of 386
-
Citus ⇄ YugabyteDB -
Citus ⇄ PostgreSQL -
Citus ⇄ Amazon RDS -
Citus ⇄ Supabase -
MySQL ⇄ OCI Database (Oracle Cloud) -
MySQL ⇄ OpenSearch -
MySQL ⇄ Oracle DB -
MySQL ⇄ RavenDB
No integrations match .
