Real-time
Two-way sync
Changes in Citus or Supabase instantly reflect in both systems. No stale data, no manual imports.
Database
Citus to Supabase integration — real-time, two-way sync
Keep Citus and Supabase 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 Supabase
Keep Citus and Supabase 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 Supabase 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.
- Mirror billing and subscription records into Supabase tables the application can join directly
- Reflect auth.users state into support and CRM systems so teams see account status without querying the database
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.
Cross-engine sync
Keep the same dataset live in both Citus and Supabase, so each workload runs on the engine that suits it.
What you can sync between Citus and Supabase
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 | Supabase objects | |
|---|---|---|
| Schemas Standard Postgres namespaces used to scope what a sync user can read and write. | auth.users Managed authentication users, often mirrored into CRM or support systems. | |
| Views Curated projections over distributed data, often used as read-only sync sources. | Row Level Security Policies Row-level access rules that govern what the REST layer exposes. | |
| Sequences Key generators that matter when external writes must not collide with application inserts. | JSONB Columns Semi-structured payloads such as event properties or nested objects. | |
| Distributed tables Tables sharded across worker nodes by a distribution column; the main sync target for large datasets. | Database Functions Postgres functions that can transform or validate synced rows. | |
| Reference tables Small lookup tables replicated to every node, synced like ordinary Postgres tables. | Storage Object Metadata File metadata rows that can be joined to synced application data. | |
| Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. | Tables Standard Postgres tables; the primary two-way sync target. |
What ships with Citus ⇄ Supabase
Connect Citus and Supabase for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Citus–Supabase connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Citus or Supabase 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 Supabase record.
Observability
Monitoring
Track your Citus ⇄ Supabase 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 Supabase.
How the Citus and Supabase 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
Supabase
- Integration surface
- Direct PostgreSQL wire protocol connection, plus an auto-generated REST API (PostgREST)
- Authentication
- Database credentials (connection string) for SQL access; API keys (anon / service role) for the REST layer
- Change detection
- Log-based CDC via Postgres logical replication, the same WAL feed that powers Supabase Realtime; database webhooks can also fire on row changes
- Capabilities
- read · write · CDC · webhooks
- Rate limits
- SQL access is bounded by connection limits (pooled connections are provided); the REST layer is subject to the platform's limits
How it works
How to connect Citus to Supabase — 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 Supabase 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
Supabase
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Citus and Supabase 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 ⇄ SupabaseCustomers 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 SupabaseCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Citus and Supabase integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Citus and Supabase: 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 Supabase: Shared reference data between services; Regional or environment copies; Cross-engine sync. Services that own separate databases stay consistent on the records they share, without a custom replication layer.
-
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). Supabase: Direct PostgreSQL wire protocol connection, plus an auto-generated REST API (PostgREST). Authentication: Database credentials (connection string) for SQL access; API keys (anon / service role) for the REST layer. 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. Supabase: Supabase Realtime is built on the Postgres write-ahead log, streaming row changes over websockets. Stacksync's field mapping accounts for these differences between Citus and Supabase 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 Supabase records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Citus and Supabase connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Citus–Supabase integration in-house.
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 Supabase.
Popular · 8 of 386
-
Citus ⇄ Oracle DB -
Citus ⇄ RavenDB -
Citus ⇄ Redis Enterprise -
Citus ⇄ SAP ASE (Sybase) -
Supabase ⇄ AWS Aurora PostgreSQL -
Supabase ⇄ MongoDB -
Supabase ⇄ CockroachDB -
Supabase ⇄ Google AlloyDB
No integrations match .
