Two-way sync
Changes in Google Cloud SQL or Rillet instantly reflect in both systems. No stale data, no manual imports.
Keep Google Cloud SQL 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 Bill, Journal Entry, Invoice Payment, Charge from Rillet into Views, Transaction logs, Instances, Databases in Google Cloud SQL and keeps the two in sync bi-directionally and in real time. Your services read finance records with normal queries against Google Cloud SQL, and rows your code writes or updates flow back into Rillet with validation, so the finance system stays the system of record.
Changes in Rillet appear in Google Cloud SQL as row changes, so you can trigger downstream logic with the database tooling you already use.
Customers, invoices, and payments from Rillet live in Google Cloud SQL as regular tables or collections your team can join, index, and query.
Build dashboards and back-office tools directly on Google Cloud SQL; Stacksync handles the API calls, rate limits, and retries against 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.
| Google Cloud SQL objects | Rillet objects | |
|---|---|---|
| Rows Read and written by primary key during each sync cycle. | Account Synced with incremental and full sync per the Stacksync docs. | |
| Views Read-only sources for shaping data before syncing it out. | Customer Synced with incremental and full sync per the Stacksync docs. | |
| Transaction logs MySQL binlog or PostgreSQL WAL, the source for log-based change capture. | Vendor Synced with incremental and full sync per the Stacksync docs. | |
| Instances The managed MySQL, PostgreSQL, or SQL Server server a sync connects to. | Invoice Synced with incremental and full sync per the Stacksync docs. | |
| Databases Scope the tables included in a sync configuration. | Credit Memo Synced with incremental and full sync per the Stacksync docs. | |
| Schemas Namespace tables in PostgreSQL and SQL Server instances. | Bill Synced with incremental and full sync per the Stacksync docs. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Google Cloud SQL–Rillet connection.
Changes in Google Cloud SQL or Rillet instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Google Cloud SQL 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 Google Cloud SQL or Rillet record.
Track your Google Cloud SQL ⇄ Rillet sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Google Cloud SQL 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 Google Cloud SQL 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 Google Cloud SQL 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 Google Cloud SQL and Rillet: authenticate both systems, choose the objects to sync (such as Google Cloud SQL's Rows and Views), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on Google Cloud SQL: Engine-dependent log-based CDC: MySQL binlog, PostgreSQL logical replication, SQL Server change tracking; polling as a fallback. 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: Bill, Journal Entry, Invoice Payment, Charge, plus custom fields where Rillet exposes them. On the Google Cloud SQL side: Views, Transaction logs, Instances, Databases. 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 Google Cloud SQL and Rillet: React to financial events; Query finance data like any other data; Internal tools without API plumbing. Changes in Rillet appear in Google Cloud SQL as row changes, so you can trigger downstream logic with the database tooling you already use.
Google Cloud SQL: Native SQL wire protocols (MySQL, PostgreSQL, SQL Server) plus a REST admin API for instance management. Authentication: Database credentials; IAM database authentication is available for MySQL and PostgreSQL. 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 Google Cloud SQL and Rillet.