PagerDuty vs Opsgenie vs VictorOps pricing and on-call features compared

PagerDuty vs Opsgenie is no longer a choice between two products you can both buy. Atlassian stopped selling Opsgenie on June 4, 2025 and shuts it off on April 5, 2027, so only existing customers can renew, and only up to that date. PagerDuty is still on sale: Professional costs 21 USD per user per month billed annually, and its higher tiers moved in 2026 to the PD Reliability Platform, which starts at 2,800 USD a year for 10 seats. If you are an Opsgenie customer, the real comparison is PagerDuty, Atlassian's own replacements (Jira Service Management and Compass) and an independent tool such as IncidentBot, which starts at 24 USD per user billed annually with a status page included.

Run a sample incident

Which one should you pick in 2026

On-call engineers reviewing an escalation plan together at a shared desk

Pick by where you are today, not by which tool was better in 2022.

Splunk On-Call, the product formerly called VictorOps, is the third name in most of these searches. It is still sold and supported as part of Splunk under Cisco, with no end of life announced, but it does not publish a per-user price.

You already run Opsgenie and have a renewal before April 2027. Renew for the shortest term Atlassian offers, then use the months you have left to run a replacement in parallel. Opsgenie is not a long term option for anyone.
You are new to on-call and comparing the two. Opsgenie is not available to you. Compare PagerDuty with the tools that are still sold, including Jira Service Management if your incident process lives in a service desk.
You want paging, Slack incident channels and a status page on one bill. PagerDuty can do it with add-ons or a platform plan. IncidentBot does it on every plan, from 24 USD per responder billed annually.
You need ServiceNow sync, AIOps noise reduction and hundreds of integrations at enterprise scale. PagerDuty's platform plans are built for that, and the bill reflects it.

PagerDuty vs Opsgenie vs VictorOps at a glance

PagerDuty details come from pagerduty.com/pricing and Opsgenie details from atlassian.com, both checked in October 2026. Confirm on the vendors' sites before you sign, since packaging changes.

What you check	PagerDuty	Opsgenie	Splunk On-Call (VictorOps)	IncidentBot
Can a new customer buy it	Yes	No. End of sale June 4, 2025, end of support April 5, 2027	Yes	Yes, online without a sales call
Entry paid price	Professional 21 USD per user a month annual, 25 monthly	Essentials 9.45 USD per user annual, renewals only	Not published per user	Starter 24 USD per user annual, 49 monthly
Higher tiers	PD Reliability Platform: Starter 2,800 USD a year for 10 seats, Essential 12,000 for 20, Plus 48,000 for 50, Ultimate custom	Standard 19.95 USD, Enterprise 31.90 USD per user annual, renewals only	Quote	Team 49 USD, Business 99 USD per user annual
Free plan	Up to 5 users, 1 schedule, 1 escalation policy, 100 SMS or phone notifications a month	Closed to new sign-ups with the rest of Opsgenie	No	No free plan; the incident simulator runs without an account
Status page	External page up to 250 subscribers on Professional; private pages on platform plans	Through Atlassian Statuspage, sold separately	Not included	1 public page on Starter, 3 public or private on Team, unlimited on Business
Read-only stakeholders	Counted in platform seats; add-on on Professional	Stakeholder roles on higher tiers	Stakeholder users included on some plans	Viewers included, never billed
Incident run in Slack	Slack and Teams app on every plan, 1 incident workflow on Professional, unlimited on platform plans	Slack and Teams alert actions	Slack alert actions	`/incident` channel with commander, comms and scribe roles from Team
Ticketing	Jira and Zendesk on every plan, ServiceNow on platform plans	Deep Jira and Confluence links	Jira and ServiceNow integrations	Postmortem action items to Jira and Linear on Team and above

Where PagerDuty wins: the largest integration catalog in the category (750 plus), AIOps and runbook automation, ServiceNow sync and a mature mobile app. Where Opsgenie won: the lowest seat price of the three and the tightest Jira link, which is exactly what Atlassian is now moving into Jira Service Management. Where IncidentBot wins: a status page and Slack incident roles in the base price, free stakeholders and a published price that does not jump to a yearly platform fee.

PagerDuty vs Opsgenie pricing for a 10 and a 40 responder team

List prices per month with annual billing. Every responder carries the pager. PagerDuty platform fees are divided by 12. Opsgenie rows apply only to existing customers and only until April 5, 2027. Compass Premium is Atlassian's on-call replacement with escalation policies and voice; it bills monthly only.

Setup	10 responders, per month	40 responders, per month
PagerDuty Professional (status page add-on extra)	210 USD	840 USD
PD Reliability Platform Starter (10 seats including stakeholders)	233 USD	not enough seats
PD Reliability Platform Plus (50 seats)	4,000 USD	4,000 USD
Opsgenie Standard, renewal only	199.50 USD	798 USD
Atlassian Compass Premium	239.60 USD	958.40 USD
IncidentBot Starter (1 public page, 100 SMS and voice per user)	240 USD	960 USD
IncidentBot Team (3 public or private pages, unlimited SMS and voice)	490 USD	1,960 USD

Read it honestly. For pure paging, PagerDuty Professional is the cheapest option you can still buy, 3 USD a seat under IncidentBot Starter, and Opsgenie Standard is cheaper still until it is switched off. At 40 responders PagerDuty's platform jumps from Essential (12,000 USD a year for 20 seats, plus credit packs at a price you get from sales) to Plus at 48,000 USD a year, which is where IncidentBot Team costs less than half. The PagerDuty Professional rows leave out the status page and AIOps add-ons, which have no public price.

