If you are comparing Opsgenie and PagerDuty in 2026, you are almost certainly an Opsgenie customer with a deadline. Atlassian shuts the product down on April 5, 2027, and PagerDuty is the name most teams write down first.

Prices and features verified on October 29, 2026 on PagerDuty's pricing page, Opsgenie's pricing page and PagerDuty's Opsgenie migration offer. Annual billing unless stated.

Verdict

  • Choose PagerDuty if you route thousands of events from many tools, need ServiceNow or a SIEM in the loop, or run incidents with roles, tasks and workflows.
  • Stay on Opsgenie until you cut over only as a bridge: it still works, but it stops on April 5, 2027 and nothing you leave in it survives.
  • Pick neither if you mainly used Opsgenie for one or two rotations and paging: PagerDuty costs you at least twice the Opsgenie Essentials rate for depth you may never open.

Opsgenie vs PagerDuty at a glance

Opsgenie PagerDuty
Status End of sale June 4, 2025, end of support April 5, 2027 Active
Free plan Up to 5 users, 100 SMS account-wide, no voice 5 users, 1 schedule, 1 escalation policy, 100 SMS or calls a month
Paid from $9.45/user/month (Essentials) $21/user/month (Professional), $25 monthly
Higher tiers $19.95 Standard, $31.90 Enterprise per user PD Reliability Platform, yearly fee from $2,800 for 10 seats
Pricing model Per user Per user, or a yearly platform fee with seats
Uptime checks No No
Heartbeats Built in, Standard and Enterprise No built-in check-in URL, rules-based workaround
Routing rules 1 on Free and Essentials, 100 on Standard and up Event Orchestration
SMS and voice Users × 100 (US/Canada) on Essentials, no cap on Standard and up 100 a month on Free, paid quotas not itemized
Status page No, Statuspage is a separate product External page with 250 subscribers on Professional
Incident roles No 2 predefined on Professional, custom on platform tiers
Integrations Smaller catalog, deepest Jira link 750+
Data retention 3 months Free, 6 Essentials, 1 year Standard Longer on platform tiers
Cost, 5 responders $47.25 (Essentials) $0 (Free) or $105 (Professional)
Cost, 25 responders $498.75 (Standard) $525 (Professional), $1,000+ on the Essential platform tier

On-call scheduling and escalation

Both products do the core job well. Opsgenie let you build layered rotations, overrides and escalation chains on every tier. That is the setup most migrants need to carry over, and PagerDuty covers it: multiple layers per schedule, timezone-aware handoffs, overrides, acknowledge and escalate.

The limits differ. PagerDuty Free gives you one schedule and one escalation policy for five users, which is enough for a single small rotation and nothing more. Professional lifts that and adds a layer Opsgenie never had: two predefined incident roles, three predefined incident types, one workflow and post-incident reviews. The PD Reliability Platform tiers go further with custom roles, more incident types and conditional workflows. If your incident process has an incident commander, a communications lead and a checklist, PagerDuty models it.

Alert routing and noise reduction

This is where PagerDuty pulls away, and where an Opsgenie Essentials team should ask whether it matters.

Opsgenie capped routing rules at one on Free and Essentials, and at 100 on Standard and Enterprise. Teams on the lower tiers routed everything to one policy, which is why many of them never touched the routing features PagerDuty sells.

PagerDuty's Event Orchestration handles conditional routing across services, time windows and severities. AIOps (machine-learning grouping) and PagerDuty Advance (the AI assistant) are add-ons on top of Professional, and AI actions are not included in Professional. If you process a few hundred alerts a month, those add-ons cost more than the routing problem they solve. If you process thousands from Datadog, Splunk and CloudWatch, they are the reason to buy PagerDuty.

Notifications: SMS, phone and push

Notification quotas decide the real cost for teams that page often.

Opsgenie Free has 100 SMS account-wide and no voice. Essentials gives users × 100 SMS and voice for the US and Canada, and users × 25 internationally. Standard and Enterprise remove the cap. That last point was one of Opsgenie's underrated features.

PagerDuty Free caps SMS and phone at 100 a month. Its pricing page does not itemize the quota on Professional, so ask for the number in writing before signing, especially if responders sit outside the US. Both products have a dedicated mobile app with push. Opsgenie's app is deactivated at shutdown, and Atlassian tells users to switch to the Jira mobile app (Atlassian support).

Heartbeats and monitoring

Neither product checks your endpoints. Your uptime monitor stays a separate tool whichever one you pick.

Heartbeats are the one gap that bites Opsgenie migrants. Opsgenie lists heartbeat monitoring on Standard and Enterprise: a backup job, a pipeline or a cron task pings Opsgenie, and a missed ping pages the on-call person. PagerDuty has no built-in check-in URL. Its own heartbeat guide builds one out of Event Orchestration cache variables, suspended alerts and a resolve webhook. The simpler path is a cron-monitoring service that sends missed runs to PagerDuty, which adds a vendor and an integration to maintain.

Status pages and incident communication

Opsgenie never had status pages. Customers who ran a public page bought Statuspage separately, and that subscription is not part of the Opsgenie shutdown, so it keeps running as a second bill.

