Real-time
Two-way sync
Changes in DuckDB or Pigment instantly reflect in both systems. No stale data, no manual imports.
Database ⇄ Accounting and finance
DuckDB to Pigment integration — real-time, two-way sync
Keep DuckDB and Pigment 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 DuckDB and Pigment
Work with Pigment's financial data straight from DuckDB: 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 Users and permissions, Applications, Metrics, Dimension lists from Pigment into Tables, Views, External files (Parquet/CSV/JSON), Attached databases in DuckDB and keeps the two in sync bi-directionally and in real time. Your services read finance records with normal queries against DuckDB, and rows your code writes or updates flow back into Pigment with validation, so the finance system stays the system of record.
Common use cases
- Push CRM pipeline data (deals, stages, amounts) into Pigment for revenue and capacity planning.
- Export approved budgets and forecasts back to a warehouse or Postgres for downstream reporting.
- Sync SaaS data to Parquet on object storage and query it with DuckDB without standing up a warehouse.
- Push aggregates computed in DuckDB out to a CRM or business tools so analysis results reach operational systems.
Internal tools without API plumbing
Build dashboards and back-office tools directly on DuckDB; Stacksync handles the API calls, rate limits, and retries against Pigment.
Write back safely
Updates written to the synced tables in DuckDB propagate into Pigment, so automations can create or correct finance records without custom integration code.
React to financial events
Changes in Pigment appear in DuckDB as row changes, so you can trigger downstream logic with the database tooling you already use.
What you can sync between DuckDB and Pigment
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 | Pigment objects | |
|---|---|---|
| Database files Single-file .duckdb databases that jobs read and write directly on disk or object storage. | Metrics Multidimensional values holding plans and actuals; the main target for inbound data | |
| Schemas Namespaces within a database used to organize tables in sync outputs. | Dimension lists Master data like accounts, products, or employees that metrics are sliced by | |
| Tables Columnar tables created via SQL; the destination for materialized sync data. | Tables Row-based transactional data loaded into models from source systems | |
| Views SQL views used to shape or filter data for downstream consumers. | Scenarios Versions such as budget, forecast, and actuals that give exported figures their context | |
| External files (Parquet/CSV/JSON) Files DuckDB queries in place without loading, common as a sync interchange format. | Data imports Scheduled loads that bring actuals from ERPs, CRMs, and HRIS into the model | |
| Attached databases Additional database files or external systems attached into one session for cross-source queries. | Users and permissions Access controls governing which model areas a sync can touch |
What ships with DuckDB ⇄ Pigment
Connect DuckDB and Pigment for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every DuckDB–Pigment connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever DuckDB or Pigment 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 DuckDB or Pigment record.
Observability
Monitoring
Track your DuckDB ⇄ Pigment sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between DuckDB and Pigment.
How the DuckDB and Pigment connectors work
DuckDB
- Integration surface
- 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)
- Change detection
- Polling or full re-reads; no change feed or transaction log API
- Capabilities
- read · write
- Rate limits
- No API rate limits; throughput is bounded by local compute and I/O
Pigment
- Integration surface
- REST-based import and export API
- Authentication
- API keys, issued separately for import and export
- Change detection
- no change feed; syncs run scheduled imports and exports
- Capabilities
- read · write
- Rate limits
- subject to the platform's API rate limits
How it works
How to connect DuckDB to Pigment — 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 DuckDB and Pigment with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
DuckDB
connected
Pigment
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the DuckDB and Pigment 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 · DuckDB ⇄ PigmentCustomers 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.
DuckDB PigmentCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
DuckDB and Pigment integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between DuckDB and Pigment: authenticate both systems, choose the objects to sync (such as DuckDB's Database files and Schemas), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Common patterns for DuckDB and Pigment: Internal tools without API plumbing; Write back safely; React to financial events. Build dashboards and back-office tools directly on DuckDB; Stacksync handles the API calls, rate limits, and retries against Pigment.
-
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). Pigment: REST-based import and export API. Authentication: API keys, issued separately for import and export. Stacksync manages authentication, retries, and rate limits on both sides.
-
Pigment: Scenario versioning (budget versus forecast versus actuals) is native to the model, so exports need a scenario context to be meaningful. DuckDB: Execution is columnar and vectorized, optimized for analytical scans rather than high-frequency transactional writes. Stacksync's field mapping accounts for these differences between DuckDB and Pigment 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 Pigment records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed DuckDB and Pigment connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom DuckDB–Pigment integration in-house.
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 DuckDB and Pigment.
Popular · 8 of 386
-
DuckDB ⇄ Stripe -
DuckDB ⇄ Rillet -
DuckDB ⇄ Workday -
DuckDB ⇄ Anaplan -
Pigment ⇄ PostgreSQL -
Pigment ⇄ Amazon RDS -
Pigment ⇄ Supabase -
Pigment ⇄ MySQL
No integrations match .
