Real-time
Two-way sync
Changes in Couchbase or Pigment instantly reflect in both systems. No stale data, no manual imports.
Database ⇄ Accounting and finance
Couchbase to Pigment integration — real-time, two-way sync
Keep Couchbase 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 Couchbase and Pigment
Work with Pigment's financial data straight from Couchbase: read it with ordinary queries, write to it from your own code, and let Stacksync keep both sides consistent.
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 XDCR replications, Full-text search indexes, Buckets, Scopes in Couchbase and keeps the two in sync bi-directionally and in real time. Your services read finance records with normal queries against Couchbase, and rows your code writes or updates flow back into Pigment with validation, so the finance system stays the system of record.
Common use cases
- Push CRM pipeline data (deals, stages, amounts) into Pigment for revenue and capacity planning.
- Export approved budgets and forecasts back to a warehouse or Postgres for downstream reporting.
- Stream document mutations via DCP into downstream systems so caches, search indexes, or warehouses stay current.
- Two-way sync between Couchbase (serving application data) and a CRM so support and sales teams see live application state.
React to financial events
Changes in Pigment appear in Couchbase as row changes, so you can trigger downstream logic with the database tooling you already use.
Query finance data like any other data
Customers, invoices, and payments from Pigment live in Couchbase as regular tables or collections your team can join, index, and query.
Internal tools without API plumbing
Build dashboards and back-office tools directly on Couchbase; Stacksync handles the API calls, rate limits, and retries against Pigment.
What you can sync between Couchbase 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.
| Couchbase objects | Pigment objects | |
|---|---|---|
| Full-text search indexes Search indexes over documents, relevant when syncing searchable content. | Users and permissions Access controls governing which model areas a sync can touch | |
| Buckets Top-level data containers, roughly analogous to a database, that scope replication and memory quotas. | Applications Planning models organized by domain such as finance, sales, or workforce | |
| Scopes Namespaces inside a bucket used to group collections, similar to schemas. | Metrics Multidimensional values holding plans and actuals; the main target for inbound data | |
| Collections Table-like groupings of documents that syncs typically map one-to-one to destination tables. | Dimension lists Master data like accounts, products, or employees that metrics are sliced by | |
| JSON Documents The core records; schemaless JSON keyed by document id, flattened or mapped to relational rows in syncs. | Tables Row-based transactional data loaded into models from source systems | |
| Global Secondary Indexes Indexes that make SQL++ query-based extraction efficient. | Scenarios Versions such as budget, forecast, and actuals that give exported figures their context |
What ships with Couchbase ⇄ Pigment
Connect Couchbase and Pigment for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Couchbase–Pigment connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Couchbase 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 Couchbase or Pigment record.
Observability
Monitoring
Track your Couchbase ⇄ Pigment sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Couchbase and Pigment.
How the Couchbase and Pigment connectors work
Couchbase
- Integration surface
- SQL++ (N1QL) query service, key-value SDK APIs, and REST management APIs
- Authentication
- Database credentials with role-based access control, typically over TLS
- Change detection
- Database Change Protocol (DCP) streams document mutations; SQL++ polling on document fields as an alternative
- Capabilities
- read · write · CDC
- Rate limits
- Throughput is bounded by cluster sizing 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 Couchbase 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.
- 01
Connect your apps
Authenticate Couchbase 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.
Couchbase
connected
Pigment
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Couchbase 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.
objects · Couchbase ⇄ PigmentCustomers 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.
Couchbase PigmentCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Couchbase and Pigment integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Couchbase and Pigment: authenticate both systems, choose the objects to sync (such as Couchbase's Full-text search indexes and Buckets), 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 Couchbase and Pigment: React to financial events; Query finance data like any other data; Internal tools without API plumbing. Changes in Pigment appear in Couchbase as row changes, so you can trigger downstream logic with the database tooling you already use.
-
Couchbase: SQL++ (N1QL) query service, key-value SDK APIs, and REST management APIs. Authentication: Database credentials with role-based access control, typically over TLS. 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. Couchbase: SQL++ (N1QL) provides SQL-style querying over JSON documents, including joins across collections, so extraction can be query-shaped rather than key-by-key. Stacksync's field mapping accounts for these differences between Couchbase 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 Couchbase and Pigment records are not retained after a sync operation.
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 Couchbase and Pigment.
Popular · 8 of 386
-
Couchbase ⇄ Workday -
Couchbase ⇄ Anaplan -
Couchbase ⇄ Chargebee -
Couchbase ⇄ Hyperline -
Pigment ⇄ Neo4j -
Pigment ⇄ OCI Database (Oracle Cloud) -
Pigment ⇄ OpenSearch -
Pigment ⇄ Oracle DB
No integrations match .
