Real-time
Two-way sync
Changes in Rillet or YugabyteDB instantly reflect in both systems. No stale data, no manual imports.
Accounting and finance ⇄ Database
Rillet to YugabyteDB integration — real-time, two-way sync
Keep Rillet and YugabyteDB 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 Rillet and YugabyteDB
Work with Rillet's financial data straight from YugabyteDB: 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 CDC Streams, Databases and Keyspaces, Tables, Indexes in YugabyteDB and keeps the two in sync bi-directionally and in real time. Your services read finance records with normal queries against YugabyteDB, 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
- Sync AR and collection status back to customer success tools ahead of renewals.
- Keep customers and invoices aligned between Rillet and a CRM so finance and sales work from the same account records.
- Consolidate data from regional YugabyteDB clusters into one reporting store.
- Run log-based CDC from YugabyteDB tables into a warehouse for analytics without batch dumps.
Write back safely
Updates written to the synced tables in YugabyteDB propagate into Rillet, so automations can create or correct finance records without custom integration code.
React to financial events
Changes in Rillet appear in YugabyteDB as row changes, so you can trigger downstream logic with the database tooling you already use.
Query finance data like any other data
Customers, invoices, and payments from Rillet live in YugabyteDB as regular tables or collections your team can join, index, and query.
What you can sync between Rillet and YugabyteDB
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.
| Rillet objects | YugabyteDB objects | |
|---|---|---|
| Journal Entry Synced with incremental and full sync per the Stacksync docs. | Tables Distributed SQL tables split into tablets; the primary read and write targets. | |
| Invoice Payment Synced with incremental and full sync per the Stacksync docs. | Indexes Global secondary indexes maintained transactionally alongside table writes. | |
| Charge Synced with incremental and full sync per the Stacksync docs. | Materialized Views Precomputed query results available in YSQL for read-side shaping. | |
| Reimbursement Synced with incremental and full sync per the Stacksync docs. | Schemas Postgres-style namespaces in YSQL used to organize synced data. | |
| Custom Field Synced with incremental and full sync per the Stacksync docs. | Sequences ID generation objects relevant when syncing writes into YSQL tables. | |
| Account Synced with incremental and full sync per the Stacksync docs. | CDC Streams Change streams over the storage-layer WAL consumed through logical replication or Debezium-compatible connectors. |
What ships with Rillet ⇄ YugabyteDB
Connect Rillet and YugabyteDB for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Rillet–YugabyteDB connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Rillet or YugabyteDB 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 Rillet or YugabyteDB record.
Observability
Monitoring
Track your Rillet ⇄ YugabyteDB sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Rillet and YugabyteDB.
How the Rillet and YugabyteDB connectors work
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.
YugabyteDB
- Integration surface
- SQL wire protocol (PostgreSQL-compatible YSQL) plus a Cassandra-compatible YCQL API
- Authentication
- Database credentials
- Change detection
- Native CDC from the write-ahead log via PostgreSQL logical replication or Debezium-compatible connectors
- Capabilities
- read · write · CDC
- Rate limits
- No API rate limits; throughput scales with cluster nodes and tablet distribution.
How it works
How to connect Rillet to YugabyteDB — 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 Rillet and YugabyteDB with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Rillet
connected
YugabyteDB
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Rillet and YugabyteDB 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 · Rillet ⇄ YugabyteDBCustomers 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.
Rillet YugabyteDBCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Rillet and YugabyteDB integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Rillet and YugabyteDB: authenticate both systems, choose the objects to sync (such as Rillet's Journal Entry and Invoice Payment), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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 Rillet and YugabyteDB: Write back safely; React to financial events; Query finance data like any other data. Updates written to the synced tables in YugabyteDB propagate into Rillet, so automations can create or correct finance records without custom integration code.
-
Rillet: 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. YugabyteDB: SQL wire protocol (PostgreSQL-compatible YSQL) plus a Cassandra-compatible YCQL API. Authentication: Database credentials. Stacksync manages authentication, retries, and rate limits on both sides.
-
Rillet: Several objects (Subsidiary, Tax Rate, Product, Contract, Bank Account, Bank Transaction) do not support incremental sync — historic sync only. YugabyteDB: CDC is exposed from the storage-layer WAL through PostgreSQL logical replication and Debezium-compatible connectors. Stacksync's field mapping accounts for these differences between Rillet and YugabyteDB 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 Rillet and YugabyteDB records are not retained after a sync operation.
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 Rillet and YugabyteDB.
Popular · 8 of 386
-
Rillet ⇄ InfluxDB -
Rillet ⇄ InterSystems IRIS -
Rillet ⇄ MarkLogic -
Rillet ⇄ Neo4j -
YugabyteDB ⇄ Stripe -
YugabyteDB ⇄ Workday -
YugabyteDB ⇄ Anaplan -
YugabyteDB ⇄ Chargebee
No integrations match .
