Grafana OnCall vs Keep
Self-host pick — both replace PagerDuty (On-call rotation / incident response / paging).
Both Grafana OnCall and Keep self-host as a replacement for PagerDuty (On-call rotation / incident response / paging). Pick Grafana OnCall if you want a AGPL-licensed codebase (AGPL-3.0); pick Keep for MIT (MIT). Both run in roughly the same cost bracket — $10-15 vps; sms/voice still costs at twilio's per-leg rate ($0 vs $10-20 vps; sms/voice via twilio at the usual per-leg rate ($0.
| Grafana OnCallopen-source | Keepopen-source | |
|---|---|---|
| License | AGPL-3.0 | MIT |
| Setup time | 30min docker-compose (OnCall engine + Postgres + Redis + Celery worker) | 30min docker-compose (keep-frontend + keep-backend + websocket-server; SQLite default, swap to Postgres via `DATABASE_CONNECTION_STRING`) |
| Monthly cost | $10-15 VPS; SMS/voice still costs at Twilio's per-leg rate ($0.0075-0.05/leg). | $10-20 VPS; SMS/voice via Twilio at the usual per-leg rate ($0.0075-0.05/leg). |
| GitHub | grafana/oncall | keephq/keep |
| Replaces | PagerDuty | PagerDuty |
Good fit for
Grafana OnCall
Teams already running Grafana / Prometheus that want on-call to live next to dashboards.
Weak at:**Repository archived 2026-03-24** — Grafana announced end-of-development; the freshness pill on this page reflects that. Existing self-hosted deploys keep running, but no upstream fixes are coming. Web UI is functional, not polished; mobile app exists but is thinner than PagerDuty's.
Keep
Teams that want alert dedup, correlation, and workflow automation alongside on-call paging — i.e. the noisy-alerts problem and the on-call problem solved by the same tool. Currently the most actively maintained option in this category.
Weak at:Pure on-call scheduling UI is thinner than PagerDuty's — Keep leads with alert orchestration, not rotation calendars. If all you need is 'who's on-call this week', the workflow surface is more than you'll use.
In a terminal? npx -y github:SolvoHQ/os-alt-cli pagerduty prints PagerDuty's self-host options including both —
how the CLI works →
FAQ
Which is easier to self-host, Grafana OnCall or Keep?
Grafana OnCall: 30min docker-compose (OnCall engine + Postgres + Redis + Celery worker). Keep: 30min docker-compose (keep-frontend + keep-backend + websocket-server; SQLite default, swap to Postgres via `DATABASE_CONNECTION_STRING`).
What does each cost to run?
Grafana OnCall: $10-15 VPS; SMS/voice still costs at Twilio's per-leg rate ($0.0075-0.05/leg).. Keep: $10-20 VPS; SMS/voice via Twilio at the usual per-leg rate ($0.0075-0.05/leg).. Both projects are free and open source.
Do Grafana OnCall and Keep replace the same SaaS?
Yes — both are open-source alternatives to PagerDuty.