Real-time
Two-way sync
Changes in RavenDB or Rillet instantly reflect in both systems. No stale data, no manual imports.
Database ⇄ Accounting and finance
RavenDB to Rillet integration — real-time, two-way sync
Keep RavenDB 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 RavenDB and Rillet
Work with Rillet's financial data straight from RavenDB: 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 Documents, Collections, Indexes, Attachments in RavenDB and keeps the two in sync bi-directionally and in real time. Your services read finance records with normal queries against RavenDB, 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
- 01 Keep customers and invoices aligned between Rillet and a CRM so finance and sales work from the same account records.
- 02 Mirror journal entries and contract revenue data into a warehouse for board and ARR reporting.
- 03 Keep external search indexes or caches current from RavenDB change feeds without custom pollers.
- 04 Stream RavenDB document changes into Postgres or a warehouse via data subscriptions for SQL analytics.
Common sync patterns
Query finance data like any other data
Customers, invoices, and payments from Rillet live in RavenDB as regular tables or collections your team can join, index, and query.
Internal tools without API plumbing
Build dashboards and back-office tools directly on RavenDB; Stacksync handles the API calls, rate limits, and retries against Rillet.
Write back safely
Updates written to the synced tables in RavenDB propagate into Rillet, so automations can create or correct finance records without custom integration code.
What you can sync between RavenDB 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.
| RavenDB objects | Rillet objects | How this pairing syncs | |
|---|---|---|---|
| Revisions Historical versions of documents, useful for audit-oriented replication | Credit Memo Synced with incremental and full sync per the Stacksync docs. | Revisions is specific to RavenDB and Credit Memo to Rillet — each maps to any object or custom field on the other side. | |
| Counters Numeric values attached to documents that change independently of the document body | Bill Synced with incremental and full sync per the Stacksync docs. | Counters is specific to RavenDB and Bill to Rillet — each maps to any object or custom field on the other side. | |
| Time series Timestamped measurements stored per document, synced for metrics analysis | Journal Entry Synced with incremental and full sync per the Stacksync docs. | Time series is specific to RavenDB and Journal Entry to Rillet — each maps to any object or custom field on the other side. | |
| Data subscriptions Server-side change feeds that push matching documents to consumers | Invoice Payment Synced with incremental and full sync per the Stacksync docs. | Data subscriptions is specific to RavenDB and Invoice Payment to Rillet — each maps to any object or custom field on the other side. | |
| Documents JSON records, the primary unit read and written during sync | Charge Synced with incremental and full sync per the Stacksync docs. | Documents is specific to RavenDB and Charge to Rillet — each maps to any object or custom field on the other side. | |
| Collections Groupings of documents by type, mapped to tables in relational targets | Reimbursement Synced with incremental and full sync per the Stacksync docs. | Collections is specific to RavenDB and Reimbursement to Rillet — each maps to any object or custom field on the other side. |
How changes propagate between RavenDB and Rillet
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.
RavenDB Rillet Sub-second propagation
DetectionChanges in RavenDB are captured at the source via change data capture — no polling loop against its API. Data subscriptions and the Changes API provide server-pushed change feeds.
DeliveryEach detected change is written to Rillet through its API, with automatic retries and rate-limit backoff.
Rillet RavenDB Sub-second propagation
DetectionRillet pushes changes as they happen — webhook events backed by change data capture. Near real-time updates via change tracking.
DeliveryEach detected change is written to RavenDB through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- RavenDB: Throughput bounded by cluster resources rather than API quotas.
- Rillet: Subject to the platform's API rate limits.
What ships with RavenDB ⇄ Rillet
Connect RavenDB and Rillet for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every RavenDB–Rillet connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever RavenDB 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 RavenDB or Rillet record.
Observability
Monitoring
Track your RavenDB ⇄ Rillet sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between RavenDB and Rillet.
How the RavenDB and Rillet connectors work
RavenDB
- Integration surface
- HTTP REST API with official clients (.NET, Java, Node.js, Python, and others)
- Authentication
- X.509 client certificates on secured servers, instead of username and password
- Change detection
- data subscriptions and the Changes API provide server-pushed change feeds
- Capabilities
- read · write · CDC
- Rate limits
- throughput bounded by cluster resources rather than API quotas
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 RavenDB 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 RavenDB 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.
RavenDB
connected
Rillet
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the RavenDB 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 · RavenDB ⇄ 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.
RavenDB RilletCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
RavenDB and Rillet integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between RavenDB and Rillet: authenticate both systems, choose the objects to sync (such as RavenDB's Revisions and Counters), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Rillet: The REST API authenticates with API keys and publishes an OpenAPI specification, with separate production and sandbox environments. RavenDB: Data subscriptions deliver a resumable, reliable stream of documents matching a query, which fits continuous sync without external CDC tooling. Stacksync's field mapping accounts for these differences between RavenDB 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 RavenDB and Rillet records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed RavenDB and Rillet connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom RavenDB–Rillet integration in-house.
-
Yes — Stacksync ships production-grade connectors for both RavenDB and Rillet. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on RavenDB: Data subscriptions and the Changes API provide server-pushed change feeds. 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.
SECURITY
Security teams trust 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 353 integrations available for RavenDB and Rillet.
Popular · 2 of 353
No integrations match .
