All posts

Does your app have backups? What Supabase, Neon and Firebase keep

Most app owners assume their database host keeps backups. Some plans do, some don't, and almost none cover everything. The uploaded photos, the invoices in your storage bucket and the mistake you only notice ten days later are usually outside what is kept. Below: what Supabase, Neon and Firebase actually keep on each plan (checked against their documentation in November 2026), what none of them back up, and a 15-minute check you can do today.

Short answer: on free plans you should assume you have little or nothing you can restore. On paid plans you get days, not months, and only of the database itself. If losing your data would hurt, add one copy you control, make sure files are copied too, and do one test restore.

What your database host keeps for you

Supabase

  • Daily backups on paid plans only. Supabase's backup docs: "We automatically back up all Pro, Team, and Enterprise Plan projects on a daily basis." Pro keeps the last 7 days, Team 14, Enterprise up to 30. For free projects the docs recommend that you "regularly export" your data yourself.
  • Point-in-time recovery is a paid add-on on Pro and up: about $100 a month for a 7-day window. With it you can go back to a moment, not just to last night.
  • Files are not included. "Database backups do not include objects you store via the Storage API." Your users' uploads need their own copy.

Neon

  • A restore window, not a set of backups. Neon lets you restore a branch to any moment inside its history window, down to the millisecond, and keeps the old state as a backup branch.
  • The window is short by default. Free: 6 hours. Launch: 1 day by default, up to 7 days. Scale: 1 day by default, up to 30. If you are on a paid plan and never changed the setting, you can go back one day.

Firebase (Firestore)

  • Nothing is on by default. Point-in-time recovery "is disabled by default"; once enabled it keeps 7 days and needs billing turned on.
  • Scheduled backups need the Blaze plan. Scheduled backups can run daily or weekly and be kept up to 14 weeks; you pay for their storage, and they are not available on the free Spark plan.
  • Cloud Storage files are separate. A Firestore backup covers the database, not the images and documents in your storage buckets.

What none of them cover

  • Your files. Profile photos, uploaded documents, generated PDFs. They live in object storage, which has its own rules and usually no automatic backup.
  • Mistakes you find late. A bad import or a bug that slowly overwrites data can go unnoticed for weeks. A 1-day or 7-day window doesn't reach back that far.
  • Losing the account. If the hosting account is closed, unpaid or locked, its backups go with it. A copy in a place you control is the only protection.
  • Things outside the database. Your environment settings, payment provider setup and email templates. Write down where each one lives.

A backup nobody checks is not a backup

A pattern I keep running into: a weekly backup job stops without anyone noticing. It was set up to email its result, but the email goes out from a test or unverified sender address that never reaches an inbox, so nobody can see that the emails have stopped as well. The data is unprotected for months while everyone assumes it is fine.

Two habits prevent this. First, alert on failure, not on success: a message when a backup doesn't run gets noticed, a weekly "all fine" gets filtered. Second, restore a backup now and then. Until you have restored one, you don't know it works.

A simple setup for a small app

  1. Know your window and raise it if needed. On Neon Launch, setting the history window to 7 days costs a little storage and gives you a week instead of a day. On Supabase Pro, the 7 daily backups are already there.
  2. Keep one copy you control. A scheduled database dump (for Postgres, pg_dump; for Firestore, a scheduled export) to storage in a different account, kept for a few weeks. A small scheduled job on GitHub Actions or your host's cron is enough.
  3. Copy your files too. Sync the storage bucket to a second location on the same schedule.
  4. Keep the copy private. A database dump contains your users' personal data. Store it encrypted or in a private bucket, and delete old copies, as your privacy policy promises.
  5. Get told when it fails. One email or chat message when the job fails, sent from an address you know arrives.
  6. Test a restore every few months. Restore into a separate database or branch, open the app against it, check that recent records and files are there.

The 15-minute check

  1. Open your database dashboard. Which plan are you on, and what does it say about backups or the restore window?
  2. Write down how far back you can go today: 0, 6 hours, 1 day, 7 days?
  3. Check where uploaded files live and whether anything copies them.
  4. Find the last backup or dump file. What is its date?
  5. Ask yourself: if the data from last Tuesday were wrong and you noticed today, could you get it back?

If two or more answers are "I don't know", that is your next task, before the next feature.

About to change tables or columns on a live app? Take a fresh backup first, then follow how to change your database without losing data.

Want it set up for you?

I add backups that run, copy files, report failures and have been restored at least once, for apps on Supabase, Neon and Firebase, including ones built with Lovable, Bolt or Cursor. Read the launch-ready checklist for the rest of what I check, or send me the details on the hire page and I'll reply within 24 hours.