If your side project lives on a Supabase Free project, here is the uncomfortable fact: there are no automated backups. None. If you drop the wrong table tonight, there is no restore button waiting for you in the dashboard tomorrow. The fix Supabase sells you is the Pro plan at $25/month — mostly, for a lot of us, just to get daily backups retained for 7 days.
The DIY fix looks trivial: run pg_dump from a GitHub Actions cron job, upload the result somewhere cheap. It is about 30 lines of YAML. But those 30 lines hide five traps, and every one of them fails quietly — you find out your backup doesn't work on the one day you actually need it.
I hit all five while building my own setup. Here they are, in the order you'll meet them.
Trap 1: The connection string Supabase shows you first breaks pg_dump
In the dashboard (Settings → Database → Connection string), the prominent option is the transaction pooler on port 6543 .…