Real-time
Two-way sync
Changes in Rillet or TimescaleDB instantly reflect in both systems. No stale data, no manual imports.
Accounting and finance ⇄ Database
Rillet to TimescaleDB integration — real-time, two-way sync
Keep Rillet and TimescaleDB 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 TimescaleDB
Work with Rillet's financial data straight from TimescaleDB: 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 Charge, Reimbursement, Custom Field, Account from Rillet into Chunks, Continuous Aggregates, Regular PostgreSQL Tables, Views in TimescaleDB and keeps the two in sync bi-directionally and in real time. Your services read finance records with normal queries against TimescaleDB, 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.
- Keep device or asset reference tables bi-directionally in sync between TimescaleDB and an ERP.
- Consolidate metrics from several services into one hypertable to serve a single reporting layer.
Internal tools without API plumbing
Build dashboards and back-office tools directly on TimescaleDB; Stacksync handles the API calls, rate limits, and retries against Rillet.
Write back safely
Updates written to the synced tables in TimescaleDB propagate into Rillet, so automations can create or correct finance records without custom integration code.
React to financial events
Changes in Rillet appear in TimescaleDB as row changes, so you can trigger downstream logic with the database tooling you already use.
What you can sync between Rillet and TimescaleDB
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 | TimescaleDB objects | |
|---|---|---|
| Charge Synced with incremental and full sync per the Stacksync docs. | Schemas Postgres namespaces used to separate synced datasets by team or environment. | |
| Reimbursement Synced with incremental and full sync per the Stacksync docs. | Hypertables Time-partitioned tables that hold the main time-series data; the primary read and write target in syncs. | |
| Custom Field Synced with incremental and full sync per the Stacksync docs. | Chunks Time-bounded partitions of a hypertable; syncs read and write through the parent hypertable and never address chunks directly. | |
| Account Synced with incremental and full sync per the Stacksync docs. | Continuous Aggregates Incrementally maintained rollups that serve as pre-aggregated read sources for downstream systems. | |
| Customer Synced with incremental and full sync per the Stacksync docs. | Regular PostgreSQL Tables Relational reference data such as devices, tenants, or accounts synced alongside the series data. | |
| Vendor Synced with incremental and full sync per the Stacksync docs. | Views Standard SQL views used to shape or filter data for consumers. |
What ships with Rillet ⇄ TimescaleDB
Connect Rillet and TimescaleDB for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Rillet–TimescaleDB connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Rillet or TimescaleDB 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 TimescaleDB record.
Observability
Monitoring
Track your Rillet ⇄ TimescaleDB 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 TimescaleDB.
How the Rillet and TimescaleDB 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.
TimescaleDB
- Integration surface
- SQL wire protocol (PostgreSQL)
- Authentication
- Database credentials
- Change detection
- Log-based capture via PostgreSQL logical decoding where the deployment allows it — hypertable changes surface on the underlying chunk tables and must be remapped to the parent — or timestamp-based polling on time columns; regular Postgres tables replicate through standard logical replication
- Capabilities
- read · write · CDC
- Rate limits
- No API rate limits; throughput is bounded by database resources and connection limits.
How it works
How to connect Rillet to TimescaleDB — 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 Rillet and TimescaleDB with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Rillet
connected
TimescaleDB
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Rillet and TimescaleDB 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 · Rillet ⇄ TimescaleDBCustomers 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.
Rillet TimescaleDBCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Rillet and TimescaleDB integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Rillet and TimescaleDB: authenticate both systems, choose the objects to sync (such as Rillet's Charge and Reimbursement), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Rillet side: Charge, Reimbursement, Custom Field, Account, plus custom fields where Rillet exposes them. On the TimescaleDB side: Chunks, Continuous Aggregates, Regular PostgreSQL Tables, Views. Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for Rillet and TimescaleDB: Internal tools without API plumbing; Write back safely; React to financial events. Build dashboards and back-office tools directly on TimescaleDB; Stacksync handles the API calls, rate limits, and retries against Rillet.
-
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. TimescaleDB: SQL wire protocol (PostgreSQL). Authentication: Database credentials. 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. TimescaleDB: Native compression converts older chunks to a columnar layout while keeping them queryable with the same SQL. Stacksync's field mapping accounts for these differences between Rillet and TimescaleDB without custom code.
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.
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 386 integrations available for Rillet and TimescaleDB.
Popular · 8 of 386
-
Rillet ⇄ Apache Cassandra -
Rillet ⇄ Azure Cosmos DB -
Rillet ⇄ Azure SQL Database -
Rillet ⇄ Citus -
TimescaleDB ⇄ Hyperline -
TimescaleDB ⇄ Pigment -
TimescaleDB ⇄ QuickBooks -
TimescaleDB ⇄ Stripe
No integrations match .
