Move your data from Supabase with your free account

The Supabase PostgreSQL capture connector in Estuary streams inserts, updates, and deletes from your Supabase database using log-based Change Data Capture. Estuary connects to Supabase through the direct PostgreSQL connection endpoint, not the Supabase connection pooler, because the pooler does not support the CDC replication features this connector relies on. Estuary reads change events from PostgreSQL’s write-ahead log through logical replication and keeps downstream systems updated in real time.

• Connect using your Supabase direct PostgreSQL hostname, port, database name, and database user.
• Use a Supabase IPv4 address and direct connection hostname that bypasses the Supabase connection pooler.
• Enable PostgreSQL logical replication by setting wal_level=logical.
• Use a database role with the REPLICATION attribute and the required table-read permissions.
• Configure a replication slot, publication, and watermarks table; Estuary can create some of these automatically when the connector has suitable permissions.
• Capture selected tables from your Supabase PostgreSQL database into Estuary collections.
• Use CDC instead of repeated bulk reloads to capture ongoing inserts, updates, and deletes with lower impact on the source database.
• Backfill existing table contents first, then continue streaming new change events.
• Support schema changes and resilient pipelines with Estuary’s schema evolution and checkpoint-based processing.