Real-time
Two-way sync
Changes in Pigment or Scaleway Postgres instantly reflect in both systems. No stale data, no manual imports.
Accounting and finance ⇄ Database
Pigment to Scaleway Postgres integration — real-time, two-way sync
Keep Pigment and Scaleway Postgres 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 Pigment and Scaleway Postgres
Work with Pigment's financial data straight from Scaleway Postgres: 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 Data imports, Users and permissions, Applications, Metrics from Pigment into Tables, Views, Materialized views, Schemas in Scaleway Postgres and keeps the two in sync bi-directionally and in real time. Your services read finance records with normal queries against Scaleway Postgres, 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 Push CRM pipeline data (deals, stages, amounts) into Pigment for revenue and capacity planning.
- 02 Export approved budgets and forecasts back to a warehouse or Postgres for downstream reporting.
- 03 Sync production tables from Scaleway Postgres into a CRM so sales and support see live product usage on customer records
- 04 Run a two-way sync between Scaleway Postgres and SaaS tools so edits made in either system converge on the same rows
Common sync patterns
Write back safely
Updates written to the synced tables in Scaleway Postgres propagate into Pigment, so automations can create or correct finance records without custom integration code.
React to financial events
Changes in Pigment appear in Scaleway Postgres 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 Scaleway Postgres as regular tables or collections your team can join, index, and query.
What you can sync between Pigment and Scaleway Postgres
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.
| Pigment objects | Scaleway Postgres objects | How this pairing syncs | |
|---|---|---|---|
| Tables Row-based transactional data loaded into models from source systems | Tables Primary sync unit; each table maps to an object or table on the other side of the sync. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Scenarios Versions such as budget, forecast, and actuals that give exported figures their context | Schemas Namespace tables so multiple applications or environments can be synced selectively. | Scenarios is specific to Pigment and Schemas to Scaleway Postgres — each maps to any object or custom field on the other side. | |
| Data imports Scheduled loads that bring actuals from ERPs, CRMs, and HRIS into the model | Sequences Generate primary keys; sync tooling must respect them when writing rows. | Data imports is specific to Pigment and Sequences to Scaleway Postgres — each maps to any object or custom field on the other side. | |
| Users and permissions Access controls governing which model areas a sync can touch | Columns Postgres-native types, including JSONB and arrays, are mapped to fields in the paired system. | Users and permissions is specific to Pigment and Columns to Scaleway Postgres — each maps to any object or custom field on the other side. | |
| Applications Planning models organized by domain such as finance, sales, or workforce | Views Read-only sources for shaping data before it leaves the database. | Applications is specific to Pigment and Views to Scaleway Postgres — each maps to any object or custom field on the other side. | |
| Metrics Multidimensional values holding plans and actuals; the main target for inbound data | Materialized views Precomputed result sets that can be read on a schedule for downstream syncs. | Metrics is specific to Pigment and Materialized views to Scaleway Postgres — each maps to any object or custom field on the other side. |
How changes propagate between Pigment and Scaleway Postgres
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.
Pigment Scaleway Postgres 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 Scaleway Postgres as a row-level write, with types converted between the two schemas.
Scaleway Postgres Pigment Sub-second propagation
DetectionChanges in Scaleway Postgres are captured at the source via change data capture — no polling loop against its API. Log-based CDC via PostgreSQL logical replication where the managed instance permits it.
DeliveryEach detected change is written to Pigment through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Pigment: Subject to the platform's API rate limits.
- Scaleway Postgres: Throughput is bounded by instance size and connection limits rather than API quotas.
What ships with Pigment ⇄ Scaleway Postgres
Connect Pigment and Scaleway Postgres for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Pigment–Scaleway Postgres connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Pigment or Scaleway Postgres 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 Pigment or Scaleway Postgres record.
Observability
Monitoring
Track your Pigment ⇄ Scaleway Postgres sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Pigment and Scaleway Postgres.
How the Pigment and Scaleway Postgres connectors work
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
Scaleway Postgres
- Integration surface
- SQL wire protocol (PostgreSQL)
- Authentication
- Database credentials (username/password over TLS)
- Change detection
- Log-based CDC via PostgreSQL logical replication where the managed instance permits it; otherwise timestamp or query-based polling
- Capabilities
- read · write · CDC
- Rate limits
- Throughput is bounded by instance size and connection limits rather than API quotas
How it works
How to connect Pigment to Scaleway Postgres — 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 Pigment and Scaleway Postgres with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pigment
connected
Scaleway Postgres
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Pigment and Scaleway Postgres 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 · Pigment ⇄ Scaleway PostgresCustomers 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.
Pigment Scaleway PostgresCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Pigment and Scaleway Postgres integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Pigment and Scaleway Postgres: authenticate both systems, choose the objects to sync (such as Pigment's Tables and Scenarios), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Pigment side: Data imports, Users and permissions, Applications, Metrics, plus custom fields where Pigment exposes them. On the Scaleway Postgres 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 Pigment and Scaleway Postgres: Write back safely; React to financial events; Query finance data like any other data. Updates written to the synced tables in Scaleway Postgres propagate into Pigment, so automations can create or correct finance records without custom integration code.
-
Pigment: REST-based import and export API. Authentication: API keys, issued separately for import and export. Scaleway Postgres: SQL wire protocol (PostgreSQL). Authentication: Database credentials (username/password over TLS). Stacksync manages authentication, retries, and rate limits on both sides.
-
Pigment: Pigment's model is multidimensional: metrics are sliced by dimension lists, so inbound records must map to those dimensions rather than flat columns. Scaleway Postgres: It runs the standard PostgreSQL engine, so ordinary Postgres drivers, ORMs, and SQL tooling work unmodified; managed-service restrictions apply to some server-level features. Stacksync's field mapping accounts for these differences between Pigment and Scaleway Postgres without custom code.
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.
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 348 integrations available for Pigment and Scaleway Postgres.
Popular · 3 of 348
No integrations match .
