Why Alerts Are Email-Only (For Now)

One channel, not three unfinished ones

It would be easy to ship a Slack integration, a webhook, and email all at once, each doing the bare minimum. Instead, alerts go out one way: email. Every incident, every recovery, every platform-status change — one channel, built to be reliable rather than three built to check a box.

What "reliable" means in practice

An alert email fires exactly once per state change: once when an incident opens, once when it recovers. No duplicate sends from a retried job, no digest that buries the one email that mattered among ten that didn't. That guarantee is easier to hold for one channel than to hold consistently across several at once.

Why this is worth saying out loud

It would be easy to imply more channels exist than actually do. They don't, yet — this is the honest state of the product today, not a roadmap dressed up as a feature list. If a webhook or a chat integration ships later, it'll be because email alerts are solid enough first that adding a second channel doesn't put that reliability at risk.