Skip to content
Data warehouse ⇄ Accounting and finance

Apache Druid to Pigment integration — real-time, two-way sync

Keep Apache Druid 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 Apache Druid and Pigment

Land the financial records from Pigment in Apache Druid 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 Applications, Metrics, Dimension lists, Tables from Pigment into tables in Apache Druid in real time, and the connection works in both directions: values computed in Apache Druid 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

  • Export approved budgets and forecasts back to a warehouse or Postgres for downstream reporting.
  • Keep dimension lists such as departments and cost centers consistent with master data in the ERP.
  • Feed operational records into Druid via batch ingestion so analysts get interactive slice-and-dice on fresh data.
  • Sync Druid query results into a warehouse to combine real-time aggregates with historical models.

Write-back of computed fields

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

Queryable history for audit and reconciliation

A continuously synced copy in Apache Druid gives you a durable, queryable record of financial data for month-end and audit questions.

Finance analytics without ETL

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

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

Apache Druid objects Pigment objects
Dimensions String and categorical columns used for filtering and grouping in synced queries. Scenarios Versions such as budget, forecast, and actuals that give exported figures their context
Metrics Numeric columns, often pre-aggregated at ingestion via rollup. Data imports Scheduled loads that bring actuals from ERPs, CRMs, and HRIS into the model
Ingestion Supervisors Long-running specs that pull from streams like Kafka; the write path into Druid. Users and permissions Access controls governing which model areas a sync can touch
Lookups Key-value mappings joined at query time, refreshable from external systems. Applications Planning models organized by domain such as finance, sales, or workforce
Tasks Batch ingestion and compaction jobs monitored during data loads. Metrics Multidimensional values holding plans and actuals; the main target for inbound data
Datasources The table-like unit of storage and querying, the main target of reads and ingestion. Dimension lists Master data like accounts, products, or employees that metrics are sliced by
What ships with Apache Druid ⇄ Pigment

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Apache Druid and Pigment connectors work

Apache Druid

Integration surface
REST API (SQL over HTTP and native JSON queries); JDBC via Avatica
Authentication
Deployment-dependent: basic authentication or an authenticator extension; often fronted by a proxy
Change detection
Not applicable for reads out (polling by time interval); data enters Druid through streaming or batch ingestion rather than row updates
Capabilities
read · write
Rate limits
No fixed API quotas; query concurrency is bounded by broker and historical node capacity

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 Apache Druid 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 Apache Druid 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
    Apache Druid connected
    Pigment connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Apache Druid 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 · Apache Druid ⇄ 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
    Apache Druid Pigment
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Apache Druid 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.

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 Apache Druid and Pigment.

Popular · 8 of 386
Coworkers laughing in front of a laptop in a casual office setting

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