Incident management alternatives in 2025

Opsgenie is end of life, Grafana OnCall OSS is getting archived

Atlassian announced it is ending support for Opsgenie. Opsgenie will no longer be available for purchase after June 4th of this year. By 2027, Opsgenie “will shut down and will no longer be accessible,” as announced by Atlassian.

However, Atlassian is not the only one closing down an alerting product. Last week, Grafana announced that they’re sunsetting Grafana OnCall OSS. As of right now, the project is in maintenance mode until it gets archived in 2026.

The alerting landscape is evolving rapidly in 2025. Last month, Zenduty, a legacy on-call vendor, was acquired by a privately held IT service desk company. Similarly, Squadcast, another legacy on-call vendor, was acquired by a cloud solutions company. Unfortunately, in this space, acquisitions don’t end well for customers—Opsgenie is just one more example.

As you look for an Opsgenie alternative that will evolve and scale with you, what options do you have?

Option 0 - Continuing down Atlassian’s path

Atlassian acquired Opsgenie in 2018. Post-acquisition, there were no investments in the platform other than branding the UI, as its users lamented for years.

What’s worse, the reliability of Opsgenie was not great. In 2022, Opsgenie’s alerts were down for 14 days for 775 customers. Customers could not even report the issue. After that, unstable performance remained a concern for Opsgenie users.

Now, Atlassian is telling its customers that the company moved these unmaintained on-call features not to one but to two separate products. Atlassian is urging its customers to migrate from Opsgenie. Let’s break down the options that Atlassian is offering its customers.

Migrating to Atlassian Jira Service Management

Your first alternative to set up on-call rotations is to buy one of Atlassian’s largest products. Jira Service Management (JSM) tries to be a single platform where Support and IT teams can collaborate.

Naturally, JSM is centered around tickets. It includes a way to schedule basic on-call rotations because your company may need support available 24/7. The surface of this product is so vast it even includes a proprietary query language.

Now, Atlassian expects SRE teams to be in the mix here with support and IT. While it’s true that SREs also work with on-call rotations, responding to a SEV1 incident is fundamentally different from answering a support ticket.

Not only is JSM not an adequate tool for SREs, but it is also extremely bloated and far from being designed for end-to-end incident lifecycle management.

Migrating to Atlassian Compass

Jira Service Management is an expensive product. Compass, on the other hand, is one of Atlassian’s cheapest products.

Compass is Atlassian’s attempt to offer a developer portal like Spotify Backstage or Cortex. Except it only works if you’re knee-deep and locked in with the Atlassian ecosystem.  You’ll never hear Compass mentioned in any developer portal conversation, not at any conference or event other than Atlassian's.

Now, Atlassian is telling SREs that if they cannot afford Jira Service Management, they can set up their alerts and on-call rotations through Compass, even though this pattern goes against what a developer portal does.

Check how many real developer portals offer alerting as a built-in feature: none. Developer portals are meant to be aggregators to reduce the cognitive load on developers and operators, not half-baked incident management aids.

Option 1 - Migrating to Rootly

Trusted by LinkedIn, NVIDIA, Dropbox, and hundreds of SRE teams, Rootly is a modern on-call and incident management solution with AI-native enhancements.

If you’re coming from Opsgenie, you’ll find Rootly intuitive to use because the core concepts are similar. Just as Opsgenie, Rootly offers a clear different between alerts and incidents, unlike other alerting solutions.

However, from a feature set and capability point of view, you’ll have much more available to you with Rootly.Rootly offers a beautiful UX across web, iOS, and Android. When compared feature by feature, Rootly offers 35+ extra functionalities than Opsgenie.

AI-native on-call and incident response

Set up escalation policies and write post-incident reviews without switching around tools. Rootly offers a comprehensive incident lifecycle platform with native integrations with Slack and MS Teams.

Rootly also offers a suite of privacy-first AI features like incident summaries, suggested team members who’ve resolved similar incidents, and postmortem drafts.

Unparalleled innovation based on SRE needs

The Rootly team works closely with its customers to direct the roadmap. Over the past year, the team shipped over a thousand new features that continuously improve how SRE teams set up on-call schedules, resolve incidents, and learn from past experiences.

For example, in 2025, recent additions to Rootly On-call include a holiday scheduler to coordinate your team’s PTO (so nobody gets an accidental alert at the beach) and an AI-assisted Alert Noisiness reduction system.

Rootly also launches features that help organizations grow in maturity of their reliability practice, like On-Call Readiness Reports and customizable performance dashboards.

Migrate from Opsgenie in <10 minutes

Rootly can help you migrate your alert sources, escalation policies, schedules, and other configurations from Opsgenie in under 10 minutes. Book a demo with one of our reliability advocates. We never talk sales but offer you a technical walkthrough of the platform.

Option 2 - Migrating to PagerDuty

PagerDuty is the largest legacy on-call solution in the market. However, its staggering prices and frustrating UX have made its customers migrate in droves to modern alternatives like Rootly.

Stagnant core product

Despite its customers requesting basic features like the ability to page teams instead of services, or making the on-call coverage experience less of a headache, the core product at PagerDuty has remained the same for the past few years.

Slow Innovation

Rootly launched Slack-native incident response in 2021. PagerDuty couldn’t catch up with the competitive landscape on its own, so it acquired Jeli, an incident management startup, in 2023. It wasn’t until last month, in 2025, that the company started to offer Jeli’s Slack integration to its customers.

PagerDuty launched its basic on-call Slack bot a few years after other competitors. In the mean time, Rootly’s capabilities have evolved to make life for SREs easier through features that do not exist in PagerDuty at all.

Check out a full feature comparison, there are 30+ major features Rootly offers that PagerDuty doesn’t even offer through paid add-ons.

Lagging Business Performance

