Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.tryardent.com/llms.txt

Use this file to discover all available pages before exploring further.

Want Claude to handle this? Paste this into Claude Code or Cursor: 
Check if my Supabase database is ready to connect to Ardent.
My connection string: [paste here]

Verify:
1. The host is reachable and credentials work
2. Logical replication is enabled (it should be on by default)
3. The user has replication privileges
4. IPv4 is enabled (check pg_hba.conf or attempt a direct connection)

Tell me exactly what to fix if anything fails, then run:
ardent connector create postgresql '<connection-string>'
1

Open the Connect dialog

In your Supabase project dashboard, click Connect in the top right corner.Select the Direct tab, then choose Direct connection as the connection method and set Type to URI.
2

Check IPv4

Scroll down in the Connect dialog. You’ll see an IPv4 compatible indicator.If it shows a checkmark, you’re good. If not, click IPv4 settings and enable the dedicated IPv4 add-on ($4/month). Ardent needs a direct connection to your database, which requires IPv4.
3

Copy your connection string

Still in the Connect dialog, copy the URI. It looks like:
postgresql://postgres:[YOUR-PASSWORD]@db.[PROJECT-REF].supabase.co:5432/postgres
4

Connect your database

ardent connector create postgresql 'postgresql://postgres:[YOUR-PASSWORD]@db.[PROJECT-REF].supabase.co:5432/postgres'
Wrap the URI in single quotes in your shell so characters in the password are not interpreted.Ardent will verify your setup and begin replicating your database. This may take a few minutes depending on data size.
Logical replication is enabled by default on Supabase — no extra setup needed.
5

Create your first branch

ardent branch create my-feature
Done. You now have an isolated copy of your Supabase database — schema, data, and all. The CLI returns a connection URL you can use anywhere.