Real-time
Two-way sync
Changes in Pigment or Starburst Enterprise instantly reflect in both systems. No stale data, no manual imports.
Accounting and finance ⇄ Data warehouse
Pigment to Starburst Enterprise integration — real-time, two-way sync
Keep Pigment and Starburst Enterprise 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 Pigment and Starburst Enterprise
Land the financial records from Pigment in Starburst Enterprise 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 Data imports, Users and permissions, Applications, Metrics from Pigment into tables in Starburst Enterprise in real time, and the connection works in both directions: values computed in Starburst Enterprise 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.
- Write curated or reconciled results back to lakehouse tables through connectors that support inserts
- Read federated views that join warehouse, lake, and database tables, then sync the result into operational tools like a CRM
Queryable history for audit and reconciliation
A continuously synced copy in Starburst Enterprise 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 Starburst Enterprise 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 Starburst Enterprise for reporting the finance system cannot do alone.
What you can sync between Pigment and Starburst Enterprise
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.
| Pigment objects | Starburst Enterprise objects | |
|---|---|---|
| Users and permissions Access controls governing which model areas a sync can touch | Views Engine-level SQL views used to shape federated data before syncing it out. | |
| Applications Planning models organized by domain such as finance, sales, or workforce | Materialized views Precomputed results that make repeated sync reads cheaper. | |
| Metrics Multidimensional values holding plans and actuals; the main target for inbound data | Columns Typed per the Trino type system, mapped from each source's native types. | |
| Dimension lists Master data like accounts, products, or employees that metrics are sliced by | Catalogs Each catalog maps to a connector (Iceberg, Hive, PostgreSQL, and others) exposing an external source. | |
| Tables Row-based transactional data loaded into models from source systems | Schemas Namespaces within a catalog, mirroring the underlying source's databases or schemas. | |
| Scenarios Versions such as budget, forecast, and actuals that give exported figures their context | Tables Queryable relations; writes pass through to sources whose connectors support them. |
What ships with Pigment ⇄ Starburst Enterprise
Connect Pigment and Starburst Enterprise for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Pigment–Starburst Enterprise connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Pigment or Starburst Enterprise 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 Pigment or Starburst Enterprise record.
Observability
Monitoring
Track your Pigment ⇄ Starburst Enterprise sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Pigment and Starburst Enterprise.
How the Pigment and Starburst Enterprise connectors work
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
Starburst Enterprise
- Integration surface
- ANSI SQL over JDBC/ODBC drivers and the Trino client REST protocol
- Authentication
- Deployment-dependent: username/password, LDAP, OAuth 2.0, or Kerberos
- Change detection
- Query-based polling; Starburst is a query engine and exposes no change log of its own
- Capabilities
- read · write
- Rate limits
- Throughput is governed by cluster sizing and resource groups rather than API quotas
How it works
How to connect Pigment to Starburst Enterprise — 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 Pigment and Starburst Enterprise with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pigment
connected
Starburst Enterprise
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Pigment and Starburst Enterprise 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 · Pigment ⇄ Starburst EnterpriseCustomers 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.
Pigment Starburst EnterpriseCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Pigment and Starburst Enterprise integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Pigment and Starburst Enterprise: authenticate both systems, choose the objects to sync (such as Pigment's Users and permissions and Applications), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Pigment: Scenario versioning (budget versus forecast versus actuals) is native to the model, so exports need a scenario context to be meaningful. Starburst Enterprise: The engine stores no data itself; reads and writes pass through to the underlying sources, and write support depends on each connector. Stacksync's field mapping accounts for these differences between Pigment and Starburst Enterprise 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 Pigment and Starburst Enterprise records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Pigment and Starburst Enterprise connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Pigment–Starburst Enterprise integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Pigment and Starburst Enterprise. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Pigment: No change feed; syncs run scheduled imports and exports. On Starburst Enterprise: Query-based polling; Starburst is a query engine and exposes no change log of its own. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
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 Pigment and Starburst Enterprise.
Popular · 8 of 386
-
Pigment ⇄ Apache Kylin -
Pigment ⇄ Apache Pinot -
Pigment ⇄ Azure Synapse Analytics -
Pigment ⇄ ClickHouse -
Starburst Enterprise ⇄ Stripe -
Starburst Enterprise ⇄ Rillet -
Starburst Enterprise ⇄ Workday -
Starburst Enterprise ⇄ Anaplan
No integrations match .
