Skip to content
ReviveDB
Browse documentation

Back up your first Supabase project

Connect Supabase, choose a project and create your first verified recovery point.

Follow these steps to connect a Supabase project and create its first verified recovery point. The storage and the schedule are handled for you.

Before you start

  • A Supabase account with access to the project you want to protect.
  • A running Supabase project. Paused projects cannot be backed up.
  • For supported projects, Supabase OAuth is enough to set up complete database and Auth coverage without storing the production database password.

1. Connect Supabase

  1. Open the ReviveDB dashboard and choose Connect Supabase.
  2. Approve the requested Supabase OAuth access.
  3. Choose the project you want to protect.

2. Verify database access

A unique read-only Postgres login is created through the Supabase Management API, every discovered table including Auth is checked, and a schema-only dump runs. The login expires after one hour and is removed when the job ends. Your project database password is not read, reset or rotated.

3. Choose region and backup policy

Choose the retention maximum (3 rolling recovery points on Free; up to 30 days on Pro or 60 days on Scale), a preferred backup hour and the project timezone. Recovery points are stored in the EU on Cloudflare R2. Each project gets a stable minute inside your chosen hour, so not every project starts at once.

4. Wait for verification

The supported project components are captured and stored off-platform. The database is restored into an isolated verification environment, Storage and Function artifacts are hash-checked, and unsupported or manual components are reported separately. The database becomes verified only after the restored result matches the capture-time inventory.