Skip to content
Database ⇄ Accounting and finance

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

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.

  • 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 MySQL and Rillet

Work with Rillet's financial data straight from MySQL: 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 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.

Common use cases

  • 01 Push billing events from a product or usage-metering system into Rillet for revenue recognition.
  • 02 Sync AR and collection status back to customer success tools ahead of renewals.
  • 03 Replicate ERP master data (customers, items, pricing) into the MySQL databases behind storefronts and portals
  • 04 Keep e-commerce orders in MySQL flowing into finance and fulfillment systems without export scripts

Common sync patterns

Internal tools without API plumbing

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

Write back safely

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

React to financial events

Changes in Rillet appear in MySQL as row changes, so you can trigger downstream logic with the database tooling you already use.

What you can sync between MySQL 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.

MySQL objects Rillet objects How this pairing syncs
Stored Procedures Server-side logic that can post-process synced rows. Charge Synced with incremental and full sync per the Stacksync docs. Stored Procedures is specific to MySQL and Charge to Rillet — each maps to any object or custom field on the other side.
Triggers An alternative change-capture mechanism when binlog access is unavailable. Reimbursement Synced with incremental and full sync per the Stacksync docs. Triggers is specific to MySQL and Reimbursement to Rillet — each maps to any object or custom field on the other side.
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. Databases (Schemas) is specific to MySQL and Custom Field to Rillet — each maps to any object or custom field on the other side.
Tables The primary sync target; rows map to records in connected systems. Account Synced with incremental and full sync per the Stacksync docs. Tables is specific to MySQL and Account to Rillet — each maps to any object or custom field on the other side.
Views Read-side projections used as outbound sync sources. Customer Synced with incremental and full sync per the Stacksync docs. Views is specific to MySQL and Customer to Rillet — each maps to any object or custom field on the other side.
Columns Field-level mapping targets with engine-typed values. Vendor Synced with incremental and full sync per the Stacksync docs. Columns is specific to MySQL and Vendor to Rillet — each maps to any object or custom field on the other side.

How changes propagate between MySQL 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.

MySQL Rillet Sub-second propagation

DetectionChanges in MySQL are captured at the source via change data capture — no polling loop against its API. Database triggers — Stacksync creates deterministic triggers for internal logging and syncing (requires log_bin_trust_function_creators=ON when.

DeliveryEach detected change is written to Rillet through its API, with automatic retries and rate-limit backoff.

Rillet MySQL 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 MySQL as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • MySQL: No API rate limits; throughput is bounded by connection limits and server resources.
  • Rillet: Subject to the platform's API rate limits.
What ships with MySQL ⇄ Rillet

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your MySQL ⇄ Rillet sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between MySQL and Rillet.

How the MySQL and Rillet connectors work

MySQL

Integration surface
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)
Change detection
Database triggers — Stacksync creates deterministic triggers for internal logging and syncing (requires log_bin_trust_function_creators=ON when binary logging is enabled)
Capabilities
read · write · CDC
Rate limits
No API rate limits; throughput is bounded by connection limits and server resources
MySQL setup guide

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 MySQL 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 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.

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

    Choose tables

    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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · MySQL ⇄ 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
    MySQL Rillet
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

MySQL 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 467 integrations available for MySQL and Rillet.

Popular · 7 of 467
All MySQL 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