Two-way sync
Changes in MySQL or Rillet instantly reflect in both systems. No stale data, no manual imports.
Keep MySQL 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.
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 Credit Memo, Bill, Journal Entry, Invoice Payment from Rillet into Views, Columns, Primary and Unique Keys, JSON Columns in MySQL and keeps the two in sync bi-directionally and in real time. Your services read finance records with normal queries against MySQL, and rows your code writes or updates flow back into Rillet with validation, so the finance system stays the system of record.
Build dashboards and back-office tools directly on MySQL; Stacksync handles the API calls, rate limits, and retries against Rillet.
Updates written to the synced tables in MySQL propagate into Rillet, so automations can create or correct finance records without custom integration code.
Changes in Rillet appear in MySQL as row changes, so you can trigger downstream logic with the database tooling you already use.
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.
| MySQL objects | Rillet objects | |
|---|---|---|
| Stored Procedures Server-side logic that can post-process synced rows. | Charge Synced with incremental and full sync per the Stacksync docs. | |
| Triggers An alternative change-capture mechanism when binlog access is unavailable. | Reimbursement Synced with incremental and full sync per the Stacksync docs. | |
| Databases (Schemas) Top-level namespaces that scope a sync's reads and writes. | Custom Field Synced with incremental and full sync per the Stacksync docs. | |
| Tables The primary sync target; rows map to records in connected systems. | Account Synced with incremental and full sync per the Stacksync docs. | |
| Views Read-side projections used as outbound sync sources. | Customer Synced with incremental and full sync per the Stacksync docs. | |
| Columns Field-level mapping targets with engine-typed values. | Vendor Synced with incremental and full sync per the Stacksync docs. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every MySQL–Rillet connection.
Changes in MySQL or Rillet instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever MySQL or Rillet data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single MySQL or Rillet record.
Track your MySQL ⇄ Rillet sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between MySQL and Rillet.
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 MySQL 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.
Pick the MySQL 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.
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 MySQL and Rillet: authenticate both systems, choose the objects to sync (such as MySQL's Stored Procedures and Triggers), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on MySQL: Database triggers — Stacksync creates deterministic triggers for internal logging and syncing (requires log_bin_trust_function_creators=ON when binary logging is enabled). On Rillet: Near real-time updates via change tracking; incremental sync per object, with delete detection (some objects checked every 1h or 4h). Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Rillet side: Credit Memo, Bill, Journal Entry, Invoice Payment, plus custom fields where Rillet exposes them. On the MySQL side: Views, Columns, Primary and Unique Keys, JSON Columns. 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 MySQL and Rillet: Internal tools without API plumbing; Write back safely; React to financial events. Build dashboards and back-office tools directly on MySQL; Stacksync handles the API calls, rate limits, and retries against Rillet.
MySQL: SQL wire protocol (MySQL client/server protocol). Authentication: Database credentials entered as a connection string or parameters, with optional SSL root certificate upload and optional SSH tunnel (SSH user + SSH host). 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. 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 MySQL and Rillet.