// the take
Grafana OnCall was an open-source on-call management tool built as a Grafana plugin — schedule rotations, escalation chains, and multi-channel alerting (Slack, Telegram, phone, SMS). It entered maintenance mode in March 2025 and was archived in March 2026, so it is dead software. Anyone looking for a self-hosted option needs to look elsewhere.
The escalation chain model was genuinely well-designed: you could build arbitrarily complex notify-wait-escalate trees without scripting. Jinja2 templating for alert payloads gave real control over how alerts surfaced per-channel. The migration tooling for moving from PagerDuty and other tools was a practical touch that most competitors skip. The Slack integration was deep enough to acknowledge, resolve, and page directly from a thread.
It is archived — last push was March 2026 and Grafana explicitly killed it in favor of their cloud product. The Django/Celery/Redis stack was operationally heavy for a tool most teams run on one or two servers; the docker-compose setup papered over real complexity. Self-hosting the phone/SMS path required going through Grafana Cloud anyway, which undermined the self-hosted pitch. The plugin architecture meant your Grafana version and OnCall version had to stay in sync, and that coupling caused breakage on upgrades.
We read the README, the directory tree and a key source file in July 2026. Nobody pays to be listed. How we judge →