Backup guides

Pick where your database runs and where you want the backups to live. Each guide covers finding credentials, allow-listing, setting up the bucket, and restoring.

When something already went wrong

What each platform keeps, what is still recoverable, and how to keep a copy next time. Facts are quoted from the providers' own pages, with links.

• Your Supabase project was paused. Here is what that means for your data.

  A paused free Supabase project keeps its data and can be restored for up to a year. How to restore it, copy it out right away, and keep it from pausing again.

• Your free Render Postgres database expired. What can still be saved.

  Free Render Postgres databases expire 30 days after creation and are deleted 14 days later. What is recoverable at each stage, and how to keep a copy that outlives the instance.

• You deleted a Railway volume, or a redeploy lost your Postgres data.

  Railway permanently deletes a volume within 48 hours, and its backups go with it. What to do inside that window, and how to keep a copy outside the project.

• Heroku deleted your app, or your account, and the database went with it.

  Heroku deletes inactive accounts with their unpaid apps and add-ons. What Heroku keeps afterwards, how to download the backups you still have, and how to keep a copy outside Heroku.

• Restore drill checklist

  One page for restoring a backup on purpose, before you need to, with the numbers written down.