Show HN: I built IncidentPulse after getting paged at 3 AM
incident-pulse.vercel.appI built IncidentPulse after the classic "Slack-on-fire, status-page-outdated" outage chaos. It's a clean, self-hosted tool to track incidents, responders, and updates.
Live Demo: https://incident-pulse.vercel.app GitHub: https://github.com/bhoyee/IncidentPulse
I'm at a crossroads and would love your blunt feedback on one question:
What's the ONE feature that would make you actually switch from your current process (be it PagerDuty, a messy Slack channel, or nothing) to a tool like this?
Other things I'd love thoughts on:
Is the webhook setup (with HMAC, idempotency keys) straightforward?
The UI is minimalistic—is it missing any critical info at a glance?
Would you consider self-hosting this, or is a cloud version a must?
I've looked without much success for good resources on training and preparing doe incident management (blog posts, conference talks, books, etc), and haven't found much. Are there resources you're aware of that talk through the process, team training, best practices, role allocations, internal and external communications, etc.? Post mortems are great to read, but they aren't the same as an actual pro-active training process.