I got surprised by a GitHub Actions quota. Built a tool to make sure it never happens again, here's how I built it

Few weeks ago I was pushing a fix for a small project I made related to a minecraft server i play :p. My data updates just stopped... Turns out I burned through the free Actions minutes three days earlier. GitHub doesn't email you, they just silently stop running your jobs. I checked Vercel the next day. 91% bandwidth. Two days from getting throttled. That's when I realised I was doing manual laps of 4 different billing pages every week just to feel safe. GitHub, Vercel, Supabase, Railway and each buried under a different nav, none of them proactively alerting you. I just started college and wanted to build something meaningful, So with the help of Claude Code I built Stackwatch. Here's how it actually works. The polling worker The core is a standalone Node.js worker running on Railway. It's dead simple: a cron job ( node-cron ) that fires every 5 minutes and loops through every connected integration in the database. The clever bit is tier-aware polling. Free users get 15-minute interv