Browse documentation

Start here

Back up your first Supabase project

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

Updated 17 July 2026

Follow these steps to connect a Supabase project and create its first verified recovery point. ReviveDB manages the storage and schedule.

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.
  • The database password may be required for complete database and Auth coverage. ReviveDB asks only when Supabase cannot provide suitable temporary database access.

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.
Choose Connect Supabase to authorize an account and select a project.

2. Complete database access

ReviveDB checks the project and uses the narrowest available connection method. On projects where Supabase cannot provide complete temporary access, paste the project database password when prompted. It is encrypted at rest and is never returned through the API.

3. Choose region and backup policy

Choose the storage region for new recovery points, the retention maximum, a preferred backup hour and the project timezone. ReviveDB assigns a stable minute inside your chosen hour so every customer does not start at once.

Policy is configured per project. Existing recovery points stay in the region where they were created.

4. Wait for verification

ReviveDB captures the project, stores it off-platform and restores the database into an isolated verification environment. The run becomes verified only after the restored result matches the capture-time inventory.

Expand a backup run to see component coverage and the facts checked during verification.