Skip to content
Database ⇄ Accounting and finance

Citus to Rillet integration — real-time, two-way sync

Keep Citus and Rillet 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 Rillet

Work with Rillet's financial data straight from Citus: read it with ordinary queries, write to it from your own code, and let Stacksync keep both sides consistent.

Engineers need finance data more often than finance systems make it easy to get: for internal tools, reporting services, or logic that reacts to invoices and payments. Working through the vendor API means rate limits, pagination, and glue code that has to be maintained forever.

Stacksync mirrors Charge, Reimbursement, Custom Field, Account from Rillet into Distributed tables, Reference tables, Local tables, Schemas in Citus and keeps the two in sync bi-directionally and in real time. Your services read finance records with normal queries against Citus, and rows your code writes or updates flow back into Rillet with validation, so the finance system stays the system of record.

Common use cases

  • 01 Sync AR and collection status back to customer success tools ahead of renewals.
  • 02 Keep customers and invoices aligned between Rillet and a CRM so finance and sales work from the same account records.
  • 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

Query finance data like any other data

Customers, invoices, and payments from Rillet live in Citus as regular tables or collections your team can join, index, and query.

Internal tools without API plumbing

Build dashboards and back-office tools directly on Citus; Stacksync handles the API calls, rate limits, and retries against Rillet.

Write back safely

Updates written to the synced tables in Citus propagate into Rillet, so automations can create or correct finance records without custom integration code.

What you can sync between Citus and Rillet

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 Rillet objects How this pairing syncs
Distributed tables Tables sharded across worker nodes by a distribution column; the main sync target for large datasets. Custom Field Synced with incremental and full sync per the Stacksync docs. Distributed tables is specific to Citus and Custom Field to Rillet — 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. Account Synced with incremental and full sync per the Stacksync docs. Reference tables is specific to Citus and Account to Rillet — each maps to any object or custom field on the other side.
Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. Customer Synced with incremental and full sync per the Stacksync docs. Local tables is specific to Citus and Customer to Rillet — each maps to any object or custom field on the other side.
Schemas Standard Postgres namespaces used to scope what a sync user can read and write. Vendor Synced with incremental and full sync per the Stacksync docs. Schemas is specific to Citus and Vendor to Rillet — each maps to any object or custom field on the other side.
Views Curated projections over distributed data, often used as read-only sync sources. Invoice Synced with incremental and full sync per the Stacksync docs. Views is specific to Citus and Invoice to Rillet — 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. Credit Memo Synced with incremental and full sync per the Stacksync docs. Sequences is specific to Citus and Credit Memo to Rillet — each maps to any object or custom field on the other side.

How changes propagate between Citus and Rillet

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 Rillet 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 written to Rillet through its API, with automatic retries and rate-limit backoff.

Rillet Citus Sub-second propagation

DetectionRillet pushes changes as they happen — webhook events backed by change data capture. Near real-time updates via change tracking.

DeliveryEach detected change is applied to Citus as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • Rillet: Subject to the platform's API rate limits.
What ships with Citus ⇄ Rillet

Connect Citus and Rillet for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Citus–Rillet connection.

Real-time

Two-way sync

Changes in Citus or Rillet instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Citus or Rillet 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 Rillet record.

Observability

Monitoring

Track your Citus ⇄ Rillet 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 Rillet.

How the Citus and Rillet 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

Rillet

Integration surface
REST API (OpenAPI-specified, with production and sandbox environments)
Authentication
API key generated in Rillet (Organization Setting -> API Access); uncheck Read Only for bidirectional sync, check Read Only for one-way sync
Change detection
Near real-time updates via change tracking; incremental sync per object, with delete detection (some objects checked every 1h or 4h)
Capabilities
read · write · CDC · webhooks
Rate limits
Subject to the platform's API rate limits.
Rillet setup guide
How it works

How to connect Citus to Rillet — 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.

  1. 01

    Connect your apps

    Authenticate Citus and Rillet with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Citus connected
    Rillet connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Citus and Rillet 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Citus ⇄ Rillet
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Citus Rillet
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Citus and Rillet integration FAQ

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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 355 integrations available for Citus and Rillet.

Popular · 4 of 355
All Citus integrations All Rillet integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own