Log based change capture
Logical replication reads the write ahead log, so only committed changes move after the first load.
Supabase
Polytomic connects Supabase to your data warehouse, databases, and SaaS tools for database ETL and reverse ETL. Replicate tables into Snowflake or BigQuery using Postgres logical replication, and write modelled data back into Supabase, without writing code.
Endpoint checked for you
Pooler hostnames are rejected when replication is enabled, so a sync cannot be misconfigured to fail later.
Full Postgres behaviour
Type handling, schema evolution, and write modes work as they do on any Postgres database.
Example workflows
Replicate Supabase tables into Snowflake, BigQuery, or Databricks
What you can sync
Move data between Supabase and your data warehouse, databases, and SaaS tools, in both directions.
From Supabase
Tables and views across schemas
Change data capture through logical replication
Custom SQL as a model source
JSON and JSONB columns
To Supabase
Tables, created and migrated automatically
Create, update, create or update, and replace
Merges keyed on the source primary key
Soft deletes by default, hard deletes optional
How it works
Supabase is Postgres, so Polytomic reads and writes it the way it does any Postgres database. Tables and views can be replicated into your data warehouse, and modelled data can be written back into the database your application serves from.
The one Supabase specific detail is the endpoint. Change data capture depends on a long lived replication connection, which the connection pooler cannot serve, so Polytomic checks for a pooler hostname and rejects it when replication is enabled rather than letting the sync fail later.
- Connect Supabase with host, port, database, and credentials
- Use the direct endpoint on port 5432 for change data capture
- Read tables and views, or write custom SQL as a model source
- Enable logical replication for log based change capture
- Write back with create, update, create or update, and replace
- Monitor sync health, record volume, and failures from one interface
How to set up
Supply the host, port, database, and credentials from your Supabase project. The database defaults to postgres and SSL is on. For change data capture you also need logical replication available, a publication, and replication permission on the role Polytomic uses.
How to get connected
- 1In Supabase, find your project's direct connection details
- 2Create a role for Polytomic with the permissions it needs
- 3For change data capture, enable logical replication and create a publication
- 4In Polytomic, navigate to Connections, then Add Connection, then Supabase
- 5Enter the direct host on port 5432, database, and credentials
- 6Test the connection, select tables, set a schedule, and click Save
Frequently asked questions
Why teams choose Polytomic
No engineering required
Set up and manage syncs without writing code.
Flexible data modeling
Use SQL to define exactly what data gets synced.
Handles scale automatically
Supports large datasets with incremental syncs and bulk APIs.
Start syncing your data with Supabase in minutes
No credit card required. Free trial available.