I built a tool that tells you when you're about to reach your dev stack limits all in one dashboard
Hey PH community 👋
I just launched Stackwatch — a usage monitor for dev teams & Solo devs that tracks GitHub Actions minutes, Vercel bandwidth, Railway and Supabase limits in one place and alerts you before you hit them.
The idea came from a painfully relatable moment: we hit our GitHub Actions limit mid-deploy on a Friday. No warning, no heads-up — just a broken pipeline and a confused team. The fix took 10 minutes, but finding why everything was broken took 45.
The problem isn't that these limits exist. It's that the tools don't talk to each other, so you're either checking 5 dashboards manually or finding out you've crossed a limit when something breaks in production.
What I built:
Connect GitHub Actions, Vercel,cRailway and Supabase with an API key
Get alerted via email, Slack, Discord, or browser push(Based on your plan) when you're approaching a threshold you set
One dashboard that refreshes automatically — no more tab-switching
What I'm genuinely curious about:
What's the most painful "I wish I knew sooner" moment you've had with usage limits or billing surprises in your stack?
Do you actually check usage dashboards proactively, or do you wait for something to break?
Are there other tools (beyond GitHub/Vercel/Supabase/Railway) where you've been caught off guard?
I am actively building out integrations and would love to know where the real pain is for teams like yours.
Would love your feedback on the product — especially if something feels off or missing. Happy to answer anything.
Replies