Two-way sync
Changes in Rillet or Scaleway Postgres instantly reflect in both systems. No stale data, no manual imports.
Keep Rillet and Scaleway Postgres 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 Reimbursement, Custom Field, Account, Customer from Rillet into Schemas, Sequences, Columns, Tables in Scaleway Postgres and keeps the two in sync bi-directionally and in real time. Your services read finance records with normal queries against Scaleway Postgres, 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 Scaleway Postgres as row changes, so you can trigger downstream logic with the database tooling you already use.
Customers, invoices, and payments from Rillet live in Scaleway Postgres as regular tables or collections your team can join, index, and query.
Build dashboards and back-office tools directly on Scaleway Postgres; 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.
| Rillet objects | Scaleway Postgres objects | How this pairing syncs | |
|---|---|---|---|
| Invoice Payment Synced with incremental and full sync per the Stacksync docs. | Sequences Generate primary keys; sync tooling must respect them when writing rows. | Invoice Payment is specific to Rillet and Sequences to Scaleway Postgres — each maps to any object or custom field on the other side. | |
| Charge Synced with incremental and full sync per the Stacksync docs. | Columns Postgres-native types, including JSONB and arrays, are mapped to fields in the paired system. | Charge is specific to Rillet and Columns to Scaleway Postgres — each maps to any object or custom field on the other side. | |
| Reimbursement Synced with incremental and full sync per the Stacksync docs. | Tables Primary sync unit; each table maps to an object or table on the other side of the sync. | Reimbursement is specific to Rillet and Tables to Scaleway Postgres — each maps to any object or custom field on the other side. | |
| Custom Field Synced with incremental and full sync per the Stacksync docs. | Views Read-only sources for shaping data before it leaves the database. | Custom Field is specific to Rillet and Views to Scaleway Postgres — each maps to any object or custom field on the other side. | |
| Account Synced with incremental and full sync per the Stacksync docs. | Materialized views Precomputed result sets that can be read on a schedule for downstream syncs. | Account is specific to Rillet and Materialized views to Scaleway Postgres — each maps to any object or custom field on the other side. | |
| Customer Synced with incremental and full sync per the Stacksync docs. | Schemas Namespace tables so multiple applications or environments can be synced selectively. | Customer is specific to Rillet and Schemas to Scaleway Postgres — each maps to any object or custom field on the other side. |
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.
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 Scaleway Postgres as a row-level write, with types converted between the two schemas.
DetectionChanges in Scaleway Postgres are captured at the source via change data capture — no polling loop against its API. Log-based CDC via PostgreSQL logical replication where the managed instance permits it.
DeliveryEach detected change is written to Rillet through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Rillet–Scaleway Postgres connection.
Changes in Rillet or Scaleway Postgres instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Rillet or Scaleway Postgres 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 Scaleway Postgres record.
Track your Rillet ⇄ Scaleway Postgres sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Rillet and Scaleway Postgres.
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 Scaleway Postgres 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 Scaleway Postgres 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 Scaleway Postgres: authenticate both systems, choose the objects to sync (such as Rillet's Invoice Payment and Charge), map fields visually, and changes propagate both ways in milliseconds — no code required.
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 Scaleway Postgres records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Rillet and Scaleway Postgres connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Rillet–Scaleway Postgres integration in-house.
Yes — Stacksync ships production-grade connectors for both Rillet and Scaleway Postgres. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Rillet: Near real-time updates via change tracking; incremental sync per object, with delete detection (some objects checked every 1h or 4h). On Scaleway Postgres: Log-based CDC via PostgreSQL logical replication where the managed instance permits it; otherwise timestamp or query-based polling. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Rillet side: Reimbursement, Custom Field, Account, Customer, plus custom fields where Rillet exposes them. On the Scaleway Postgres side: Schemas, Sequences, Columns, Tables. Stacksync auto-detects both schemas and converts types between the two systems.
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 366 integrations available for Rillet and Scaleway Postgres.