Skip to content
Data warehouse ⇄ Accounting and finance

Dremio to Pigment integration — real-time, two-way sync

Keep Dremio 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 Dremio and Pigment

Land the financial records from Pigment in Dremio continuously, and write results back, without building or maintaining a pipeline.

Finance data belongs in the warehouse: revenue, invoices, payments, and customers joined with everything else the business measures. Getting it there usually means an extraction pipeline that breaks quietly and delivers yesterday's numbers.

Stacksync syncs Metrics, Dimension lists, Tables, Scenarios from Pigment into tables in Dremio in real time, and the connection works in both directions: values computed in Dremio can be written back to fields in Pigment 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.

Common use cases

  • Keep dimension lists such as departments and cost centers consistent with master data in the ERP.
  • Sync headcount and compensation data from an HRIS into workforce planning models.
  • Reverse-ETL aggregates computed over lake data out to CRMs and finance tools for business users.
  • Publish operational database tables into Iceberg via Dremio so the lakehouse reflects current application state.

Finance analytics without ETL

Invoices, payments, and customer records from Pigment arrive in Dremio as queryable tables, current within seconds instead of a day behind.

Revenue joined with everything else

Analysts combine Pigment's financial records with product, marketing, or operational data already in Dremio for reporting the finance system cannot do alone.

Write-back of computed fields

Scores or segments computed in Dremio, like payment-risk flags or customer tiers, sync back onto records in Pigment where the finance team can act on them.

What you can sync between Dremio 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.

Dremio objects Pigment objects
Spaces and folders Namespaces that organize virtual datasets and govern access. Dimension lists Master data like accounts, products, or employees that metrics are sliced by
Reflections Materialized accelerations that make repeated extraction queries cheaper. Tables Row-based transactional data loaded into models from source systems
Jobs Query execution records useful for monitoring sync workloads. Scenarios Versions such as budget, forecast, and actuals that give exported figures their context
Sources Connected storage and database systems (S3, ADLS, relational databases) Dremio queries in place. Data imports Scheduled loads that bring actuals from ERPs, CRMs, and HRIS into the model
Physical datasets Tables and files promoted from sources; the raw data a sync ultimately reads. Users and permissions Access controls governing which model areas a sync can touch
Virtual datasets (views) SQL views layering semantics over physical data; the preferred sync target for curated extracts. Applications Planning models organized by domain such as finance, sales, or workforce
What ships with Dremio ⇄ Pigment

Connect Dremio and Pigment for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Dremio–Pigment connection.

Real-time

Two-way sync

Changes in Dremio or Pigment instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Dremio 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 Dremio or Pigment record.

Observability

Monitoring

Track your Dremio ⇄ Pigment sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Dremio and Pigment.

How the Dremio and Pigment connectors work

Dremio

Integration surface
Arrow Flight SQL, JDBC/ODBC, and a REST API
Authentication
Personal access tokens or username/password; OAuth-based SSO on Dremio Cloud
Change detection
Polling via SQL; Iceberg table snapshots can anchor incremental reads; no consumer-facing change feed
Capabilities
read · write
Rate limits
Bounded by engine capacity and workload management rather than API rate limits

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 Dremio 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.

  1. 01

    Connect your apps

    Authenticate Dremio 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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Dremio connected
    Pigment connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Dremio 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Dremio ⇄ Pigment
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Dremio Pigment
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Dremio and Pigment integration FAQ

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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 386 integrations available for Dremio and Pigment.

Popular · 8 of 386
All Dremio integrations All Pigment integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own