Two-way sync
Changes in OCI Database (Oracle Cloud) or Pigment instantly reflect in both systems. No stale data, no manual imports.
Keep OCI Database (Oracle Cloud) 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 Metrics, Dimension lists, Tables, Scenarios from Pigment into Tables, Views, Materialized views, Schemas in OCI Database (Oracle Cloud) and keeps the two in sync bi-directionally and in real time. Your services read finance records with normal queries against OCI Database (Oracle Cloud), 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 OCI Database (Oracle Cloud) as regular tables or collections your team can join, index, and query.
Build dashboards and back-office tools directly on OCI Database (Oracle Cloud); Stacksync handles the API calls, rate limits, and retries against Pigment.
Updates written to the synced tables in OCI Database (Oracle Cloud) 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.
| OCI Database (Oracle Cloud) objects | Pigment objects | How this pairing syncs | |
|---|---|---|---|
| Tables The primary sync surface; rows are read and written directly over SQL | Tables Row-based transactional data loaded into models from source systems | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Sequences Key generators that matter when writing new rows from external systems | Data imports Scheduled loads that bring actuals from ERPs, CRMs, and HRIS into the model | Sequences is specific to OCI Database (Oracle Cloud) and Data imports to Pigment — each maps to any object or custom field on the other side. | |
| PL/SQL procedures and packages Server-side logic that can react to synced data or transform it in place | Users and permissions Access controls governing which model areas a sync can touch | PL/SQL procedures and packages is specific to OCI Database (Oracle Cloud) and Users and permissions to Pigment — each maps to any object or custom field on the other side. | |
| JSON collections Document-style storage in the converged engine, synced alongside relational tables | Applications Planning models organized by domain such as finance, sales, or workforce | JSON collections is specific to OCI Database (Oracle Cloud) and Applications to Pigment — each maps to any object or custom field on the other side. | |
| Partitions Physical table subdivisions relevant when replicating large fact tables | Metrics Multidimensional values holding plans and actuals; the main target for inbound data | Partitions is specific to OCI Database (Oracle Cloud) and Metrics to Pigment — each maps to any object or custom field on the other side. | |
| Views Read-only projections used to expose curated subsets to downstream systems | Dimension lists Master data like accounts, products, or employees that metrics are sliced by | Views is specific to OCI Database (Oracle Cloud) and Dimension lists to Pigment — each maps to any object or custom field on the other side. |
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
DetectionChanges in OCI Database (Oracle Cloud) are captured at the source via change data capture — no polling loop against its API. Log-based CDC from redo logs (LogMiner or GoldenGate), or timestamp polling.
DeliveryEach detected change is written to Pigment through its API, with automatic retries and rate-limit backoff.
DetectionStacksync polls Pigment for changes on an incremental schedule, reading only records changed since the previous pass. No change feed.
DeliveryEach detected change is applied to OCI Database (Oracle Cloud) as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every OCI Database (Oracle Cloud)–Pigment connection.
Changes in OCI Database (Oracle Cloud) or Pigment instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever OCI Database (Oracle Cloud) 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 OCI Database (Oracle Cloud) or Pigment record.
Track your OCI Database (Oracle Cloud) ⇄ Pigment sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between OCI Database (Oracle Cloud) 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 OCI Database (Oracle Cloud) 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 OCI Database (Oracle Cloud) 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 OCI Database (Oracle Cloud) and Pigment: authenticate both systems, choose the objects to sync (such as OCI Database (Oracle Cloud)'s Tables and Sequences), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on OCI Database (Oracle Cloud): Log-based CDC from redo logs (LogMiner or GoldenGate), or timestamp polling. On Pigment: No change feed; syncs run scheduled imports and exports. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Pigment side: Metrics, Dimension lists, Tables, Scenarios, plus custom fields where Pigment exposes them. On the OCI Database (Oracle Cloud) side: Tables, Views, Materialized views, Schemas. Stacksync auto-detects both schemas and converts types between the two systems.
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 OCI Database (Oracle Cloud) 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 OCI Database (Oracle Cloud) as regular tables or collections your team can join, index, and query.
OCI Database (Oracle Cloud): SQL wire protocol (Oracle Net) via JDBC, ODBC, and native drivers; ORDS REST optionally exposes tables over HTTP. Authentication: Database credentials, commonly with mutual TLS using a client wallet on Autonomous Database; OCI IAM integration available. 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.
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 341 integrations available for OCI Database (Oracle Cloud) and Pigment.