More detail on each vendor: PagerDuty pricing has the full plan list and add-ons, and Opsgenie pricing prices Opsgenie, Compass and Jira Service Management for 5, 15 and 40 users. IncidentBot pricing has a seat calculator for any team size.

Scheduling, routing and incident response

Scheduling is where Opsgenie earned its fans. Its rotation editor was easy to read and its activity stream showed every on-call change. PagerDuty's scheduling handles layered, multi-team rotations and round robin on platform plans, but takes longer to set up. IncidentBot's on call scheduling software covers rotations, overrides, swaps, follow-the-sun and calendar sync, with up to 3 schedules on Starter and unlimited from Team.

Routing and noise are PagerDuty's strongest ground. Alert grouping, suppression and intelligent triage come with AIOps, which is an add-on on Professional and included on the platform plans. Opsgenie offered alert policies and deduplication on every tier. IncidentBot deduplicates and groups repeat alerts on Team and above, and routes by service and severity; see incident alerting for the rules.

Incident response is where the three differ most. PagerDuty allows one incident workflow on Professional and unlimited workflows on the platform plans, with conditional logic and incident tasks from Plus. Opsgenie handed bigger incidents to Jira Service Management. IncidentBot opens a Slack channel with /incident, sets severity SEV1 to SEV4, assigns roles and posts the runbook on every plan; the Slack incident management app page shows the commands.

Status pages and the people who only read

Every major incident has more readers than responders: support leads, account managers, executives. PagerDuty counts them in platform seats or sells stakeholder licenses on Professional. Opsgenie relied on Atlassian Statuspage, which is a separate subscription from 29 to 1,499 USD a month (see Statuspage pricing). IncidentBot includes a hosted status page app in every plan and lets anyone follow incidents as a viewer without a seat.

Moving from Opsgenie to PagerDuty or IncidentBot

Engineer confirming a test notification on a phone next to a laptop

The steps are the same whichever tool you pick, and the old tool keeps paging until the last one.

A team of 10 to 50 responders usually finishes in two to three weeks of calendar time. Leave a margin before April 5, 2027 and avoid cutting over during a release freeze or holiday rotation. The Opsgenie alternative page maps every Opsgenie concept to its IncidentBot equivalent.

Export: take teams, schedules, escalation policies, integrations and notification rules out of Opsgenie while you still have full access.
Rebuild: import schedules and escalation policies into the new tool (IncidentBot imports them directly from Opsgenie, including overrides already on the calendar) and have each engineer check their own shifts.
Re-point alerts: add the new tool next to Opsgenie in each monitoring source, one service at a time, starting with the least critical.
Parallel run: keep both paging for one to two weeks. Every engineer installs the mobile app and confirms a test page by push, SMS and voice.
Cut over: remove Opsgenie per service once the parallel run matches, then cancel before your renewal.

Other tools on the same shortlist

Most teams leaving Opsgenie also look at Splunk On-Call (VictorOps), incident.io, ilert, Squadcast and Grafana Cloud IRM. VictorOps users weighing a move can read the Splunk On-Call alternative page, and teams leaning toward PagerDuty but worried about the platform fee should read the PagerDuty alternative comparison. Slack-first teams usually price the incident.io alternative, and EU-hosted ilert is covered on the ilert alternative page. For a shortlist by team type see best incident management software.

Is Opsgenie better than PagerDuty?

Neither is better for a new buyer, because Opsgenie can no longer be bought. For existing customers, Opsgenie was cheaper and easier to schedule in, with the tightest Jira link, while PagerDuty has stronger routing, AIOps and far more integrations. Opsgenie stops working on April 5, 2027, so the useful comparison is PagerDuty against the tools still on sale.

Is Opsgenie being discontinued?

Yes. Atlassian announced the end of Opsgenie as a standalone product on March 4, 2025, ended sales to new customers on June 4, 2025 and ends support on April 5, 2027. After that date access is shut off. Existing customers can renew only for terms that end before April 5, 2027.

What is replacing Opsgenie?

Atlassian is moving Opsgenie's alerting and on-call into Jira Service Management and Compass. Teams that used Opsgenie only for paging and on-call often pick a dedicated tool instead: PagerDuty for enterprise scale, or IncidentBot when they want on-call, Slack incident channels and a status page on one seat price from 24 USD per user.

Is Opsgenie cheaper than PagerDuty?

Yes, on list price. Opsgenie Essentials is 9.45 USD and Standard 19.95 USD per user per month billed annually, against 21 USD for PagerDuty Professional. That saving only lasts until April 5, 2027. Atlassian's replacement with escalation and voice, Compass Premium, costs 23.96 USD per user per month.

How much does PagerDuty cost per user?

PagerDuty Professional costs 21 USD per user per month billed annually or 25 USD monthly, and a free plan covers up to 5 users. Higher tiers are now the PD Reliability Platform, priced as a yearly fee: Starter 2,800 USD for 10 seats, Essential 12,000 USD for 20 and Plus 48,000 USD for 50. Checked on pagerduty.com in October 2026.

Is VictorOps the same as Splunk On-Call?

Yes. Splunk bought VictorOps in 2018 and renamed it Splunk On-Call. It is still sold and supported under Cisco, which owns Splunk, and no end of life has been announced. Its price is quoted rather than published per user.

Can we try IncidentBot before we migrate?

Yes. The incident simulator runs a sample incident in your browser: an alert, escalation through a policy you build, a Slack channel, a status page draft and a postmortem skeleton. No account is needed.

Replace Opsgenie before April 2027 without a gap in paging

Create your account, import your schedules from Opsgenie and run both tools side by side until every page lands.