Stop relying on pg_dump for Supabase Backups

If you are building on Supabase, you probably sleep well knowing they handle database backups (PITR is a lifesaver). But here is the scary part I realized while scaling my SaaS: The database is not your entire project. If you accidentally delete your project or need to migrate to a new environment, pg_dump will not save you from losing: ❌ Storage Objects: Your user avatars, PDF invoices, and uploads in S3 buckets are NOT in the SQL dump. ❌ Auth Configuration: Your SMTP settings, Auth Providers (Google/GitHub login keys), and email templates. ❌ Edge Functions: The serverless logic effectively lives outside the DB. I didn't want to find out about this during a disaster. So I built a tool to fix it. Meet smoonb (Supa Moonbase) It's a CLI wrapper that creates a complete operational snapshot of your Supabase project. It grabs the schema, data, actual files from Storage, Auth policies, and Function configs, bundling them into a single restoreable package. I just launched it on Product Hunt t