Skip to content
Accounting and finance ⇄ Database

Rillet to VoltDB integration — real-time, two-way sync

Keep Rillet and VoltDB 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 VoltDB

Work with Rillet's financial data straight from VoltDB: 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 Account, Customer, Vendor, Invoice from Rillet into Replicated Tables, Stored Procedures, Materialized Views, Streams in VoltDB and keeps the two in sync bi-directionally and in real time. Your services read finance records with normal queries against VoltDB, 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

  • Keep customers and invoices aligned between Rillet and a CRM so finance and sales work from the same account records.
  • Mirror journal entries and contract revenue data into a warehouse for board and ARR reporting.
  • Keep product, plan, or entitlement state consistent between VoltDB and back-office systems.
  • Push aggregates from VoltDB materialized views into dashboards or operational tools.

Query finance data like any other data

Customers, invoices, and payments from Rillet live in VoltDB 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 VoltDB; Stacksync handles the API calls, rate limits, and retries against Rillet.

Write back safely

Updates written to the synced tables in VoltDB propagate into Rillet, so automations can create or correct finance records without custom integration code.

What you can sync between Rillet and VoltDB

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 VoltDB objects
Reimbursement Synced with incremental and full sync per the Stacksync docs. Partitioned Tables Tables sharded across partitions by a partitioning column; the primary transactional store and sync target.
Custom Field Synced with incremental and full sync per the Stacksync docs. Replicated Tables Small reference tables copied to every partition, a common landing spot for synced lookup data.
Account Synced with incremental and full sync per the Stacksync docs. Stored Procedures Precompiled transactional units that serve as the primary write interface.
Customer Synced with incremental and full sync per the Stacksync docs. Materialized Views Synchronously maintained aggregates over tables, useful as pre-computed read sources.
Vendor Synced with incremental and full sync per the Stacksync docs. Streams Insert-only constructs that feed the export subsystem with committed rows.
Invoice Synced with incremental and full sync per the Stacksync docs. Export Targets and Topics Connectors that push committed data to external systems such as Kafka or JDBC sinks.
What ships with Rillet ⇄ VoltDB

Connect Rillet and VoltDB for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Rillet–VoltDB connection.

Real-time

Two-way sync

Changes in Rillet or VoltDB instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Rillet or VoltDB 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 VoltDB record.

Observability

Monitoring

Track your Rillet ⇄ VoltDB 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 VoltDB.

How the Rillet and VoltDB 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.
Rillet setup guide

VoltDB

Integration surface
SQL over JDBC plus native client libraries and an HTTP/JSON interface
Authentication
Database credentials
Change detection
Export streams and topics push committed changes to configured targets; otherwise polling
Capabilities
read · write
Rate limits
No API rate limits; throughput is bounded by partition count and cluster sizing.
How it works

How to connect Rillet to VoltDB — 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.

  1. 01

    Connect your apps

    Authenticate Rillet and VoltDB with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Rillet connected
    VoltDB connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Rillet and VoltDB 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Rillet ⇄ VoltDB
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Rillet VoltDB
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Rillet and VoltDB integration FAQ

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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 386 integrations available for Rillet and VoltDB.

Popular · 8 of 386
All Rillet integrations All VoltDB integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own