Atlassian could sunset Opsgenie because it has a diverse portfolio of products. Pagerduty, on the other hand, sells only one product: alerting. Pagerduty’s business is structured around increasing the revenue from each alerting deal by selling add-ons, often at a higher price point than the base product.

However, Pagerduty’s sustained lack of innovation has limited its capacity to retain customers and attract new deals. In 2024, their net new business was close to zero, which means they’re losing customers at the same rate they’re winning them. In the past year, Pagerduty’s stock plummeted by roughly 29%.

Option 3 - Migrating to Grafana OnCall

Grafana is one of the most popular observability platforms. And for a good reason. Grafana offers rich dashboards that lets you visualize data from different sources, including Prometheus, Elasticsearch, AWS, and many others.

The best part? It’s built on open source, which means you could potentially self-host an observability solution. If your team doesn’t have the capacity to self-host or prefer to have SLA guarantees, Grafana offers a fully-managed solution through Grafana Cloud.

Given that Grafana already issues alerts, they decided to spin up Grafana OnCall as an open source project. That way, Grafana could have their users set up simple rotations to manage the alerts that they were generating without much fuzz. Grafana Cloud offers a managed version of Grafana OnCall, it is essentially the same UI and features.

Basic On-call Features Only

Grafana OnCall is very straight-forward. It’s designed for SRE teams with simple needs: you need to set up simple rotations so Grafana notifications can be acknowledged by someone.

If you’re already using Grafana and you’re a compact SRE team with little need for more complex escalation policies or governance features, Grafana OnCall is a great alternative to Opsgenie.

Uncertain future development

Grafana announced that they’re archiving Grafana OnCall OSS in 2026. As of right now, the project is already in maintenance mode.

While the company has made it clear that they will continue to offer managed Grafana OnCall through Grafana Cloud as normal, it is uncertain whether they will continue to invest in the platform.

Option 4 - Migrating to BetterStack

BetterStack is part of the new generation of observability solutions. The company started as a tool to monitor uptime, optimized for developer experience. This is great because you can cover most common use cases—like HTTP availability—with ease. However, you still need to set up other observability tools, such as Prometheus, to scrape apps and services and capture more advanced logs and traces.

Just like Grafana, BetterStack recently added an on-call add-on to their suite, allowing customers to route the notifications their system generates more easily. Over the past year, BetterStack has invested significantly in their on-call offering, building a Slack integration that neatly fits into their observability platform. Yet, BetterStack’s on-call features remain fairly basic.

An option if you’re a BetterStack customer

BetterStack’s on-call solution is tightly integrated with their observability suite, which is the company’s strong point. If you’re already a BetterStack customer and need an easy-to-use on-call solution, integrating it into your stack is a great option. However, if you’re not already using BetterStack for observability, it might be a trickier decision.

BetterStack is great for teams with simple requirements

Not every team needs complex workflows and escalation policies, which makes BetterStack a strong option for those with simpler needs. If you’re already a customer and only need basic rotations, BetterStack is a good option to consider.

However, if you need round-robin escalation policies, vacation-aware rotation schedules, shadow rotations, or simplified coverage requests, you may want to consider an alternative like Rootly.

Option 5 - Migrating to Splunk On-Call

Splunk On-Call, previously known as VictorOps before being acquired by Splunk, is a legacy on-call management solution with deep roots in the enterprise observability landscape. To get an idea of the experience you can expect, check out the following screenshot taken from their “Getting Started” documentation page:

Outdated UI and limited functionality

Splunk On-Call features what might be one of the most anachronistic UIs in the on-call landscape. It’s difficult to figure out what’s going on on any given screen—navigation feels unintuitive, and you’ll likely need to go through corporate training videos just to get the hang of it.

What’s more problematic is that this unnecessary complexity doesn’t bring additional flexibility or power. Instead, the feature set offered by Splunk On-Call is rather limited. You can only assign rigid on-call rotations to users, and there aren’t many options for escalation policies. The same applies to alerting, and there’s no AI on the roadmap for Splunk On-Call.

Only compatible with Splunk

Splunk On-Call is only compatible with Splunk as an observability source. If you’re not a Splunk customer, you can’t get access to Splunk On-Call—it’s sold exclusively as an add-on to their observability platform.

Option 6 - Migrating to xMatters

xMatters is a legacy on-call vendor geared toward enterprise teams. The UX across both mobile and web is dated and offers limited functionality. Scheduling options are rigid and lack support for modern escalation policies, and integrations with tools like Slack are minimal.

Shocking lack of transparency

If you visit the xMatters website, you’ll notice there are no actual screenshots of the product on the marketing pages—only product-style illustrations that don’t represent the real interface. Even the documentation is gated behind a customer login.

Pricing details are also absent. Overall, it’s hard to understand what xMatters actually does without booking a sales call.

Minimal integration with Slack and MS Teams

xMatters provides only limited integration with popular collaboration tools like Slack and MS Teams. Instead of offering native support, they offer customers the ability to deliver xMatters alerts to Slack and MS Teams “as a device”—a setup each individual user must configure on their own.

Conclusion

Hundreds of Opsgenie customers have migrated to Rootly over the past year, drawn by its vast feature set and modern UX. Trusted by industry leaders like LinkedIn, Cisco, NVIDIA, and hundreds of SRE teams, Rootly offers a complete end-to-end incident management platform.

Newer on-call solutions—like those from BetterStack or Grafana OnCall—are great options if you’re already part of those ecosystems and have simpler requirements.

Meanwhile, legacy on-call tools like PagerDuty, Splunk On-Call, and xMatters are quickly becoming obsolete as their feature sets remain stagnant and difficult to use. If you're searching for an Opsgenie alternative, moving to one of these older tools may not be your best bet.

‍