Skip to content
Data warehouse ⇄ Accounting and finance

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

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

Land the financial records from Rillet in Exasol 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 Exasol in real time, and the connection works in both directions: values computed in Exasol 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

  • 01 Mirror journal entries and contract revenue data into a warehouse for board and ARR reporting.
  • 02 Push billing events from a product or usage-metering system into Rillet for revenue recognition.
  • 03 Consolidate data from multiple operational databases into Exasol as the central analytics layer.
  • 04 Keep dimension tables such as customers and products aligned with the systems of record.

Common sync patterns

Write-back of computed fields

Scores or segments computed in Exasol, 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 Exasol gives you a durable, queryable record of financial data for month-end and audit questions.

Finance analytics without ETL

Invoices, payments, and customer records from Rillet arrive in Exasol as queryable tables, current within seconds instead of a day behind.

What you can sync between Exasol 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.

Exasol objects Rillet objects How this pairing syncs
Users and roles Grant read/write access for the dedicated integration account. Custom Field Synced with incremental and full sync per the Stacksync docs. Users and roles is specific to Exasol and Custom Field to Rillet — each maps to any object or custom field on the other side.
Schemas Namespaces that group the tables a sync reads from or writes into. Account Synced with incremental and full sync per the Stacksync docs. Schemas is specific to Exasol and Account to Rillet — each maps to any object or custom field on the other side.
Tables Primary sync target; columnar relational tables written with standard SQL. Customer Synced with incremental and full sync per the Stacksync docs. Tables is specific to Exasol and Customer to Rillet — each maps to any object or custom field on the other side.
Views Read-only query surfaces often used as curated sources for reverse ETL. Vendor Synced with incremental and full sync per the Stacksync docs. Views is specific to Exasol and Vendor to Rillet — each maps to any object or custom field on the other side.
Virtual schemas Federated views over external sources; useful for deciding what needs physical replication. Invoice Synced with incremental and full sync per the Stacksync docs. Virtual schemas is specific to Exasol and Invoice to Rillet — each maps to any object or custom field on the other side.
UDF scripts In-database functions that can transform synced data after load. Credit Memo Synced with incremental and full sync per the Stacksync docs. UDF scripts is specific to Exasol and Credit Memo to Rillet — each maps to any object or custom field on the other side.

How changes propagate between Exasol 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.

Exasol Rillet Interval-based propagation

DetectionStacksync polls Exasol for changes on an incremental schedule, reading only records changed since the previous pass. Polling with timestamp or key columns.

DeliveryEach detected change is written to Rillet through its API, with automatic retries and rate-limit backoff.

Rillet Exasol 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 applied to Exasol as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • Exasol: No API quota; concurrency is bounded by cluster resources and session limits.
  • Rillet: Subject to the platform's API rate limits.
What ships with Exasol ⇄ Rillet

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Exasol ⇄ Rillet sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Exasol and Rillet.

How the Exasol and Rillet connectors work

Exasol

Integration surface
SQL over JDBC/ODBC drivers and a WebSocket-based client protocol
Authentication
Database credentials (username and password)
Change detection
Polling with timestamp or key columns; Exasol does not expose a transaction-log change feed to clients
Capabilities
read · write
Rate limits
No API quota; concurrency is bounded by cluster resources and session 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.
Rillet setup guide
How it works

How to connect Exasol 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.

  1. 01

    Connect your apps

    Authenticate Exasol 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.

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

    Choose tables

    Pick the Exasol 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Exasol ⇄ Rillet
    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
    Exasol Rillet
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Exasol and Rillet integration FAQ

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.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
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 355 integrations available for Exasol and Rillet.

Popular · 6 of 355
All Exasol integrations All Rillet 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