Skip to content
Database ⇄ Accounting and finance

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

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

Work with Rillet's financial data straight from DuckDB: 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 Payment, Charge, Reimbursement, Custom Field from Rillet into Views, External files (Parquet/CSV/JSON), Attached databases, Database files in DuckDB and keeps the two in sync bi-directionally and in real time. Your services read finance records with normal queries against DuckDB, 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

  • Mirror journal entries and contract revenue data into a warehouse for board and ARR reporting.
  • Push billing events from a product or usage-metering system into Rillet for revenue recognition.
  • Use DuckDB as a transform step: read synced Parquet exports, aggregate with SQL, and write results back to an operational database.
  • Sync SaaS data to Parquet on object storage and query it with DuckDB without standing up a warehouse.

Write back safely

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

React to financial events

Changes in Rillet appear in DuckDB as row changes, so you can trigger downstream logic with the database tooling you already use.

Query finance data like any other data

Customers, invoices, and payments from Rillet live in DuckDB as regular tables or collections your team can join, index, and query.

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

DuckDB objects Rillet objects
Attached databases Additional database files or external systems attached into one session for cross-source queries. Invoice Payment Synced with incremental and full sync per the Stacksync docs.
Database files Single-file .duckdb databases that jobs read and write directly on disk or object storage. Charge Synced with incremental and full sync per the Stacksync docs.
Schemas Namespaces within a database used to organize tables in sync outputs. Reimbursement Synced with incremental and full sync per the Stacksync docs.
Tables Columnar tables created via SQL; the destination for materialized sync data. Custom Field Synced with incremental and full sync per the Stacksync docs.
Views SQL views used to shape or filter data for downstream consumers. Account Synced with incremental and full sync per the Stacksync docs.
External files (Parquet/CSV/JSON) Files DuckDB queries in place without loading, common as a sync interchange format. Customer Synced with incremental and full sync per the Stacksync docs.
What ships with DuckDB ⇄ Rillet

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the DuckDB and Rillet connectors work

DuckDB

Integration surface
In-process SQL engine via client libraries (Python, Node.js, JDBC, CLI); no server or network API by default
Authentication
None built in; access control is file-system level (MotherDuck adds token auth for its hosted service)
Change detection
Polling or full re-reads; no change feed or transaction log API
Capabilities
read · write
Rate limits
No API rate limits; throughput is bounded by local compute and I/O

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 DuckDB 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 DuckDB 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
    DuckDB connected
    Rillet connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the DuckDB 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 · DuckDB ⇄ 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
    DuckDB Rillet
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

DuckDB and Rillet 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 DuckDB and Rillet.

Popular · 8 of 386
All DuckDB 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