Two-way sync
Changes in BigQuery or Rillet instantly reflect in both systems. No stale data, no manual imports.
Keep BigQuery 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.
Finance teams sync Rillet into BigQuery to extend accounting analysis beyond the ledger. Accounts, Invoices, and Bills replicate into BigQuery Tables, where they join revenue, product, and CRM data in a single Dataset for reporting.
Stacksync syncs Charge, Reimbursement, Custom Field, Account from Rillet into tables in BigQuery in real time, and the connection works in both directions: values computed in BigQuery 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.
Rillet Accounts and balances sync into a BigQuery Dataset for management reporting.
Invoices, Credit Memos, and Bills land in partitioned BigQuery Tables for aging and cash analysis.
Customers and Vendors replicate to clustered BigQuery Tables joined against operational data.
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.
| BigQuery objects | Rillet objects | How this pairing syncs | |
|---|---|---|---|
| Tables The syncable unit: only tables can be synced per the Stacksync docs. | Credit Memo Synced with incremental and full sync per the Stacksync docs. | Tables is specific to BigQuery and Credit Memo to Rillet — each maps to any object or custom field on the other side. | |
| Partitioned tables Synced like regular tables; partition columns map to target fields. | Bill Synced with incremental and full sync per the Stacksync docs. | Partitioned tables is specific to BigQuery and Bill to Rillet — each maps to any object or custom field on the other side. | |
| Clustered tables Supported; clustering is transparent to the sync. | Journal Entry Synced with incremental and full sync per the Stacksync docs. | Clustered tables is specific to BigQuery and Journal Entry to Rillet — each maps to any object or custom field on the other side. | |
| Datasets Organizational container — you pick which dataset’s tables to sync. | Invoice Payment Synced with incremental and full sync per the Stacksync docs. | Datasets is specific to BigQuery and Invoice Payment to Rillet — each maps to any object or custom field on the other side. | |
| Projects Connection scope: the service account grants access per project. | Charge Synced with incremental and full sync per the Stacksync docs. | Projects is specific to BigQuery and Charge 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 BigQuery are captured at the source via change data capture — no polling loop against its API. Real-time notification service deployed into your Google Cloud project: Eventarc ("a notification service that enables real-time updates to happen").
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 BigQuery as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every BigQuery–Rillet connection.
Changes in BigQuery or Rillet instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever BigQuery 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 BigQuery or Rillet record.
Track your BigQuery ⇄ Rillet sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between BigQuery 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 BigQuery 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 BigQuery 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 BigQuery and Rillet: authenticate both systems, choose the objects to sync (such as BigQuery's Tables and Partitioned tables), map fields visually, and changes propagate both ways in milliseconds — no code required.
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 BigQuery and Rillet records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed BigQuery and Rillet connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom BigQuery–Rillet integration in-house.
Yes — Stacksync ships production-grade connectors for both BigQuery and Rillet. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on BigQuery: Real-time notification service deployed into your Google Cloud project: Eventarc ("a notification service that enables real-time updates to happen") with a Cloud Run "secure portal for real-time notification service in. On Rillet: Near real-time updates via change tracking; incremental sync per object, with delete detection (some objects checked every 1h or 4h). Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Rillet side: Charge, Reimbursement, Custom Field, Account, plus custom fields where Rillet exposes them. On the BigQuery side: Tables, Partitioned tables, Clustered tables, Datasets. Stacksync auto-detects both schemas and converts types between the two systems.
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 463 integrations available for BigQuery and Rillet.