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. 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.
  • 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

ReviveDB creates a unique read-only Postgres login through the Supabase Management API, checks every discovered table including Auth, and runs a schema-only dump. The login has a six-hour expiry and is removed after the job. 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. ReviveDB assigns a stable minute inside your chosen hour so every customer does not start at once.

4. Wait for verification

ReviveDB captures the supported project components and stores them off-platform. It restores the database into an isolated verification environment, hash-checks Storage and Function artifacts, and reports unsupported or manual components separately. The database becomes verified only after the restored result matches the capture-time inventory.