Real-time
Two-way sync
Changes in Rillet or Supabase instantly reflect in both systems. No stale data, no manual imports.
Accounting and finance ⇄ Database
Rillet to Supabase integration — real-time, two-way sync
Keep Rillet and Supabase 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 Rillet and Supabase
Work with Rillet's financial data straight from Supabase: 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 Invoice, Credit Memo, Bill, Journal Entry from Rillet into Schemas, auth.users, Row Level Security Policies, JSONB Columns in Supabase and keeps the two in sync bi-directionally and in real time. Your services read finance records with normal queries against Supabase, 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
- Mirror journal entries and contract revenue data into a warehouse for board and ARR reporting.
- Push billing events from a product or usage-metering system into Rillet for revenue recognition.
- Mirror billing and subscription records into Supabase tables the application can join directly
- Reflect auth.users state into support and CRM systems so teams see account status without querying the database
Internal tools without API plumbing
Build dashboards and back-office tools directly on Supabase; Stacksync handles the API calls, rate limits, and retries against Rillet.
Write back safely
Updates written to the synced tables in Supabase propagate into Rillet, so automations can create or correct finance records without custom integration code.
React to financial events
Changes in Rillet appear in Supabase as row changes, so you can trigger downstream logic with the database tooling you already use.
What you can sync between Rillet and Supabase
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 | Supabase objects | |
|---|---|---|
| Credit Memo Synced with incremental and full sync per the Stacksync docs. | Storage Object Metadata File metadata rows that can be joined to synced application data. | |
| Bill Synced with incremental and full sync per the Stacksync docs. | Tables Standard Postgres tables; the primary two-way sync target. | |
| Journal Entry Synced with incremental and full sync per the Stacksync docs. | Views Read-side projections exposed to outbound syncs. | |
| Invoice Payment Synced with incremental and full sync per the Stacksync docs. | Schemas Namespaces (public and custom) that scope sync access. | |
| Charge Synced with incremental and full sync per the Stacksync docs. | auth.users Managed authentication users, often mirrored into CRM or support systems. | |
| Reimbursement Synced with incremental and full sync per the Stacksync docs. | Row Level Security Policies Row-level access rules that govern what the REST layer exposes. |
What ships with Rillet ⇄ Supabase
Connect Rillet and Supabase for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Rillet–Supabase connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Rillet or Supabase 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 Rillet or Supabase record.
Observability
Monitoring
Track your Rillet ⇄ Supabase sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Rillet and Supabase.
How the Rillet and Supabase connectors work
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.
Supabase
- Integration surface
- Direct PostgreSQL wire protocol connection, plus an auto-generated REST API (PostgREST)
- Authentication
- Database credentials (connection string) for SQL access; API keys (anon / service role) for the REST layer
- Change detection
- Log-based CDC via Postgres logical replication, the same WAL feed that powers Supabase Realtime; database webhooks can also fire on row changes
- Capabilities
- read · write · CDC · webhooks
- Rate limits
- SQL access is bounded by connection limits (pooled connections are provided); the REST layer is subject to the platform's limits
How it works
How to connect Rillet to Supabase — 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.
- 01
Connect your apps
Authenticate Rillet and Supabase with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Rillet
connected
Supabase
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Rillet and Supabase 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.
objects · Rillet ⇄ SupabaseCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Rillet SupabaseCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Rillet and Supabase integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Rillet and Supabase: authenticate both systems, choose the objects to sync (such as Rillet's Credit Memo and Bill), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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. Supabase: Direct PostgreSQL wire protocol connection, plus an auto-generated REST API (PostgREST). Authentication: Database credentials (connection string) for SQL access; API keys (anon / service role) for the REST layer. Stacksync manages authentication, retries, and rate limits on both sides.
-
Rillet: The REST API authenticates with API keys and publishes an OpenAPI specification, with separate production and sandbox environments. Supabase: Supabase Realtime is built on the Postgres write-ahead log, streaming row changes over websockets. Stacksync's field mapping accounts for these differences between Rillet and Supabase 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 Supabase records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Rillet and Supabase connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Rillet–Supabase integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Rillet and Supabase. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
SECURITY
Security teams love 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.
SOC 2 type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 386 integrations available for Rillet and Supabase.
Popular · 8 of 386
-
Rillet ⇄ Firebase -
Rillet ⇄ SingleStore -
Rillet ⇄ Amazon Aurora -
Rillet ⇄ Amazon Lightsail -
Supabase ⇄ Anaplan -
Supabase ⇄ Chargebee -
Supabase ⇄ Hyperline -
Supabase ⇄ Pigment
No integrations match .
