Last month I was demoing a client app on a staging project. Mid-demo, I see that my project was paused. Restoring it in front of people was not a great few minutes.
I already knew the inactivity timer watches Postgres activity, not API gateway traffic. The fix is a real database hit on a schedule — something that actually runs a query, not just a network request that bounces off auth or storage.
There are ways to set this up yourself. When you have several projects it got tedious, and the part that really bothered me was finding out late that something had broken for a different reason.
So I built SupAntiPause. It pings each project on a schedule — that's a real Postgres query so it counts toward the activity threshold. You give it the Project URL and the public anon key. It never asks for the service_role key.
If a project was healthy and a ping fails, you get one email listing what went wrong. It also shows ping history, status codes, and latency. You can see all your projects in one monitor.
1 project is free, no card. Paid plans start at $5/year
Stack: TanStack Start, React, Supabase (auth, database, RLS), Paddle for payments, Resend for email alerts, Vercel for hosting.
Honest feedback welcome — what would make this actually useful for your workflow? Thinking about adding Discord/Slack webhook notifications alongside email. Anything else you'd want before adding something like this to your stack?
www.supantipause.com