Real-time
Two-way sync
Changes in MariaDB or Scaleway Postgres instantly reflect in both systems. No stale data, no manual imports.
Database
MariaDB to Scaleway Postgres integration — real-time, two-way sync
Keep MariaDB 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 MariaDB and Scaleway Postgres
Keep MariaDB and Scaleway Postgres synchronized in real time, across engines, regions, or services, in one or both directions.
Two databases that must agree is one of the oldest problems in engineering: different engines for different workloads, separate services with overlapping reference data, a migration in flight, or regional instances that share a subset of records. Hand-rolled replication across systems means change capture, conflict handling, and type mapping, all built and maintained by your team.
Stacksync syncs tables or collections between MariaDB and Scaleway Postgres continuously and bi-directionally, translating types between the two engines and resolving conflicts by rules you configure. Rows written on either side appear on the other within seconds.
Common use cases
- 01 Keep several MariaDB instances aligned with one system of record across environments
- 02 Two-way sync between a MariaDB application database and a CRM so both systems hold the same customer records
- 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
Regional or environment copies
Mirror selected tables to another region or environment continuously, filtered to just the rows that should travel.
Cross-engine sync
Keep the same dataset live in both MariaDB and Scaleway Postgres, so each workload runs on the engine that suits it.
Migration with zero-downtime cutover
When one database is replacing the other, sync both directions during the transition and switch traffic when ready, without a freeze window.
What you can sync between MariaDB 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.
| MariaDB objects | Scaleway Postgres objects | How this pairing syncs | |
|---|---|---|---|
| Tables The primary sync target; rows map to records in connected 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. | |
| Views Read-side projections used as outbound sync sources. | Views Read-only sources for shaping data before it leaves the database. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Columns Field-level mapping targets with engine-typed values. | Columns Postgres-native types, including JSONB and arrays, are mapped to fields in the paired system. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Primary and Unique Keys Match keys for idempotent upserts. | Schemas Namespace tables so multiple applications or environments can be synced selectively. | Primary and Unique Keys is specific to MariaDB and Schemas to Scaleway Postgres — each maps to any object or custom field on the other side. | |
| System-Versioned Tables Temporal tables that retain row history natively, useful for auditing synced changes. | Sequences Generate primary keys; sync tooling must respect them when writing rows. | System-Versioned Tables is specific to MariaDB and Sequences to Scaleway Postgres — each maps to any object or custom field on the other side. | |
| JSON Columns Semi-structured payloads validated with JSON functions. | Materialized views Precomputed result sets that can be read on a schedule for downstream syncs. | JSON Columns is specific to MariaDB and Materialized views to Scaleway Postgres — each maps to any object or custom field on the other side. |
How changes propagate between MariaDB 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.
MariaDB Scaleway Postgres Sub-second propagation
DetectionChanges in MariaDB are captured at the source via change data capture — no polling loop against its API. Database triggers — Stacksync creates deterministic triggers for internal logging and syncing.
DeliveryEach detected change is applied to Scaleway Postgres as a row-level write, with types converted between the two schemas.
Scaleway Postgres MariaDB 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 applied to MariaDB as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- MariaDB: No API rate limits; throughput is bounded by connection limits and server resources.
- Scaleway Postgres: Throughput is bounded by instance size and connection limits rather than API quotas.
What ships with MariaDB ⇄ Scaleway Postgres
Connect MariaDB and Scaleway Postgres for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every MariaDB–Scaleway Postgres connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever MariaDB 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 MariaDB or Scaleway Postgres record.
Observability
Monitoring
Track your MariaDB ⇄ 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 MariaDB and Scaleway Postgres.
How the MariaDB and Scaleway Postgres connectors work
MariaDB
- Integration surface
- SQL wire protocol (MySQL-compatible client/server protocol)
- Authentication
- Database credentials (connection string or parameters), with optional SSL root certificate upload and optional SSH tunnel (SSH user + host)
- Change detection
- Database triggers — Stacksync creates deterministic triggers for internal logging and syncing
- Capabilities
- read · write · CDC
- Rate limits
- No API rate limits; throughput is bounded by connection limits and server resources
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 MariaDB 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 MariaDB 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.
MariaDB
connected
Scaleway Postgres
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the MariaDB 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 · MariaDB ⇄ 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.
MariaDB Scaleway PostgresCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
MariaDB and Scaleway Postgres integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between MariaDB and Scaleway Postgres: authenticate both systems, choose the objects to sync (such as MariaDB's Tables and Views), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Change detection on MariaDB: Database triggers — Stacksync creates deterministic triggers for internal logging and syncing. On Scaleway Postgres: Log-based CDC via PostgreSQL logical replication where the managed instance permits it; otherwise timestamp or query-based polling. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the MariaDB side: Stored Procedures, Databases (Schemas), Tables, Views, plus custom fields where MariaDB exposes them. On the Scaleway Postgres side: Schemas, Sequences, Columns, Tables. 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 MariaDB and Scaleway Postgres: Regional or environment copies; Cross-engine sync; Migration with zero-downtime cutover. Mirror selected tables to another region or environment continuously, filtered to just the rows that should travel.
-
MariaDB: SQL wire protocol (MySQL-compatible client/server protocol). Authentication: Database credentials (connection string or parameters), with optional SSL root certificate upload and optional SSH tunnel (SSH user + host). Scaleway Postgres: SQL wire protocol (PostgreSQL). Authentication: Database credentials (username/password over TLS). Stacksync manages authentication, retries, and rate limits on both sides.
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
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 382 integrations available for MariaDB and Scaleway Postgres.
Popular · 2 of 382
No integrations match .
