1 day ago
Sat Nov 15, 2025 1:30pm PST
Show HN: I built IncidentPulse after getting paged at 3 AM
I 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?

read article
comments:
add comment
loading comments...