Real-time
Real-time sync
Changes in Aviato or Citus instantly reflect in both systems. No stale data, no manual imports.
Business productivity ⇄ Database
Aviato to Citus integration — real-time data sync
Keep Aviato 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.
- 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 Aviato and Citus
Mirror Aviato's data into Citus so your own code can read and write it like any other table, with changes flowing both ways in seconds.
Aviato is a read-only source: Stacksync reads its data in real time and delivers it into Citus, so Citus always reflects the current state of Aviato — without exports, scripts, or schedulers.
Engineers integrate with tools like Aviato 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 Employment Record, Acquisition / Exit Event, Company, Person from Aviato 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 Aviato, so the tool and the database never disagree.
Common use cases
- 01 Backfill missing firmographic fields on inbound leads by matching them to Aviato company profiles
- 02 Enrich CRM accounts with Aviato firmographic data (sector, stage, headcount) so reps see current company context without manual research
- 03 Consolidate per-tenant rows from distributed tables into per-customer reporting databases.
- 04 Sync high-volume event or tenant data from a Citus cluster into a warehouse for cross-tenant analytics.
Common sync patterns
One integration pattern for the whole stack
Every synced tool looks the same from the database, so each new integration is configuration, not a new codebase.
Read Aviato with a query
Records from Aviato are ordinary rows in Citus; join them, index them, and use them in application logic without touching the vendor API.
Automate Aviato from your codebase
Write to the synced tables in Citus and Stacksync propagates the change into Aviato, replacing custom integration code.
What you can sync between Aviato and Citus
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.
| Aviato objects | Citus objects | How this pairing syncs | |
|---|---|---|---|
| Acquisition / Exit Event M&A and exit records tied to the acquired company profile | Reference tables Small lookup tables replicated to every node, synced like ordinary Postgres tables. | Acquisition / Exit Event is specific to Aviato and Reference tables to Citus — each maps to any object or custom field on the other side. | |
| Company Private-company profiles with firmographics, sector tags, and status | Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. | Company is specific to Aviato and Local tables to Citus — each maps to any object or custom field on the other side. | |
| Person Founder and employee profiles linked to current and past companies | Schemas Standard Postgres namespaces used to scope what a sync user can read and write. | Person is specific to Aviato and Schemas to Citus — each maps to any object or custom field on the other side. | |
| Funding Round Round-level records with stage, amount, date, and participating investors | Views Curated projections over distributed data, often used as read-only sync sources. | Funding Round is specific to Aviato and Views to Citus — each maps to any object or custom field on the other side. | |
| Investor Funds and angels connected to the rounds and companies they back | Sequences Key generators that matter when external writes must not collide with application inserts. | Investor is specific to Aviato and Sequences to Citus — each maps to any object or custom field on the other side. | |
| Headcount Snapshot Point-in-time employee counts used to track company growth over time | Distributed tables Tables sharded across worker nodes by a distribution column; the main sync target for large datasets. | Headcount Snapshot is specific to Aviato and Distributed tables to Citus — each maps to any object or custom field on the other side. |
How changes propagate between Aviato and Citus
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.
Aviato Citus Interval-based propagation
DetectionStacksync polls Aviato for changes on an incremental schedule, reading only records changed since the previous pass. Polling-based: re-query tracked records on a schedule and diff against the last synced state.
DeliveryEach detected change is applied to Citus as a row-level write, with types converted between the two schemas.
Citus Aviato 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.
DeliveryAviato does not accept inbound record writes, so this direction carries requests rather than records: Aviato's output flows back as field updates on the originating Citus records.
Rate-limit considerations
- Aviato: Request volume is credit- and rate-limited per plan; schedule refreshes in batches rather than per-record calls.
What ships with Aviato ⇄ Citus
Connect Aviato and Citus for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Aviato–Citus connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Aviato or Citus 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 Aviato or Citus record.
Observability
Monitoring
Track your Aviato ⇄ Citus sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Aviato and Citus.
How the Aviato and Citus connectors work
Aviato
- Integration surface
- REST API returning JSON, with search/filter endpoints for querying company and people records
- Authentication
- API key passed on each request
- Change detection
- Polling-based: re-query tracked records on a schedule and diff against the last synced state; no native change feed is assumed
- Capabilities
- read
- Rate limits
- Request volume is credit- and rate-limited per plan; schedule refreshes in batches rather than per-record calls
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
How it works
How to connect Aviato to Citus — 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 Aviato 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.
Aviato
connected
Citus
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Aviato 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.
objects · Aviato ⇄ CitusCustomers 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.
Aviato CitusCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Aviato and Citus integration FAQ
-
Yes. Stacksync provides a managed, real-time integration between Aviato and Citus — Aviato is a read-only source, so data flows from it into the other system: authenticate both systems, choose the objects to sync, map fields visually, and changes propagate in milliseconds — no code required.
-
Aviato: Aviato's data model centers on private-market entities — companies, the people behind them, and the funding events connecting them — rather than user-created business records. 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 Aviato and Citus 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 Aviato and Citus records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Aviato and Citus connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Aviato–Citus integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Aviato and Citus. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Aviato: Polling-based: re-query tracked records on a schedule and diff against the last synced state; no native change feed is assumed. 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.
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 212 integrations available for Aviato and Citus.
Popular · 4 of 212
No integrations match .
