Two-way sync
Changes in OpenSearch or Pigment instantly reflect in both systems. No stale data, no manual imports.
Keep OpenSearch 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.
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 Dimension lists, Tables, Scenarios, Data imports from Pigment into Index templates, Ingest pipelines, Data streams, Snapshots in OpenSearch and keeps the two in sync bi-directionally and in real time. Your services read finance records with normal queries against OpenSearch, and rows your code writes or updates flow back into Pigment with validation, so the finance system stays the system of record.
Customers, invoices, and payments from Pigment live in OpenSearch as regular tables or collections your team can join, index, and query.
Build dashboards and back-office tools directly on OpenSearch; Stacksync handles the API calls, rate limits, and retries against Pigment.
Updates written to the synced tables in OpenSearch propagate into Pigment, so automations can create or correct finance records without custom integration code.
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.
| OpenSearch objects | Pigment objects | |
|---|---|---|
| Ingest pipelines Server-side processors that transform documents as they are written | Dimension lists Master data like accounts, products, or employees that metrics are sliced by | |
| Data streams Append-oriented time-series storage for logs and events pushed from source systems | Tables Row-based transactional data loaded into models from source systems | |
| Snapshots Backup artifacts, relevant when reseeding an index from a repository | Scenarios Versions such as budget, forecast, and actuals that give exported figures their context | |
| Indexes The core container; synced records land in indexes with defined mappings | Data imports Scheduled loads that bring actuals from ERPs, CRMs, and HRIS into the model | |
| Documents JSON records written via the index and bulk APIs and read via search queries | Users and permissions Access controls governing which model areas a sync can touch | |
| Index aliases Stable names over rotating indexes, used for zero-downtime reindex during backfills | Applications Planning models organized by domain such as finance, sales, or workforce |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every OpenSearch–Pigment connection.
Changes in OpenSearch or Pigment instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever OpenSearch or Pigment data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single OpenSearch or Pigment record.
Track your OpenSearch ⇄ Pigment sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between OpenSearch and Pigment.
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 OpenSearch 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.
Pick the OpenSearch 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.
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 OpenSearch and Pigment: authenticate both systems, choose the objects to sync (such as OpenSearch's Ingest pipelines and Data streams), 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 OpenSearch and Pigment: Query finance data like any other data; Internal tools without API plumbing; Write back safely. Customers, invoices, and payments from Pigment live in OpenSearch as regular tables or collections your team can join, index, and query.
OpenSearch: REST API over HTTP(S) with JSON payloads. Authentication: Basic authentication with the security plugin, or AWS IAM request signing on Amazon OpenSearch 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. OpenSearch: Amazon OpenSearch Service domains typically authenticate with IAM request signing, while self-managed clusters use the security plugin's basic auth or certificates. Stacksync's field mapping accounts for these differences between OpenSearch 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 OpenSearch and Pigment 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 OpenSearch and Pigment.