Real-time
Two-way sync
Changes in Databricks or Rillet instantly reflect in both systems. No stale data, no manual imports.
Data warehouse ⇄ Accounting and finance
Databricks to Rillet integration — real-time, two-way sync
Keep Databricks 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 Databricks and Rillet
Land the financial records from Rillet in Databricks continuously, and write results back, without building or maintaining a pipeline.
Finance data belongs in the warehouse: revenue, invoices, payments, and customers joined with everything else the business measures. Getting it there usually means an extraction pipeline that breaks quietly and delivers yesterday's numbers.
Stacksync syncs Account, Customer, Vendor, Invoice from Rillet into tables in Databricks in real time, and the connection works in both directions: values computed in Databricks can be written back to fields in Rillet where you want them operational. Schema changes are handled, API limits are managed, and the sync is something you configure rather than code you maintain.
Common use cases
- Sync AR and collection status back to customer success tools ahead of renewals.
- Keep customers and invoices aligned between Rillet and a CRM so finance and sales work from the same account records.
- Land CRM and ERP records in Delta tables continuously so lakehouse models work from current operational data.
- Use Change Data Feed to propagate only changed rows to downstream apps instead of full-table scans.
Revenue joined with everything else
Analysts combine Rillet's financial records with product, marketing, or operational data already in Databricks for reporting the finance system cannot do alone.
Write-back of computed fields
Scores or segments computed in Databricks, like payment-risk flags or customer tiers, sync back onto records in Rillet where the finance team can act on them.
Queryable history for audit and reconciliation
A continuously synced copy in Databricks gives you a durable, queryable record of financial data for month-end and audit questions.
What you can sync between Databricks 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.
| Databricks objects | Rillet objects | |
|---|---|---|
| Delta Tables The primary read and write target; operational data lands here as managed or external tables. | Account Synced with incremental and full sync per the Stacksync docs. | |
| Views Curated read-only projections used as sync sources for downstream tools. | Customer Synced with incremental and full sync per the Stacksync docs. | |
| Materialized Views Precomputed results read on a schedule for reverse-ETL style syncs. | Vendor Synced with incremental and full sync per the Stacksync docs. | |
| Volumes Unity Catalog file storage used for staging bulk loads. | Invoice Synced with incremental and full sync per the Stacksync docs. | |
| SQL Warehouses The compute endpoint a sync connects to for query execution. | Credit Memo Synced with incremental and full sync per the Stacksync docs. | |
| Change Data Feed Row-level change records on Delta tables that drive incremental reads. | Bill Synced with incremental and full sync per the Stacksync docs. |
What ships with Databricks ⇄ Rillet
Connect Databricks and Rillet for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Databricks–Rillet connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Databricks 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 Databricks or Rillet record.
Observability
Monitoring
Track your Databricks ⇄ Rillet sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Databricks and Rillet.
How the Databricks and Rillet connectors work
Databricks
- Integration surface
- SQL over JDBC/ODBC via SQL warehouses, plus a REST API including statement execution
- Authentication
- Personal access tokens or OAuth machine-to-machine credentials for service principals
- Change detection
- Delta Lake Change Data Feed for row-level changes; otherwise incremental polling on watermark columns
- Capabilities
- read · write · CDC
- Rate limits
- Throughput depends on the SQL warehouse size; API calls are subject to workspace rate limits
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.
How it works
How to connect Databricks 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.
- 01
Connect your apps
Authenticate Databricks 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.
Databricks
connected
Rillet
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Databricks 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.
objects · Databricks ⇄ RilletCustomers 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.
Databricks RilletCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Databricks and Rillet integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Databricks and Rillet: authenticate both systems, choose the objects to sync (such as Databricks's Delta Tables and Views), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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 Databricks and Rillet: Revenue joined with everything else; Write-back of computed fields; Queryable history for audit and reconciliation. Analysts combine Rillet's financial records with product, marketing, or operational data already in Databricks for reporting the finance system cannot do alone.
-
Databricks: SQL over JDBC/ODBC via SQL warehouses, plus a REST API including statement execution. Authentication: Personal access tokens or OAuth machine-to-machine credentials for service principals. 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.
-
Rillet: Rillet is built for SaaS companies, with a general ledger organized around automated revenue recognition and month-end close. Databricks: Delta Lake's Change Data Feed records row-level inserts, updates, and deletes, enabling incremental sync without full scans. Stacksync's field mapping accounts for these differences between Databricks and Rillet 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 Databricks and Rillet records are not retained after a sync operation.
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 Databricks and Rillet.
Popular · 8 of 386
-
Databricks ⇄ Stripe -
Databricks ⇄ Workday -
Databricks ⇄ Anaplan -
Databricks ⇄ Chargebee -
Rillet ⇄ StarRocks -
Rillet ⇄ Teradata Vantage -
Rillet ⇄ Tinybird -
Rillet ⇄ Vertica
No integrations match .
