Two-way sync
Changes in MongoDB or Rillet instantly reflect in both systems. No stale data, no manual imports.
Keep MongoDB 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 Reimbursement, Custom Field, Account, Customer from Rillet into Databases, Collections, Documents, Embedded documents and arrays in MongoDB and keeps the two in sync bi-directionally and in real time. Your services read finance records with normal queries against MongoDB, and rows your code writes or updates flow back into Rillet with validation, so the finance system stays the system of record.
Customers, invoices, and payments from Rillet live in MongoDB as regular tables or collections your team can join, index, and query.
Build dashboards and back-office tools directly on MongoDB; Stacksync handles the API calls, rate limits, and retries against Rillet.
Updates written to the synced tables in MongoDB propagate into Rillet, so automations can create or correct finance records without custom integration code.
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.
| MongoDB objects | Rillet objects | How this pairing syncs | |
|---|---|---|---|
| Databases Logical groupings of collections that scope a sync connection. | Invoice Synced with incremental and full sync per the Stacksync docs. | Databases is specific to MongoDB and Invoice to Rillet — each maps to any object or custom field on the other side. | |
| Collections The table-like sync unit; each collection maps to a table or object in the paired system. | Credit Memo Synced with incremental and full sync per the Stacksync docs. | Collections is specific to MongoDB and Credit Memo to Rillet — each maps to any object or custom field on the other side. | |
| Documents BSON records created, updated, and deleted during syncs, keyed by _id. | Bill Synced with incremental and full sync per the Stacksync docs. | Documents is specific to MongoDB and Bill to Rillet — each maps to any object or custom field on the other side. | |
| Embedded documents and arrays Nested structures that syncs flatten or map to related records in relational targets. | Journal Entry Synced with incremental and full sync per the Stacksync docs. | Embedded documents and arrays is specific to MongoDB and Journal Entry to Rillet — each maps to any object or custom field on the other side. | |
| Indexes Keep lookups by sync key fast on large collections. | Invoice Payment Synced with incremental and full sync per the Stacksync docs. | Indexes is specific to MongoDB and Invoice Payment to Rillet — each maps to any object or custom field on the other side. | |
| Views Read-only aggregation-defined sources for filtered sync datasets. | Charge Synced with incremental and full sync per the Stacksync docs. | Views is specific to MongoDB and Charge to Rillet — 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.
DetectionChanges in MongoDB are captured at the source via change data capture — no polling loop against its API. MongoDB oplog and change streams (requires the database to run as a replica set — even single-node).
DeliveryEach detected change is written to Rillet through its API, with automatic retries and rate-limit backoff.
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 MongoDB as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every MongoDB–Rillet connection.
Changes in MongoDB or Rillet instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever MongoDB 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 MongoDB or Rillet record.
Track your MongoDB ⇄ Rillet sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between MongoDB 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 MongoDB 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 MongoDB 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 MongoDB and Rillet: authenticate both systems, choose the objects to sync (such as MongoDB's Databases and Collections), map fields visually, and changes propagate both ways in milliseconds — no code required.
MongoDB: MongoDB wire protocol via official drivers; Atlas additionally offers an administration REST API for cluster management. Authentication: Database credentials (username/password) or TLS/SSL X.509 certificate (.pem upload), entered individually or via a MongoDB connection string (SRV or standard); Stacksync IP allowlisting 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. 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. MongoDB: Replica set configuration is required even for a single node — standalone MongoDB cannot be change-tracked. Stacksync's field mapping accounts for these differences between MongoDB 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 MongoDB and Rillet records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed MongoDB and Rillet connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom MongoDB–Rillet integration in-house.
Yes — Stacksync ships production-grade connectors for both MongoDB and Rillet. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
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 461 integrations available for MongoDB and Rillet.