PagerDuty includes an external status page with 250 subscribers on Professional. The PD Reliability Platform tiers add internal pages and more subscribers, and premium status pages are an add-on. For a SaaS with a few thousand subscribers, plan on that add-on.

Pricing and cost for 5 and 25 people

Opsgenie, annual billing, until the shutdown:

Tier Per user per month Routing rules SMS and voice (US/Canada) Incidents per month
Free $0 1 100 SMS account-wide, no voice Not listed
Essentials $9.45 1 Users × 100 100
Standard $19.95 100 No cap No cap
Enterprise $31.90 100 No cap No cap

PagerDuty, annual billing:

Plan Price Seats
Free $0 5 users
Professional $21 per user per month ($25 monthly) Per user
PD Reliability Platform Starter $2,800 per year 10
PD Reliability Platform Essential $12,000 per year 20
PD Reliability Platform Plus $48,000 per year 50
PD Reliability Platform Ultimate Custom 500

Per month, annual rates:

Opsgenie PagerDuty
5 responders $47.25 Essentials, $99.75 Standard $0 Free, $105 Professional
10 responders $94.50 Essentials, $199.50 Standard $210 Professional, about $233 Starter platform
25 responders $236.25 Essentials, $498.75 Standard $525 Professional, $1,000 Essential platform plus seats beyond 20

PagerDuty Free is a real answer for five people with one rotation. The moment you need a second schedule or a sixth person, the bill jumps to $105. At 10 to 25 responders, Professional costs about what Opsgenie Standard did, so the per-user rate is not the problem. The problem is what stays outside: the uptime monitor, the heartbeat tool, and the platform fee if you want AIOps, custom fields or the analytics dashboard.

What Opsgenie and PagerDuty don't do well

Opsgenie: a shutdown date. After April 5, 2027, users cannot log in or retrieve data, Opsgenie-based integrations stop, the mobile app is deactivated, and only data migrated to Jira Service Management survives (Atlassian support). Before that: no uptime monitoring, no status page, one routing rule and 100 incidents a month on Essentials.

PagerDuty: no uptime monitoring and no built-in heartbeat, so the monitoring stack stays separate. Paid notification quotas are not itemized on the pricing page. AIOps and PagerDuty Advance are add-ons, and custom fields, analytics and longer retention sit on the platform tiers, billed per year upfront. The new pricing page also no longer names the "Operations Cloud Core" plan that the migration offer requires (see below).

What PagerDuty's Opsgenie migration offer includes

PagerDuty published two offers, and the fine print matters.

The Summer 2026 promotional offer (page updated July 10, 2026) is "limited to current Opsgenie customers" and to "the first fifty (50) qualifying customers to execute an agreement for the Operations Cloud Core plan". It provides "up to eighty (80) Expert Service Hours over the first 3 weeks of the plan", covers environments of "up to 250 active users", and "is only valid until June 1, 2028". ITSM integrations such as ServiceNow, complex custom dependencies and net-new builds fall outside it, and "PagerDuty may revoke or modify this offer at any time". The page does not say how many of the 50 spots are left, and the current pricing page sells Professional and the PD Reliability Platform rather than a plan called Operations Cloud Core: ask sales which plan qualifies and whether a spot is still open before you count on it.

The community offer (May 5, 2025) is smaller: free migration support "for implementations under 5 hours" for "organizations up to 100 users", covering user and team migration, escalation policies and schedules, up to 3 monitoring tools and up to 25 services. Larger migrations go through a scoping consultation.

Whatever you choose, export your Opsgenie schedules, escalation policies, routing rules and heartbeats through its REST API now. The Opsgenie migration checklist lists every endpoint and step, and the Opsgenie end-of-life timeline explains the 120-day trap of Atlassian's in-app migration.

What if neither fits?

PagerDuty is the right call for a large SRE organization with a deep integration stack and a formal incident process. Jira Service Management is the right call when incidents already live in Jira; the Opsgenie vs Jira Service Management comparison covers that path and its per-agent cost.

The teams in between used Opsgenie for one to three rotations, an escalation chain and phone alerts, fed by an uptime monitor. For them, two options are worth pricing before PagerDuty:

  • incident.io, if incidents are run in Slack: $15 per user on Team plus $10 per user for on-call, billed yearly, as of October 2026. It has heartbeats but no uptime checks. See PagerDuty vs incident.io.
  • Hyperping, which we make, if you want the uptime checks, cron healthchecks, on-call schedules, escalation and a status page on one bill. Hyperping Essentials is $24 a month billed yearly with 3 seats included and $7 per extra seat. The limits: no native mobile app (alerts arrive by phone call, SMS, Slack or Teams), no event rules engine or AIOps, no incident roles, browser checks from two regions only, no RUM or APM, and a missed healthcheck alerts every channel instead of paging the on-call schedule. The team rebuilds Opsgenie setups for free on paid plans (migration guide).

For the full field, read the Opsgenie shutdown alternatives guide or the best PagerDuty alternatives. Side-by-side pages: Hyperping vs Opsgenie and Hyperping vs PagerDuty.

Why you can trust this comparison

I'm Léo, founder of Hyperping, so I have a commercial stake in where you land, and that is why the product sits in one section after the comparison instead of a column in every table. Every price and limit above comes from the vendors' own pages, checked on October 29, 2026: