Skip to content
Database ⇄ Accounting and finance

CockroachDB to Pigment integration — real-time, two-way sync

Keep CockroachDB 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 CockroachDB and Pigment

Work with Pigment's financial data straight from CockroachDB: 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 Users and permissions, Applications, Metrics, Dimension lists from Pigment into Sequences, Changefeeds, Databases, Schemas in CockroachDB and keeps the two in sync bi-directionally and in real time. Your services read finance records with normal queries against CockroachDB, 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

  • 01 Sync headcount and compensation data from an HRIS into workforce planning models.
  • 02 Push CRM pipeline data (deals, stages, amounts) into Pigment for revenue and capacity planning.
  • 03 Keep reference data consistent between CockroachDB and regional application databases.
  • 04 Consolidate data from several SaaS tools into one distributed SQL store that survives zone failures.

Common sync patterns

Internal tools without API plumbing

Build dashboards and back-office tools directly on CockroachDB; Stacksync handles the API calls, rate limits, and retries against Pigment.

Write back safely

Updates written to the synced tables in CockroachDB propagate into Pigment, so automations can create or correct finance records without custom integration code.

React to financial events

Changes in Pigment appear in CockroachDB as row changes, so you can trigger downstream logic with the database tooling you already use.

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

CockroachDB objects Pigment objects How this pairing syncs
Tables The core read/write target; rows sync bi-directionally with SaaS objects or other databases. 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.
Views Read-only projections used as curated sync sources. Metrics Multidimensional values holding plans and actuals; the main target for inbound data Views is specific to CockroachDB and Metrics to Pigment — each maps to any object or custom field on the other side.
Indexes Secondary indexes that keep sync lookup queries fast on key columns. Dimension lists Master data like accounts, products, or employees that metrics are sliced by Indexes is specific to CockroachDB and Dimension lists to Pigment — each maps to any object or custom field on the other side.
Sequences ID generators that matter when writes originate from an external system. Scenarios Versions such as budget, forecast, and actuals that give exported figures their context Sequences is specific to CockroachDB and Scenarios to Pigment — each maps to any object or custom field on the other side.
Changefeeds Built-in CDC streams that emit row-level changes to external sinks. Data imports Scheduled loads that bring actuals from ERPs, CRMs, and HRIS into the model Changefeeds is specific to CockroachDB and Data imports to Pigment — each maps to any object or custom field on the other side.
Databases Logical containers a sync connects to, addressed like PostgreSQL databases. Users and permissions Access controls governing which model areas a sync can touch Databases is specific to CockroachDB and Users and permissions to Pigment — each maps to any object or custom field on the other side.

How changes propagate between CockroachDB and Pigment

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.

CockroachDB Pigment Sub-second propagation

DetectionChanges in CockroachDB are captured at the source via change data capture — no polling loop against its API. CDC via changefeeds, which stream row-level changes.

DeliveryEach detected change is written to Pigment through its API, with automatic retries and rate-limit backoff.

Pigment CockroachDB Interval-based propagation

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 CockroachDB as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • CockroachDB: No API rate limits in the SaaS sense; throughput is bounded by cluster capacity.
  • Pigment: Subject to the platform's API rate limits.
What ships with CockroachDB ⇄ Pigment

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the CockroachDB and Pigment connectors work

CockroachDB

Integration surface
SQL wire protocol (PostgreSQL-compatible)
Authentication
Database credentials with TLS; client certificates or SCRAM password auth
Change detection
CDC via changefeeds, which stream row-level changes; polling as a fallback
Capabilities
read · write · CDC
Rate limits
No API rate limits in the SaaS sense; throughput is bounded by cluster 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 CockroachDB 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 CockroachDB 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
    CockroachDB connected
    Pigment connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

CockroachDB and Pigment integration FAQ

SECURITY

Security teams trust 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.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 350 integrations available for CockroachDB and Pigment.

Popular · 6 of 350
All CockroachDB integrations All Pigment integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

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

Book a demo Tour the platform on your own