How Do I Back Up My App and Data?
You built your app with Claude, ChatGPT, Bolt, or Lovable and it is live. People are using it. Data is accumulating. And at some point a quiet fear appears…
You built your app with Claude, ChatGPT, Bolt, or Lovable and it is live. People are using it. Data is accumulating. And at some point a quiet fear appears: what happens if something goes wrong? What if I accidentally delete data? What if the database gets corrupted? What if the hosting platform has an outage and data is lost? The answer to all of these fears is the same: backups. Here is exactly what to back up, how often, and the simplest ways to do it.
The Two Things You Need to Back Up
Your code. If your code is on GitHub, it is already backed up. GitHub stores every version of every commit you have ever made. Your code is safe. This is one of the best reasons to use GitHub even for small personal projects.
Your data. Your database is the thing that is actually at risk. Code can be rewritten. Data, once lost, is often gone forever. User accounts, form submissions, orders, content, preferences: all of it lives in your database and needs to be backed up regularly.
How to Back Up Your Database
Supabase: has automatic backups built in. On the free tier, you get daily backups retained for seven days. On paid tiers, you get point-in-time recovery. To check your backup settings, go to your Supabase project settings and click Database. You do not need to do anything extra to enable daily backups on the free tier.
Firebase: has automatic daily backups on paid plans. On the free Spark plan, backups are not automatic. To set up manual exports, go to Firestore in your Firebase console and use the Export data feature to save a snapshot to Google Cloud Storage.
Render and Railway: let you create manual database snapshots from their dashboards. On paid tiers, automated daily backups are available. Check your database settings on your hosting platform.
For any database: you can also set up automated export scripts. Ask your AI: “Can you write a script that exports my entire database to a JSON or SQL file and saves it to [Supabase Storage / AWS S3 / Google Drive]? I want to run this daily.”
How Often to Back Up
The right backup frequency depends on how much data you can afford to lose. If your app gets new data every hour, a daily backup means you could lose up to 24 hours of data in a worst-case scenario.
For most early-stage vibe-coded apps, daily backups are sufficient. As your app grows and data becomes more critical, move to hourly or continuous backups using point-in-time recovery.
Test Your Backups
A backup you have never tested is a backup you do not actually have. At least once, practice restoring from a backup to confirm it works before you actually need it.
Ask your AI: “How do I restore my database from a backup on [your platform]?” It will walk you through the process so you know what to do before an emergency.
What to Do if You Accidentally Delete Data
If you have backups, contact your hosting platform’s support immediately. Most platforms with backup systems can restore to a specific point in time. The sooner you act, the easier the recovery.
If you do not have backups, check if your database has a recycle bin or soft delete feature. Some databases keep deleted records for a period before permanently removing them. Supabase Vault and some Firebase configurations retain deleted documents briefly. Check before giving up.
The One Thing to Remember
Back up your code by keeping it on GitHub. Back up your database by enabling automatic backups on your hosting platform and testing that restoration works. Daily backups are sufficient for most early-stage apps. Test your backup restoration before you need it, because the worst time to discover a backup does not work is during an emergency.
Want your app and data running on reliable, managed infrastructure? → Snapdock
New here? These might help: Your app is live. Now what? What nobody tells you after launch. → What is a database? And does my app actually need one? →