Connect Supabase

This guide: connect a Supabase Postgres database so walwarden can run scheduled logical backups into a destination you own. Supabase is a shipping provider.

Prerequisites

• A configured, preflight-verified destination — see BYO AWS S3 or the destinations overview.
• A Supabase project with a Postgres database.
• A database role with SELECT on the tables you want to back up. Superuser is not required.

Step 1: Get the connection string

In the Supabase dashboard, open Project Settings → Database and copy the connection string (the direct connection URI, not a pooled pgbouncer URI — pg_dump needs a direct session). It looks like:

postgresql://postgres:<password>@db.<project-ref>.supabase.co:5432/postgres

Step 2: Add the protected database

1. In the walwarden dashboard, click Protected databases → Add database.
2. Enter:
   • Name — a label for your reference (for example, supabase-prod)
   • DSN — the connection string from step 1, including the password. It is stored encrypted and never returned to the browser.
   • Destination — select your verified destination.
3. Click Save. Walwarden validates that it can reach the database and that the role has the permissions pg_dump needs.

Step 3: Set a schedule

On the database detail page, set a cron schedule (see Scheduled backups). The first backup runs at the next tick; you can also trigger one ad-hoc.

Verify it worked

The Backup history table shows a completed row with a signed manifest hash, and the dashboard shows an RPO figure for this database. That confirms the backup ran and landed in your bucket. To prove recoverability, run a restore drill.