Two-way sync
Changes in Braze or Citus instantly reflect in both systems. No stale data, no manual imports.
Keep Braze and Citus in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Engineers integrate with tools like Braze through APIs, which means auth, pagination, rate limits, webhooks, and retry logic, all maintained forever and all different for every tool. Meanwhile the data would be trivial to use if it simply lived in Citus.
Stacksync mirrors Canvases, Subscription Groups, Content Blocks, Users from Braze into Schemas, Views, Sequences, Distributed tables in Citus and keeps both sides in sync in real time. Your services query the database directly, and inserts or updates your code makes flow back into Braze, so the tool and the database never disagree.
Updates in Braze arrive as row changes in Citus, so triggers, jobs, and services can respond in near real time.
Every synced tool looks the same from the database, so each new integration is configuration, not a new codebase.
Records from Braze are ordinary rows in Citus; join them, index them, and use them in application logic without touching the vendor API.
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.
| Braze objects | Citus objects | |
|---|---|---|
| Custom Events Behavioral events pushed into Braze to trigger campaigns and Canvases. | Sequences Key generators that matter when external writes must not collide with application inserts. | |
| Purchases Transaction records logged against profiles for revenue-based targeting. | Distributed tables Tables sharded across worker nodes by a distribution column; the main sync target for large datasets. | |
| Segments Audience definitions read for membership export and campaign targeting. | Reference tables Small lookup tables replicated to every node, synced like ordinary Postgres tables. | |
| Campaigns Message sends whose metadata and analytics are read for reporting. | Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. | |
| Canvases Multi-step journeys; entry and performance data is read for lifecycle analysis. | Schemas Standard Postgres namespaces used to scope what a sync user can read and write. | |
| Subscription Groups Channel-level opt-in states synced with consent records in other systems. | Views Curated projections over distributed data, often used as read-only sync sources. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Braze–Citus connection.
Changes in Braze or Citus instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Braze or Citus data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Braze or Citus record.
Track your Braze ⇄ Citus sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Braze and Citus.
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.
Authenticate Braze and Citus with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Braze and Citus 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Braze and Citus: authenticate both systems, choose the objects to sync (such as Braze's Custom Events and Purchases), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on Braze: Braze Currents streams engagement events outward; profile reads otherwise rely on export endpoints and polling. On Citus: PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Braze side: Canvases, Subscription Groups, Content Blocks, Users, plus custom fields where Braze exposes them. On the Citus side: Schemas, Views, Sequences, Distributed tables. Stacksync auto-detects both schemas and converts types between the two systems.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
Common patterns for Braze and Citus: React to changes as they happen; One integration pattern for the whole stack; Read Braze with a query. Updates in Braze arrive as row changes in Citus, so triggers, jobs, and services can respond in near real time.
Braze: REST API. Authentication: REST API keys scoped to specific endpoints, issued per workspace. 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). Stacksync manages authentication, retries, and rate limits on both sides.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 386 integrations available for Braze and Citus.