I've been building IncidentPulse after getting tired of managing outages across chaotic Slack threads and outdated status pages.

It's a self-hosted incident management tool that focuses on being clean, simple, and actually useful for small teams. The core features:

Centralized incident timeline with responder assignment

Smart webhook automation with deduplication (using fingerprinting)

Support for Slack, Discord, Teams, Telegram, GitHub Actions, UptimeRobot

Easy self-hosting setup

Live demo: https://incident-pulse.vercel.app GitHub: https://github.com/bhoyee/IncidentPulse

I'd love HN's brutally honest feedback on a few things:

Is the webhook setup (HMAC signatures, idempotency keys, fingerprint deduplication) something you'd actually use, or is it over-engineered?

For small teams – would you self-host something like this, or is a cloud version mandatory?

What's the one feature that would make you switch from your current incident process?

The project is fully open-source, and I'm looking for contributors who enjoy building transparent tools for reliability.