Supabase - Ardent

Ardent works with Supabase Postgres. This page covers only what’s specific to Supabase — the full walkthrough is the Quickstart.

Using Claude Code or Cursor? It can do the checks for you

With the ardent-cli skill installed, a short ask is enough — the skill fetches this page and runs the checks:

Check if my Supabase database is ready to connect to Ardent.
My connection string: [paste here]

Without the skill, paste the full directions:

Check if my Supabase database is ready to connect to Ardent.
My connection string: [paste here]

Use Ardent preflight first:
ardent connector preflight postgresql '<connection-string>' --schemas public

Verify:
1. This is the Direct connection string, not the pooler string.
2. IPv4 is enabled for the Supabase project.
3. The URL points to the writable primary: SELECT pg_is_in_recovery(); must return false.
4. Logical replication and wal2json are available.
5. The Ardent preflight Grant script has been run for the schemas I want to replicate.
6. Tables selected for replication have a primary key, valid unique NOT NULL index, or REPLICA IDENTITY FULL.

After preflight passes, run:
ardent connector create postgresql '<connection-string>'

Three things matter here:

Use the direct connection, not the pooler

In your Supabase dashboard:

Click Connect in the top right.
Select the Direct tab.
Choose Direct connection.
Set Type to URI.

The pooler connection string — host ending in pooler.supabase.com, usually port 6543 — will not work. Ardent replicates your data over a direct, long-lived Postgres connection; poolers only forward regular queries and can’t carry replication.

Check IPv4

Scroll down in the Connect dialog to the IPv4 compatible indicator.

Checkmark — you’re good.
No checkmark — click IPv4 settings and enable the dedicated IPv4 add-on. Ardent needs a direct IPv4 route to your database.

Copy the connection string

It looks like:

postgresql://postgres:[YOUR-PASSWORD]@db.[PROJECT-REF].supabase.co:5432/postgres

Wrap it in single quotes when you use it in a shell.

From here, continue with the Quickstart: run preflight, run the grant script if preflight prints one, then create the connector. One Supabase-specific preflight failure to know: if preflight says the source is a read replica, you’ve copied a replica URL. Use the writable primary instead — branching needs a source that supports logical replication.

Running Supabase locally too? Ardent can point your local Supabase services at a branch — see Local Supabase linking.

Regression testing AWS RDS