Grafana OnCall OSS was archived on March 24, 2026 — the repo is read-only and self-hosted Cloud Connection telephony stopped working. Staying means running unmaintained paging infrastructure, which is the one component you cannot afford to have rot. OpsPing is a maintained successor for exactly this cohort: it speaks the Opsgenie alert API that OnCall deployments commonly used via the OpsGenie receiver, runs as a private single-tenant deployment (the closest thing to the self-hosted model you chose OnCall for), and costs $8–$15/responder hosted or a private install on your own hardware. If you are all-in on Grafana Cloud, Grafana Cloud IRM keeps everything in one platform — that is its honest advantage.
Side by side
| OpsPing | Grafana OnCall | |
|---|---|---|
| Status | Live and shipping | OSS archived March 24, 2026; repo read-only |
| Self-hosted | Private single-tenant deployments (maintained) | OSS code runs, but unmaintained — no fixes, no Cloud Connection telephony |
| Cloud option | Hosted, $8–$15/responder/month | Grafana Cloud IRM (usage-based, billed per monthly active user) |
| Alert ingestion | Alertmanager/OpsGenie receiver paths, Grafana contact points, webhooks, email-to-alert | Grafana alerting + integrations (as configured) |
| Mobile paging | iOS Critical Alerts, Android DND-bypass alarms — core feature | Mobile app; push reliability varied |
| Schedules and escalations | Rotations, overrides, PTO, escalation policies with repeat | Rotations and escalations (as of archive) |
| Status pages | Included | Not part of OnCall |
| Postmortems | One-click from audit trail | Not part of OnCall |
Checked October 16, 2026. Grafana Cloud IRM pricing is usage-based per monthly active user — see grafana.com/products/cloud/pricing for current numbers.
What moves over cleanly
Point your Grafana contact points or Alertmanager receivers at OpsPing: the OpsGenie receiver compatibility is native, so most OnCall setups change a URL rather than redesign ingestion. Schedules, rotations, and escalation chains rebuild through the importer or API. The Grafana OnCall migration guide walks the full path, including retiring Cloud Connection.
Choose Grafana Cloud IRM if…
- Your observability already lives in Grafana Cloud and you want one bill and one UI.
- You prefer usage-based pricing over per-responder seats.
Choose OpsPing if…
- You chose OnCall OSS because you wanted control — private single-tenant deployments are the maintained version of that choice.
- You need paging that survives silent mode: iOS Critical Alerts and Android DND-bypass alarms are the product's core.
- You want status pages, postmortems, and Slack ack included, not bolted on.
FAQ
Can I keep running the archived OnCall OSS code?
Technically yes, but the former mobile Cloud Connection is gone and the archived project no longer receives bug fixes or security patches. Third-party push and self-managed telephony remain possible when you operate them yourself — budget for that maintenance and risk. Paging infrastructure is the wrong place to run unmaintained code.
Do I need to keep Grafana at all?
No. OpsPing accepts alerts from anything that sends webhooks — Datadog, CloudWatch, Uptime Kuma, Healthchecks, your own scripts. Grafana/Alertmanager is just the smoothest path because the OpsGenie receiver compatibility is native.
Can I script the migration?
Yes — use the documented OpsPing API or importer. The migration guide covers repointing Alertmanager or Grafana contact points, rebuilding schedules and escalation chains, and verifying through the real receiver before cutover.