Two-way sync
Changes in DuckDB or Tinybird instantly reflect in both systems. No stale data, no manual imports.
Keep DuckDB and Tinybird 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 DuckDB's rows in Tinybird, 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 DuckDB where the services that read from it get them at normal query latency.
Stacksync covers both directions with one connection. Tables or collections in DuckDB sync into Tinybird in real time, and result tables in Tinybird sync back into DuckDB, 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 Tinybird and keep DuckDB focused on its operational workload.
Rows from DuckDB land in Tinybird 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.
| DuckDB objects | Tinybird objects | |
|---|---|---|
| Views SQL views used to shape or filter data for downstream consumers. | Pipes Chained SQL nodes that transform Data Sources into query-ready results. | |
| External files (Parquet/CSV/JSON) Files DuckDB queries in place without loading, common as a sync interchange format. | API Endpoints Published Pipe outputs exposed as parameterized HTTP queries; the main read surface. | |
| Attached databases Additional database files or external systems attached into one session for cross-source queries. | Materialized Views Pipes materialized into new Data Sources for pre-aggregation at ingest time. | |
| Database files Single-file .duckdb databases that jobs read and write directly on disk or object storage. | Workspaces Project boundary that scopes Data Sources, Pipes, and tokens for a sync. | |
| Schemas Namespaces within a database used to organize tables in sync outputs. | Tokens Scoped credentials that control read and append rights per resource. | |
| Tables Columnar tables created via SQL; the destination for materialized sync data. | Data Sources ClickHouse-backed tables that receive ingested rows; the write target for syncs into Tinybird. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every DuckDB–Tinybird connection.
Changes in DuckDB or Tinybird instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever DuckDB or Tinybird data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single DuckDB or Tinybird record.
Track your DuckDB ⇄ Tinybird sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between DuckDB and Tinybird.
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 DuckDB and Tinybird 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 DuckDB and Tinybird 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 DuckDB and Tinybird: authenticate both systems, choose the objects to sync (such as DuckDB's Views and External files (Parquet/CSV/JSON)), map fields visually, and changes propagate both ways in milliseconds — no code required.
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 DuckDB and Tinybird: 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.
DuckDB: 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). Tinybird: REST API (Events API for ingestion, published query endpoints) with a ClickHouse SQL dialect. Authentication: Scoped auth tokens. Stacksync manages authentication, retries, and rate limits on both sides.
Tinybird: Tinybird is built on ClickHouse; Pipes are chained SQL nodes that can be published directly as parameterized HTTP endpoints. DuckDB: It queries Parquet, CSV, and JSON files directly without importing them, which makes file-based exchange a natural sync pattern. Stacksync's field mapping accounts for these differences between DuckDB and Tinybird 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 DuckDB and Tinybird records are not retained after a sync operation.
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 DuckDB and Tinybird.