Simple, honest pricing
Start free. Upgrade when you need more.
Business
You sign in, connect Google Drive, and add the Supabase database URI for the job you want backed up.
Your entire database goes straight from your Supabase project to your Google Drive. It's never downloaded to our servers first.
Backup files are uploaded to the Google Drive account you connect. The backup runner writes them under a supabackups folder path for the backup job.
Supabackup only gets access to files it creates in your Google Drive. It cannot read, edit, or delete your other Drive files. You can verify this yourself - Google shows this exact permission on the consent screen when you connect Drive.
Yes. The Free plan supports one weekly backup job. Pro adds more jobs, daily scheduling, auto-delete options, and priority support.
On Pro, you can keep the latest 7, 14, or 30 backups. You can also keep everything by choosing no auto-delete.
The job is paused so it isn't retried blindly, and the dashboard shows the error so you know what to fix. Pro users also get an email alert when a job fails.
Yes, a backup reads your whole database out of Supabase, which counts as egress on your own Supabase project. Usually a non-issue unless your database is large and backed up often.