{
  "id": 17173655,
  "title": "Supabase Backups and Point-in-Time Recovery: What Each Plan Includes, What It Costs, and a Restore Drill You Can Run on the Free Plan",
  "url": "https://urgent.news/2026/10/30/supabase-backups-and-point-in-time-recovery-what-each-plan-includes",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-10-30T04:18:02.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/tomozilla/supabase-backups-and-point-in-time-recovery-what-each-plan-includes-what-it-costs-and-a-restore-48h7"
  },
  "original_language": "en",
  "account": "Here is a summary of the key points from the source, rewritten in my own words:\n\nSupabase offers three types of backups:\n1. Daily backups are automatically taken for Pro, Team and Enterprise projects, with retention periods of 7, 14 and 30 days respectively. Free projects do not have automatic backups and it's recommended to regularly export backups using the CLI or other methods.\n2. Point-in-time recovery (PITR) is a paid feature that combines daily snapshots with a continuous record of changes. It can recover data up to 2 minutes ago. Pricing starts at about $100 per month for 7 days of retention, increasing to $200 for 14 days and $400 for 28 days. PITR requires at least the Small compute add-on, with Micro being insufficient.\n3. Users can also create their own backup copies. On the Free plan, this is the main method. The restore drill in the article used this method, backing up a test database, accidentally deleting data, and then restoring it.\n\nPITR costs more than the original $100 estimate I previously mentioned. The full pricing is provided by Supabase in the docs.\n\nThe drill involved backing up a database, accidentally deleting data and then restoring it. Comparing the restored data to the original shows how much is lost depending on the frequency of backups.\n\nNote that for the Free plan:\n- Daily backups are not available\n- Passwords for custom database roles are not stored, so would need to be reconfigured after a restore\n- While a restore is running, the project is unavailable\n- Larger databases take longer to restore\n\nIn summary, Supabase provides multiple backup options with varying levels of automation and retention. PITR offers faster recovery but at a higher cost, and requires a specific compute add-on. The Free plan relies on manual backup exports to maintain copies.",
  "summary": "I wanted to know three things about Supabase backups: what I actually have on each plan, what PITR really costs, and whether I can restore. So I read the docs and the dashboard, then ran a restore drill on a Free project and built a small check page. Everything is from my run on 2026-10-27. Prices change, so every number is dated. How this was made: I wrote this with Claude's help: it drafted,…",
  "key_points": [],
  "editors_take": "The tiered backup structure forces users to choose between manual maintenance on free tiers or paying significant premiums for the automation and granular recovery required by professional production environments.",
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}