Hey everyone 👋

A couple months ago, I started a side project using Supabase — nothing huge, just experimenting. I left it idle for a bit (life happens), and when I came back, it had been paused due to inactivity. After 90 days, there’s no restoring from the dashboard. You have to download a backup and start again.

That’s when I built KeepMySupabaseAlive.

💡 What It Does

KeepMySupabaseAlive is a simple service that keeps your Supabase project alive by pinging it on a set schedule.

🛠 Key features:

  • Add your Supabase Public URL and Anon key
  • Set a custom ping frequency
  • Monitor your connection with a clean dashboard (ping logs, success rate, status)
  • Manually test your connection anytime

You can check it out here: keepmysupabasealive.com

🚀 producthunt: https://www.producthunt.com/products/keepmysupabasealive

⚙️ The Stack

  • Next.js 15 – App router, server components
  • Tailwind CSS – UI styling
  • ShadCN UI – For fast, consistent components
  • Supabase – Auth and DB (of course)
  • Vercel – Hosting the app
  • Cron jobs – Managed through

🚧 What I Learned

  • Supabase has great docs, but you have to read the fine print on project inactivity.
  • Next.js 15's App Router feels really natural once you lean into server components.
  • UX really matters — especially for dev tools. The ping success chart was a small detail but ended up being super helpful for users.

🧠 What’s Next

Here’s what I’m planning next for KeepMySupabaseAlive:

  • 💾 Automatic Supabase backups — schedule exports of your data as a safety net
  • 📈 Advanced monitoring — more insights into downtime, ping response times, and anomalies
  • ✉️ Slack / Email notifications — get alerted if something’s not working
  • 👥 Team/shared dashboards — let multiple devs manage and view connections
  • 🧪 Detailed ping logs — including response codes and error messages
  • ⚙️ Custom ping intervals — go beyond presets and set intervals in hours/minutes
  • 🛠 Priority support — for power users or small teams running multiple projects

🙌 Feedback?

I’d love your feedback on:

  • The tool itself
  • How I’ve built it (Next.js 15 tips welcome!)
  • What features you’d expect if you were using something like this for your own dev environment