Two-way sync
Changes in Google Cloud Spanner or MotherDuck instantly reflect in both systems. No stale data, no manual imports.
Keep Google Cloud Spanner and MotherDuck in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Operational databases and analytical warehouses want the same data at different moments. Analysts want Google Cloud Spanner's rows in MotherDuck, current and joinable, without a change-data-capture pipeline to maintain. Engineers want the outputs of warehouse work, such as aggregates, features, and segments, available in Google Cloud Spanner where the services that read from it get them at normal query latency.
Stacksync covers both directions with one connection. Tables or collections in Google Cloud Spanner sync into MotherDuck in real time, and result tables in MotherDuck sync back into Google Cloud Spanner, with schema and type mapping between the two systems handled for you.
Because changes stream continuously, analysts query current data instead of waiting for last night's load.
Point analytical queries at the synced copy in MotherDuck and keep Google Cloud Spanner focused on its operational workload.
Rows from Google Cloud Spanner land in MotherDuck as they change, replacing hand-built CDC and batch extract jobs.
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.
| Google Cloud Spanner objects | MotherDuck objects | |
|---|---|---|
| Databases Top-level containers that scope schema and sync configuration. | Attached Local DuckDB Databases Local files attached alongside cloud databases for hybrid queries. | |
| Tables Relational tables mapped one-to-one to sync targets. | Databases Cloud-hosted DuckDB databases that scope a sync's reads and writes. | |
| Rows The unit of read and write in each sync cycle, keyed by primary key. | Schemas Namespaces within a database used to organize synced tables. | |
| Interleaved tables Child rows physically co-located with parents; synced as related records. | Tables The main landing target for synced records and source for analysis. | |
| Secondary indexes Used to make incremental read queries efficient on non-key columns. | Views Modeled projections used as outbound sync sources. | |
| Change streams Capture inserts, updates, and deletes for log-style change data capture. | Database Shares Read-only copies of a database shared with other users or teams. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Google Cloud Spanner–MotherDuck connection.
Changes in Google Cloud Spanner or MotherDuck instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Google Cloud Spanner or MotherDuck data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Google Cloud Spanner or MotherDuck record.
Track your Google Cloud Spanner ⇄ MotherDuck sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Google Cloud Spanner and MotherDuck.
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 Google Cloud Spanner and MotherDuck 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 Google Cloud Spanner and MotherDuck 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 Google Cloud Spanner and MotherDuck: authenticate both systems, choose the objects to sync (such as Google Cloud Spanner's Databases and Tables), map fields visually, and changes propagate both ways in milliseconds — no code required.
Yes — Stacksync ships production-grade connectors for both Google Cloud Spanner and MotherDuck. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Google Cloud Spanner: Change streams (log-style CDC), or timestamp-based polling queries. On MotherDuck: Polling; no log-based CDC or webhook surface is exposed. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the MotherDuck side: Attached Local DuckDB Databases, Databases, Schemas, Tables, plus custom fields where MotherDuck exposes them. On the Google Cloud Spanner side: Tables, Rows, Interleaved tables, Secondary indexes. 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 Google Cloud Spanner and MotherDuck: Fresh analytics without loading windows; Offload heavy reads; Operational data in the warehouse, minus the pipeline. Because changes stream continuously, analysts query current data instead of waiting for last night's load.
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 386 integrations available for Google Cloud Spanner and MotherDuck.