Grafana OnCall OSS was archived on March 24, 2026. No new features. Security patches only for CVSS 7.0+ vulnerabilities. SMS, phone, and push notifications via Cloud Connection stopped working on that date.
If you were self-hosting Grafana OnCall OSS, your practical choices are to move to Grafana Cloud IRM, switch to another tool, or continue running the archived OSS version with its new limitations.
This list covers the first two options. Grafana Cloud IRM is included because it is the official migration path. The remaining five are standalone alternatives.
Disclosure: Runframe is our product. It is included alongside other options. Pricing checked April 2026.
At a glance
| Tool | Price (per user/month) | Grafana Cloud Required? | On-Call Bundled? | Best For |
|---|---|---|---|---|
| Runframe | $15/user/mo (Free tier available) | No | Yes | Startups who want Grafana OnCall simplicity without Grafana Cloud |
| Grafana Cloud IRM | $20/user + $19/mo platform (Free for 3 users) | Yes | Yes | Teams already invested in Grafana Cloud |
| PagerDuty | ~$21-41/user/mo (Free tier, limited to 5 users) | No | Yes | Enterprises needing 700+ integrations and compliance |
| incident.io | $19-25/user + $10-20 on-call (Free Basic tier) | No | Add-on (separate pricing) | Slack-heavy teams wanting premium incident workflows |
| Squadcast | $20-29/user/mo (Free tier available) | No | Yes | Budget-conscious teams accepting acquisition risk |
| Rootly | $20/user/mo per product | No | Add-on (separate pricing) | Teams prioritizing workflow automation |
The bottom line: If you were happy with OnCall OSS because it was simple, free, and worked, Runframe and Squadcast are closest in simplicity and scope. PagerDuty and incident.io offer more sophistication at higher cost. If you are already on Grafana Cloud, IRM is the path of least resistance.
What you are migrating from
Grafana OnCall OSS gave you on-call scheduling with rotations and overrides, escalation chains with configurable timeouts, Slack and Telegram integration, and webhook-based alert routing from Grafana Alerting, Prometheus, and others. It was free, self-hosted, and had no per-user fees.
The tools below are evaluated against what OnCall OSS actually did, not what enterprise tools are optimized for. Pricing was verified against official documentation in April 2026. For a broader view of incident management tools with bundled on-call, see our full comparison.
1. Runframe
Price: Free / $15/user/month
Runframe is standalone incident management and on-call. No Grafana Cloud dependency. On-call scheduling, escalation policies, and Slack-native incident workflows are included at every tier.
If you were using Grafana OnCall mainly for on-call scheduling with Slack notifications, Runframe covers that plus incident management. You get rotations (daily, weekly, biweekly, monthly), primary and secondary on-call, configurable escalation timeouts, and multi-channel alerting through Slack, email, SMS, and voice calls.
It accepts webhooks from Datadog, Prometheus, CloudWatch, and any custom source. See webhooks integration for details on alert routing. Grafana Alerting webhook payloads can typically be routed through Runframe's generic webhook endpoint, but teams should validate mappings during migration.
What carries over: On-call rotations with overrides, escalation policies with configurable timeouts, Slack integration (channel creation, slash commands, interactive buttons), webhook-based alert routing from Prometheus, Datadog, or CloudWatch, and a free tier for small teams.
What is new: Incident management with status tracking, timelines, severity levels, and SLAs. AI-generated postmortem drafts. SMS and voice call escalation. A public API and MCP server for AI agent workflows.
What is different: SaaS only, no self-hosting option. No Telegram, it is Slack-native. It is a newer product.
This works well if you used OnCall for on-call plus Slack and want a standalone replacement without buying into a larger platform. See pricing details for plan comparison.
Start free. No credit card required.
2. Grafana Cloud IRM
Price: Free (3 active users) / $20/active user/month + $19/month platform fee
The official successor. Grafana merged Grafana OnCall and Grafana Incident into Cloud IRM. If you are already paying for Grafana Cloud for dashboards and alerting, this is the easiest path. Your alert routing stays native.
The migration is documented. Escalation chains, schedules, and integrations carry over if you were connected to Grafana Cloud. The open-source plugin data can be migrated using Grafana's tools.
The tradeoff: IRM requires Grafana Cloud. If you were self-hosting everything (Grafana plus OnCall), you are now buying a managed platform. For 20 active IRM users, that is $419/month ($20 x 20 plus the $19 platform fee) plus whatever you pay for Grafana Cloud itself.
This works well if you are already on Grafana Cloud and want the easiest migration with zero alert routing changes. It is probably not worth it if you would be buying Grafana Cloud just for this.
3. PagerDuty
Price: Free (5 users) — Professional starts at ~$21/user/month and Business at ~$41/user/month (annual pricing). For a 20-user team, that is roughly $420–820/month before add-ons. Add-on (separate pricing)s like AIOps, status pages, and stakeholder licenses can increase total cost.
PagerDuty is the default choice. 700+ integrations, on-call and incident management in one product, they have been doing this since 2009.
OnCall migrants need to decide whether they need PagerDuty's scale. OnCall users tend to be smaller teams, maybe 10-50 engineers, who valued simplicity and cost. Professional at ~$21/user/month is a big jump from free. Some teams may find they need Business-tier features once they move beyond basic paging.
PagerDuty has a Prometheus integration and accepts Grafana Alerting webhooks. The migration path exists, but expect a week of configuration for routing rules, escalation policies, and service mapping.
This works well if you are over 100 engineers and the integration catalog and compliance certifications justify the price. It is probably overkill if you were happy with OnCall's simplicity. For a deeper comparison of PagerDuty alternatives, see our dedicated guide.
4. incident.io
Price: Basic free / $19/user/month (Team) / $25/user/month (Pro), plus on-call at $10-20/user/month extra
incident.io has strong Slack-based incident management and added on-call in 2024. On-call is a separate add-on, not included in the base price. Total cost with on-call on Team is $31/user/month.
For OnCall migrants, incident.io makes sense if you were already looking for better incident management alongside on-call. If you just need on-call scheduling, the base price plus add-on costs more than you need.
There is a free Basic plan now, but it is intentionally limited. It includes incident response, a status page, and single-team on-call. Most growing startups comparing paid tools will really be looking at Team or Pro.
No free tier for the paid plans. It is a better fit for teams that want richer incident workflows, not just basic on-call scheduling. It can feel heavy for the kind of 15-person team that was running OnCall OSS.
This works well if you are 50+ engineers, want the best Slack incident experience, and do not mind paying for on-call separately.
5. Squadcast
Price: Free (up to 5 users) / $20/user/month (Pro, annual billing) / $29/user/month (Premium, annual billing) / Enterprise custom
Squadcast bundles on-call, incidents, SLO tracking, and status pages at every tier. Acquired by SolarWinds in 2025.
If you were on OnCall because it was free and simple, Squadcast's free tier (5 users) and $20/user Pro plan are the closest in spirit. The SolarWinds acquisition introduces some uncertainty around long-term roadmap and positioning.
The UI is rougher than incident.io or PagerDuty. SSO and audit logs require the $39/user Enterprise tier.
This works well if you are a small team, 5-50 engineers, optimizing for lowest cost and can live with the acquisition risk.
6. Rootly
Price: $20/user/month per product (incident response and on-call priced separately)
Rootly is Slack-native incident management with strong workflow automation. On-call was introduced later and is offered as a separate product. If you need conditional logic, like routing SEV1s differently than SEV3s or auto-creating Jira tickets for specific services, Rootly's workflow builder is the most capable here.
For OnCall migrants, Rootly is overkill if you just need on-call scheduling. It makes sense if you want to level up your incident response at the same time. They offer up to 50% off for startups under 100 employees.
On-call and incident response together cost $40/user/month before discounts. No free tier.
This works well if you are 50-500 engineers, want advanced automation, and qualify for the startup discount.
Migration checklist
Switching from OnCall OSS? Here is what to plan for:
- Export your current schedules. Document rotations, override patterns, and escalation chain timeouts before they become inaccessible.
- Map your alert routing. List every webhook integration sending alerts to OnCall and note the payload format.
- Test webhook compatibility. Most tools accept Prometheus or Alertmanager webhook format. Test before cutting over.
- Migrate in parallel. Run both tools for 1-2 weeks. Route alerts to both. Verify paging works on the new tool before decommissioning OnCall.
- Update runbooks. Any documentation referencing OnCall URLs, slash commands, or escalation paths needs updating.
Common questions
Can I keep self-hosting Grafana OnCall?
Technically, yes. The repo is archived, not deleted. But there are no new features, no community support, and SMS, phone, and push via Cloud Connection stopped working March 24. Security patches are CVSS 7.0+ only. Running an unmaintained on-call tool is a risk most teams should not take. Teams also evaluating other tools may want to see our comparison of incident management tools with bundled on-call for a broader market view.
Is Grafana Cloud IRM the same as Grafana OnCall?
It is the managed successor. Merges OnCall and Grafana Incident into one product. The on-call UI is familiar, but it requires Grafana Cloud and costs $20/active user/month plus $19 platform fee.
What is the cheapest alternative?
Runframe and Squadcast both have free tiers for up to 5 users. Runframe includes on-call and incidents. Squadcast adds status pages and SLOs on free.
Which tool is closest to what OnCall did?
For teams that mainly used OnCall for scheduling, escalation, and Slack notifications, standalone tools like Runframe and Squadcast are likely the closest fit in scope. If you need native Grafana Alerting integration, Cloud IRM is the only option that preserves that.
Our recommendation
Pick based on what you valued in OnCall OSS:
If you valued simplicity and cost: Runframe Free or Growth, or Squadcast Pro. Both preserve the "just works" experience without enterprise complexity.
If you valued Grafana integration: Cloud IRM is your path. Paying for Grafana Cloud is now required, but your alerting stays native.
If you valued having everything in one place: PagerDuty has everything, but you pay for the breadth. incident.io and Rootly offer on-call as an add-on.
If you are unsure: Most tools in this list offer free tiers or trials. Test with a small group before committing your full team.
For teams evaluating multiple tools, our comparison of incident management tools with bundled on-call covers options beyond the Grafana ecosystem.
Last updated: April 15, 2026. Pricing and features verified against official documentation. Suggest a correction.