Two-way sync
Changes in Dynamo DB or Rillet instantly reflect in both systems. No stale data, no manual imports.
Keep Dynamo DB 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 Global Tables, Tables, Items, Attributes in Dynamo DB and keeps the two in sync bi-directionally and in real time. Your services read finance records with normal queries against Dynamo DB, and rows your code writes or updates flow back into Rillet with validation, so the finance system stays the system of record.
Build dashboards and back-office tools directly on Dynamo DB; Stacksync handles the API calls, rate limits, and retries against Rillet.
Updates written to the synced tables in Dynamo DB propagate into Rillet, so automations can create or correct finance records without custom integration code.
Changes in Rillet appear in Dynamo DB as row changes, so you can trigger downstream logic with the database tooling you already use.
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.
| Dynamo DB objects | Rillet objects | How this pairing syncs | |
|---|---|---|---|
| Global Tables Multi-region replicas relevant when syncs must read from a specific region. | Charge Synced with incremental and full sync per the Stacksync docs. | Global Tables is specific to Dynamo DB and Charge to Rillet — each maps to any object or custom field on the other side. | |
| Tables The top-level containers a sync targets; each table is addressed independently. | Reimbursement Synced with incremental and full sync per the Stacksync docs. | Tables is specific to Dynamo DB and Reimbursement to Rillet — each maps to any object or custom field on the other side. | |
| Items Schemaless records keyed by partition (and optional sort) key, mapped to rows or SaaS objects in syncs. | Custom Field Synced with incremental and full sync per the Stacksync docs. | Items is specific to Dynamo DB and Custom Field to Rillet — each maps to any object or custom field on the other side. | |
| Attributes Per-item fields, including nested maps and lists, flattened or mapped during sync. | Account Synced with incremental and full sync per the Stacksync docs. | Attributes is specific to Dynamo DB and Account to Rillet — each maps to any object or custom field on the other side. | |
| Partition and Sort Keys The primary key pair used as the match key for bi-directional sync. | Customer Synced with incremental and full sync per the Stacksync docs. | Partition and Sort Keys is specific to Dynamo DB and Customer to Rillet — each maps to any object or custom field on the other side. | |
| Global Secondary Indexes Alternate access paths used when sync queries filter on non-key attributes. | Vendor Synced with incremental and full sync per the Stacksync docs. | Global Secondary Indexes is specific to Dynamo DB and Vendor 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 Dynamo DB are captured at the source via change data capture — no polling loop against its API. Item-level change streams via DynamoDB Streams or Kinesis Data Streams integration.
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 Dynamo DB as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Dynamo DB–Rillet connection.
Changes in Dynamo DB or Rillet instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Dynamo DB 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 Dynamo DB or Rillet record.
Track your Dynamo DB ⇄ Rillet sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Dynamo DB 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 Dynamo DB 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 Dynamo DB 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 Dynamo DB and Rillet: authenticate both systems, choose the objects to sync (such as Dynamo DB's Global Tables and Tables), map fields visually, and changes propagate both ways in milliseconds — no code required.
Common patterns for Dynamo DB and Rillet: Internal tools without API plumbing; Write back safely; React to financial events. Build dashboards and back-office tools directly on Dynamo DB; Stacksync handles the API calls, rate limits, and retries against Rillet.
Dynamo DB: Proprietary JSON-over-HTTPS API accessed through AWS SDKs; PartiQL supported for SQL-like queries. Authentication: AWS IAM credentials with SigV4 request signing. 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: The REST API authenticates with API keys and publishes an OpenAPI specification, with separate production and sandbox environments. Dynamo DB: PartiQL provides a SQL-compatible query layer over the same key-based access model. Stacksync's field mapping accounts for these differences between Dynamo DB 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 Dynamo DB and Rillet records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Dynamo DB and Rillet connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Dynamo DB–Rillet integration in-house.
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 371 integrations available for Dynamo DB and Rillet.