Grafana OnCall vs Oncall (LinkedIn)
Self-host pick — both replace PagerDuty (On-call rotation / incident response / paging).
Both Grafana OnCall and Oncall (LinkedIn) 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 Oncall (LinkedIn) for BSD (BSD-2-Clause). Both run in roughly the same cost bracket — $10-15 vps; sms/voice still costs at twilio's per-leg rate ($0 vs $10 vps; pair with iris (sister project) for paging — same upstream twilio cost.
| Grafana OnCallopen-source | Oncall (LinkedIn)open-source | |
|---|---|---|
| License | AGPL-3.0 | BSD-2-Clause |
| Setup time | 30min docker-compose (OnCall engine + Postgres + Redis + Celery worker) | 30min docker-compose (Oncall + MySQL + Iris for paging) |
| Monthly cost | $10-15 VPS; SMS/voice still costs at Twilio's per-leg rate ($0.0075-0.05/leg). | $10 VPS; pair with Iris (sister project) for paging — same upstream Twilio cost. |
| GitHub | grafana/oncall | linkedin/oncall |
| 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.
Oncall (LinkedIn)
Larger orgs that already use Iris for paging and want a calendar-shaped rotation tool with strong audit logs.
Weak at:**Last commit Aug 2025** — repo is unarchived but no longer actively pushed (freshness pill: stale). Two-component setup (Oncall + Iris); UI looks 2018; less active than Keep or pre-archive Grafana OnCall.
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 Oncall (LinkedIn)?
Grafana OnCall: 30min docker-compose (OnCall engine + Postgres + Redis + Celery worker). Oncall (LinkedIn): 30min docker-compose (Oncall + MySQL + Iris for paging).
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).. Oncall (LinkedIn): $10 VPS; pair with Iris (sister project) for paging — same upstream Twilio cost.. Both projects are free and open source.
Do Grafana OnCall and Oncall (LinkedIn) replace the same SaaS?
Yes — both are open-source alternatives to PagerDuty.