Log based change capture
Logical replication reads the write ahead log, so only committed changes move after the first load.
Neon
Polytomic connects Neon to your data warehouse, databases, and SaaS tools for database ETL and reverse ETL. Replicate branches into Snowflake or BigQuery using Postgres logical replication, and write modelled data back into Neon, without writing code.
Branch aware by design
Each branch is its own endpoint and its own sync, so environments stay separate rather than blurring together.
Survives a compute suspend
The replication slot holds the position, so a serverless pause interrupts the reader without losing its place.
Example workflows
Replicate Neon into Snowflake, BigQuery, or Databricks
What you can sync
Move data between Neon and your data warehouse, databases, and SaaS tools, in both directions.
From Neon
Tables and views across schemas
Change data capture through logical replication
Custom SQL as a model source
Any branch, connected by its own endpoint
To Neon
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
Neon is Postgres, so Polytomic reads and writes it the way it does any Postgres database, including logical replication for change data capture. The connection defaults to the neondb database with SSL enabled.
Branching is what makes Neon different in practice. A connection points at one branch's endpoint, and that branch carries its own publication and replication slot, so syncing production and a development branch means two separate setups rather than one that follows you around.
- Connect Neon with the direct endpoint for the branch you want
- Read tables and views, or write custom SQL as a model source
- Enable logical replication for log based change capture
- Treat each branch as its own source with its own slot
- 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 branch endpoint, database, and credentials. The database defaults to neondb and SSL is on. For change data capture you also need logical replication enabled on the project, a publication, and replication permission on the role Polytomic uses.
How to get connected
- 1In Neon, choose the branch you want to sync and copy its direct endpoint
- 2Confirm the hostname is the direct one rather than the pooled one
- 3Create a role for Polytomic with the permissions it needs
- 4For change data capture, enable logical replication and create a publication
- 5In Polytomic, navigate to Connections, then Add Connection, then Neon
- 6Enter the endpoint and credentials, test, then select tables 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 Neon in minutes
No credit card required. Free trial available.