Two-way sync
Changes in Rillet or TiDB instantly reflect in both systems. No stale data, no manual imports.
Keep Rillet and TiDB 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 Custom Field, Account, Customer, Vendor from Rillet into Views, Columns, Indexes, Sequences in TiDB and keeps the two in sync bi-directionally and in real time. Your services read finance records with normal queries against TiDB, and rows your code writes or updates flow back into Rillet with validation, so the finance system stays the system of record.
Updates written to the synced tables in TiDB propagate into Rillet, so automations can create or correct finance records without custom integration code.
Changes in Rillet appear in TiDB as row changes, so you can trigger downstream logic with the database tooling you already use.
Customers, invoices, and payments from Rillet live in TiDB as regular tables or collections your team can join, index, and query.
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 | TiDB objects | |
|---|---|---|
| Vendor Synced with incremental and full sync per the Stacksync docs. | Views Logical views for shaping reads before syncing outward. | |
| Invoice Synced with incremental and full sync per the Stacksync docs. | Columns MySQL-compatible types mapped to fields in the paired system. | |
| Credit Memo Synced with incremental and full sync per the Stacksync docs. | Indexes Secondary indexes that keep incremental sync queries efficient. | |
| Bill Synced with incremental and full sync per the Stacksync docs. | Sequences Server-side ID generation relevant when external systems write rows. | |
| Journal Entry Synced with incremental and full sync per the Stacksync docs. | Databases MySQL-style schemas addressed by any MySQL-compatible client. | |
| Invoice Payment Synced with incremental and full sync per the Stacksync docs. | Tables Row data stored in TiKV; the primary unit for reads, writes, and CDC. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Rillet–TiDB connection.
Changes in Rillet or TiDB instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Rillet or TiDB data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Rillet or TiDB record.
Track your Rillet ⇄ TiDB sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Rillet and TiDB.
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 Rillet and TiDB 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 Rillet and TiDB 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 Rillet and TiDB: authenticate both systems, choose the objects to sync (such as Rillet's Vendor and Invoice), map fields visually, and changes propagate both ways in milliseconds — no code required.
Common patterns for Rillet and TiDB: Write back safely; React to financial events; Query finance data like any other data. Updates written to the synced tables in TiDB 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. TiDB: MySQL wire protocol (SQL). Authentication: Database credentials (MySQL-compatible username/password). Stacksync manages authentication, retries, and rate limits on both sides.
Rillet: Rillet is built for SaaS companies, with a general ledger organized around automated revenue recognition and month-end close. TiDB: TiCDC provides ordered row-level change capture and delivers to sinks such as Kafka or MySQL-compatible targets. Stacksync's field mapping accounts for these differences between Rillet and TiDB 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 TiDB records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Rillet and TiDB connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Rillet–TiDB integration in-house.
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 Rillet and TiDB.