Skip to content
Database

MariaDB to Supabase integration — real-time, two-way sync

Keep MariaDB and Supabase 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 Supabase

Keep MariaDB and Supabase 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 Supabase 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 application tables in Supabase with the CRM two-way so new signups appear as contacts and sales edits flow back to the app
  • 04 Mirror billing and subscription records into Supabase tables the application can join directly

Common sync patterns

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.

Shared reference data between services

Services that own separate databases stay consistent on the records they share, without a custom replication layer.

Regional or environment copies

Mirror selected tables to another region or environment continuously, filtered to just the rows that should travel.

What you can sync between MariaDB and Supabase

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 Supabase objects How this pairing syncs
Tables The primary sync target; rows map to records in connected systems. Tables Standard Postgres tables; the primary two-way sync target. 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-side projections exposed to outbound syncs. 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. auth.users Managed authentication users, often mirrored into CRM or support systems. Primary and Unique Keys is specific to MariaDB and auth.users to Supabase — 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. Row Level Security Policies Row-level access rules that govern what the REST layer exposes. System-Versioned Tables is specific to MariaDB and Row Level Security Policies to Supabase — each maps to any object or custom field on the other side.
JSON Columns Semi-structured payloads validated with JSON functions. JSONB Columns Semi-structured payloads such as event properties or nested objects. JSON Columns is specific to MariaDB and JSONB Columns to Supabase — each maps to any object or custom field on the other side.
Stored Procedures Server-side logic that can post-process synced rows. Database Functions Postgres functions that can transform or validate synced rows. Stored Procedures is specific to MariaDB and Database Functions to Supabase — each maps to any object or custom field on the other side.

How changes propagate between MariaDB and Supabase

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

Supabase MariaDB Sub-second propagation

DetectionSupabase pushes changes as they happen — webhook events backed by change data capture. Log-based CDC via Postgres logical replication, the same WAL feed that powers Supabase Realtime.

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.
  • Supabase: SQL access is bounded by connection limits (pooled connections are provided); the REST layer is subject to the platform's limits.
What ships with MariaDB ⇄ Supabase

Connect MariaDB and Supabase for flexible, real-time data sync.

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

Real-time

Two-way sync

Changes in MariaDB or Supabase instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever MariaDB or Supabase 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 Supabase record.

Observability

Monitoring

Track your MariaDB ⇄ Supabase 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 Supabase.

How the MariaDB and Supabase 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
MariaDB setup guide

Supabase

Integration surface
Direct PostgreSQL wire protocol connection, plus an auto-generated REST API (PostgREST)
Authentication
Database credentials (connection string) for SQL access; API keys (anon / service role) for the REST layer
Change detection
Log-based CDC via Postgres logical replication, the same WAL feed that powers Supabase Realtime; database webhooks can also fire on row changes
Capabilities
read · write · CDC · webhooks
Rate limits
SQL access is bounded by connection limits (pooled connections are provided); the REST layer is subject to the platform's limits
How it works

How to connect MariaDB to Supabase — 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 MariaDB and Supabase 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
    MariaDB connected
    Supabase connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

MariaDB and Supabase 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
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:

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 390 integrations available for MariaDB and Supabase.

Popular · 8 of 390
All MariaDB integrations All Supabase 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