Supalive
Supabase pauses free-tier projects after roughly a week without activity. Waking one up is manual, and if you only notice when something breaks, you notice late.
Supalive is a scheduled GitHub Actions workflow that runs in a repository you own. Twice a day it makes one small read against each project you list, which is enough to count as activity. If a ping fails, the run fails, and GitHub emails you — so silence means everything is fine.
When a ping does fail, the report says which kind of failure it is: something you need to fix, like a rotated key or a renamed table, or Supabase not answering, which needs nothing from you. It quotes what Supabase itself said, so a failed run rarely sends you to a dashboard to work out what happened.
The setup tool configures it in your browser and hands back a ready-to-push repository. Your keys are sent to your own Supabase project to verify each one works, and nowhere else. Nothing is stored on any server, because there is no server.
How it works
- 01
A workflow in a repository you own
Supalive is a scheduled GitHub Actions workflow, running from your own repository on GitHub’s runners. There is no server to trust and no account to create, because there is nothing else in the loop.
- 02
One small read, twice a day
At 08:00 and 20:00 it makes a single REST read against each project you listed. That is enough to count as activity, and far too little to trouble your quota.
- 03
Silence means it worked
A failed ping fails the run, and GitHub emails you. The summary opens by saying which kind of failure it is — a rotated key or a renamed table, which is yours to fix, or Supabase not answering, which needs nothing from you.
Screens
Built with · since 2026
- GitHub Actions
- Bash
- Supabase REST
Source
Every repository here is private. If you want to read or use the source of something, get in touch and say which project and what for.
Request code access