Skip to content
Database ⇄ Accounting and finance

Apache Cassandra to Pigment integration — real-time, two-way sync

Keep Apache Cassandra 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 Apache Cassandra and Pigment

Work with Pigment's financial data straight from Apache Cassandra: 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 Scenarios, Data imports, Users and permissions, Applications from Pigment into Secondary Indexes, User-Defined Types, Collections, Counters in Apache Cassandra and keeps the two in sync bi-directionally and in real time. Your services read finance records with normal queries against Apache Cassandra, 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

  • Export approved budgets and forecasts back to a warehouse or Postgres for downstream reporting.
  • Keep dimension lists such as departments and cost centers consistent with master data in the ERP.
  • Feed Cassandra change streams into search indexes or caches that must track the source of truth.
  • Consolidate data from multiple keyspaces or clusters into one reporting store.

Write back safely

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

React to financial events

Changes in Pigment appear in Apache Cassandra 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 Apache Cassandra as regular tables or collections your team can join, index, and query.

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

Apache Cassandra objects Pigment objects
Counters Increment-only counter columns, usually read-only in syncs. Dimension lists Master data like accounts, products, or employees that metrics are sliced by
Keyspaces Top-level namespaces with replication settings that scope a sync connection. Tables Row-based transactional data loaded into models from source systems
Tables Wide-column tables addressed by partition key, the unit of row-level sync. Scenarios Versions such as budget, forecast, and actuals that give exported figures their context
Partitions and Rows Records located by partition and clustering keys during reads and upserts. Data imports Scheduled loads that bring actuals from ERPs, CRMs, and HRIS into the model
Materialized Views Server-maintained denormalized views; considered experimental and disabled by default in recent releases. Users and permissions Access controls governing which model areas a sync can touch
Secondary Indexes Optional indexes that allow filtered reads outside the partition key. Applications Planning models organized by domain such as finance, sales, or workforce
What ships with Apache Cassandra ⇄ Pigment

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Apache Cassandra and Pigment connectors work

Apache Cassandra

Integration surface
CQL over the Cassandra native binary protocol
Authentication
Database credentials (password authenticator); TLS and role-based grants where configured
Change detection
Commit-log based CDC on tables with CDC enabled, or polling using writetime metadata and timestamp columns
Capabilities
read · write · CDC
Rate limits
No API quotas; throughput is governed by cluster capacity and consistency-level choices

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 Apache Cassandra 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 Apache Cassandra 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
    Apache Cassandra connected
    Pigment connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

Apache Cassandra and Pigment integration FAQ

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 Apache Cassandra and Pigment.

Popular · 8 of 386
Coworkers laughing in front of a laptop in a casual office setting

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