Prices and plans checked on November 2, 2026, on each vendor’s own pricing page.
Quick answer: OpsGenie stopped taking new customers on June 4, 2025, and shuts down on April 5, 2027. Atlassian’s own path is Jira Service Management (JSM). PagerDuty is a popular alternative for OpsGenie users. It fits teams that send thousands of alerts from many monitoring tools, or that run incidents with roles, workflows and ServiceNow. For a team of 10 to 100 people that used OpsGenie for alerting and on-call, PagerDuty Professional costs about twice OpsGenie Essentials. Much of the extra depth may go unused. A standalone on-call tool (like Spike) is the other option.
TL;DR
- PagerDuty Professional costs $25 per user per month. That’s $250 a month for 10 people, $625 for 25 and $1,250 for 50.
- Noise reduction (AIOps) is an add-on that starts at $799 a month. AI features, call routing and larger status pages cost extra too.
- PagerDuty’s OpsGenie migration offer is real, but it’s limited to the first 50 customers. The bundle is priced through sales.
- PagerDuty has no built-in heartbeat check, so cron jobs and backups need a separate monitoring tool.
Is PagerDuty a like-for-like swap for OpsGenie?
If you’re comparing OpsGenie and PagerDuty in 2026, you likely run OpsGenie today and need to move before it shuts down on April 5, 2027. PagerDuty has been around since 2009 and is a popular name in on-call. So it’s natural that your team considers it.
The usual thinking is that PagerDuty is the safe, like-for-like swap. Sure, the core is the same: schedules, escalation policies and phone alerts work much like they did in OpsGenie. But the bill and the setup are where the two part ways. At OpsGenie Standard prices, the per-user rate looks familiar, but what stays outside the base plan decides the real cost.
We built Spike, an on-call tool, so we have a stake in where you land. I tested PagerDuty myself, and every price below comes from the vendor’s own page. Spike gets one section near the end instead of a column in every table.
The comparison is shaped around the two questions that usually decide the answer: how big your team is and what your monitoring stack sends. First comes a side-by-side view, then the cost at three team sizes, then how each tool handles the things OpsGenie users rely on.
OpsGenie vs PagerDuty at a glance
| OpsGenie | PagerDuty | |
|---|---|---|
| Status | Sales ended June 4, 2025; shuts down April 5, 2027 | Active |
| Can new teams buy it? | No | Yes |
| Free plan | 5 users, 100 SMS, no voice | 5 users, 1 schedule, 1 escalation policy, 100 SMS or phone alerts a month |
| Paid entry plan | Essentials, $11.55 per user per month | Professional, $25 per user per month |
| Pricing model | Per user | Per user, or a yearly platform fee with a set number of seats |
| Phone and SMS | Essentials: 100 per user (US and Canada); Standard and up: unlimited | Free: 100 a month; Professional: included |
| Alert routing | 1 routing rule on Essentials, 100 on Standard | Event Orchestration; grouping and suppression need the AIOps add-on on Professional |
| Heartbeats | Built in | No built-in check; a recipe built from Event Orchestration |
| Incoming call routing | 1 number on Standard and up | Add-on on Professional |
| Status page | None (Statuspage.io is a separate product) | One external page with 250 subscribers on Professional |
| Mobile app | Stops working on April 5, 2027 | Active |
| Integrations | 200+, with the deepest Jira link | 750+ |
Sources: OpsGenie pricing, PagerDuty pricing. Monthly billing.
The table shows features, but it can’t show your bill. On PagerDuty, the bill depends on how many alerts you send and which add-ons you end up needing. The next section puts numbers on that.
OpsGenie vs PagerDuty pricing for 10, 25 and 50 people
These are list prices with monthly billing. PagerDuty’s yearly platform plans are paid upfront, so they’re shown as a monthly average.
| Team size | OpsGenie Essentials | OpsGenie Standard | PagerDuty Professional | PagerDuty platform plan |
|---|---|---|---|---|
| 10 people | $115.50 | $241.50 | $250 | Starter: about $233 ($2,800 a year, 10 seats) |
| 25 people | $288.75 | $603.75 | $625 | Essential: $1,000 ($12,000 a year, 20 seats) plus extra seats |
| 50 people | About $525 | Up to $1,207.50 | $1,250 | Plus: $4,000 ($48,000 a year, 50 seats) |
OpsGenie lowers its per-user rate above 25 users, so the 50-person figures are estimates. With yearly billing, PagerDuty Professional drops to $21 per user and OpsGenie Essentials to $9.45.
Two things stand out. PagerDuty Professional costs about what OpsGenie Standard did, so teams coming from Standard won’t see a big jump in the per-user rate. Teams on Essentials pay a little over twice as much.
PagerDuty’s free plan also has a sharp edge. It covers five people with one schedule and one escalation policy. A second rotation or a sixth person moves the whole team to Professional, which is $150 a month for six people.
What stays outside PagerDuty Professional
The per-user rate is rarely what decides the bill. What does is the list of things Professional leaves out. PagerDuty’s pricing page lists these as add-ons, and its separate pricing pages show where they start:
- AIOps (alert grouping, suppression, thresholds and paused notifications): from $799 a month, or $699 a month billed yearly. It’s priced by the number of events you send. (AIOps pricing)
- PagerDuty Advance (the generative AI features): from $415 a month, on a yearly plan only. (AIOps pricing)
- Status Pages: Professional includes one external page with 250 subscribers. The add-on starts at $89 per 1,000 subscribers a month. (Status Pages pricing)
- Runbook Automation (automated diagnostics and fixes during an incident): $125 per user a month plus a platform fee. (Automation pricing)
- Live Call Routing (a phone number that rings whoever is on-call): no published price.
These add up quickly. A 25-person team on Professional pays $625 a month. Adding AIOps at its starting price takes that to about $1,424, which is more than double. The yearly platform plans include most of these, with limits on events and AI actions.
One more cost sits outside PagerDuty altogether. It has no built-in heartbeat check, so a cron-monitoring tool often joins the stack (more on that below).
For comparison, Atlassian’s own path is JSM. It’s priced per agent and includes unlimited SMS and voice alerts from the Standard plan. Our OpsGenie to JSM guide covers that route and its costs.
What PagerDuty’s OpsGenie migration offer includes
PagerDuty runs two offers for OpsGenie customers, and the fine print matters more than the headline.
The main one is the Summer 2026 promotional offer. It’s open to current OpsGenie customers and limited to “the first fifty (50) qualifying customers”. It includes “up to eighty (80) Expert Service Hours over the first 3 weeks of the plan” for environments of up to 250 active users. The offer runs until June 1, 2028, and PagerDuty notes that it “may revoke or modify this offer at any time”.
The offer requires the “Operations Cloud Core” plan. That plan name doesn’t appear on PagerDuty’s current pricing page. PagerDuty’s two-page Replacing Opsgenie guide describes the deal as a bundle that “covers your team with a base amount of users”, with new users added “at $0 extra cost”. It doesn’t say what the bundle costs or how many users the base includes.
There’s also a smaller community offer. It covers free migration support “for implementations under 5 hours” for organisations of up to 100 users. That includes users and teams, up to 3 monitoring tools, up to 25 services, and escalation policies and schedules.
Both offers can save real setup time. Since the key numbers come from a sales call, these are the questions worth getting answered in writing:
- Which plan qualifies, and how many of the 50 spots are still open?
- What does the bundle cost, and how many users does the base include?
- What happens to the seat count and the price at renewal?
- How many SMS and phone alerts are included for responders outside the US?
Head-to-head on what OpsGenie users rely on
On-call scheduling and overrides
Both tools handle layered rotations, time zones and overrides. OpsGenie shows rotations, overrides and the final schedule on one screen. PagerDuty covers the same ground, and its free plan stops at one schedule.
When I tested PagerDuty, I couldn’t clone a schedule or see a history of past overrides. Users on r/devops named a few OpsGenie pains too: overrides around holidays, and new people breaking an existing rotation. These are worth testing in any tool before you move.
Verdict: a tie on the core job. Test overrides and rotation changes with your own team before you commit.
Alerting, phone and SMS
PagerDuty Professional includes SMS and phone alerts, and the free plan stops at 100 a month. The pricing page doesn’t list an allowance for responders outside the US, so it’s one to ask about.
In my tests, each responder set their own notification rules. A team lead couldn’t choose phone or SMS for the whole team. That’s fine for small teams, but it takes more chasing when someone’s settings are wrong.
Verdict: PagerDuty matches OpsGenie Standard here. Teams with responders outside the US should get the allowance confirmed.
Alert noise and your monitoring stack
How many alerts your monitoring tools send decides how much of PagerDuty you’ll use. An uptime monitor and one cloud provider might send a few hundred alerts a month. A stack with Datadog, Splunk, CloudWatch and others can send thousands of events. That second case is what PagerDuty’s two strongest features are built for. Event Orchestration is its rules engine for routing and filtering alerts. AIOps groups and suppresses noisy alerts on top of that.
With a few hundred alerts a month, AIOps has little to group. OpsGenie Essentials allowed just one routing rule, which is enough when every alert goes to one escalation policy. With thousands of events, grouping and suppression earn their price. That’s where PagerDuty is hard to beat.
Verdict: PagerDuty wins for high alert volume from many tools. For a small stack, the extra depth mostly goes unused.
Heartbeats
Heartbeats are an easy gap to miss when you move. In OpsGenie, a backup job or cron task pings a URL. A missed ping alerts whoever is on-call. PagerDuty has no built-in check-in URL. Its own heartbeat guide builds one from Event Orchestration cache variables, suspended alerts and a resolve webhook, under its AIOps pages.
The simpler route is a cron-monitoring service like Healthchecks.io or Cronitor that sends missed runs to PagerDuty. In fairness, Spike and most standalone on-call tools work this way too.
Verdict: OpsGenie had the easier setup. Plan for a cron-monitoring tool whichever way you go.
Status pages
OpsGenie’s status pages were internal views of service health. Teams that ran a public page for customers bought Statuspage.io separately. That subscription isn’t part of the shutdown, so it keeps billing after OpsGenie closes. PagerDuty Professional includes one external status page with 250 subscribers, and private pages come with the platform plans.
Verdict: PagerDuty can replace a small Statuspage.io setup. A larger audience needs the add-on, from $89 per 1,000 subscribers a month.
Mobile app
OpsGenie’s mobile app stops working at shutdown, and Atlassian tells users to switch to the Jira mobile app. Users on r/devops who tried both rate PagerDuty’s app higher.
Verdict: PagerDuty wins clearly here.
Integrations
PagerDuty lists more than 750 integrations against OpsGenie’s 200 or so. The count matters less than the five or six tools your on-call actually depends on. Checking that short list against the plan you’d buy says more than the total.
Verdict: PagerDuty wins on breadth. It only matters if one of your tools is missing elsewhere.
Reliability and support
An alerting tool has one job that can’t fail. OpsGenie was caught in Atlassian’s April 2022 outage, when 775 customers lost access for up to 14 days. The Pragmatic Engineer reported that OpsGenie was among the products affected. After April 5, 2027, there’s no support at all.
PagerDuty includes standard email and chat support from Professional. Its Gold Services support level is a paid add-on. Support quality is where some long-time users push back. A user on r/devops who ran PagerDuty for about ten years wrote this about three years ago:
The main thing I hate about PD is their support. They used to have live chat support which was great. These days I have to send in an email and then wait a week or two for a response.
Verdict: PagerDuty, since OpsGenie support ends with the shutdown. It’s worth asking what support level comes with your plan.
What changes for your team when you move to PagerDuty
The two tools use different words for similar ideas, and some OpsGenie features need a new home. This map helps when you plan the move:
| In OpsGenie | In PagerDuty |
|---|---|
| Team | Team, with a service for each thing you alert on |
| Routing rule | Event Orchestration rules |
| Escalation policy | Escalation policy |
| Schedule | Schedule |
| Heartbeat | Event Orchestration recipe, or a cron-monitoring tool |
| Integration (API key) | Integration key on a service |
| Incoming call number | Live Call Routing (add-on on Professional) |
| Mobile app | PagerDuty app for every responder |
Users, schedules and escalation policies move with help from PagerDuty’s team or your own scripts. Integrations need new keys in each monitoring tool. Scripts and Terraform built on OpsGenie’s API need rewriting, and notification rules get set up again for each person.
The people side takes time too. Every responder needs the new app and a test alert before their first shift. PagerDuty’s community FAQ says a move “usually includes 2–3 days to migrate, validate, and optimize”. Running both tools side by side for a few weeks often helps, because it shows gaps before anyone relies on the new setup.
Which fits your team: team size and monitoring stack
Team size and monitoring stack decide most of the answer. This table maps common setups to the place to look first:
| If your team… | Look first at |
|---|---|
| Has 10 to 25 people, one to three rotations, an uptime monitor and one cloud provider | A standalone on-call tool. PagerDuty may be more than you need |
| Has 25 to 100 people, several services, a few monitoring tools and phone alerts at night | PagerDuty Professional and a standalone tool, compared on total cost rather than per-user price |
| Sends thousands of events a month from many tools, or needs ServiceNow, Salesforce or incident roles | PagerDuty |
| Already runs IT service management in Jira | JSM (see our OpsGenie to JSM guide) |
Choose PagerDuty if:
- Many monitoring tools send you thousands of alerts a month, and machine-learning grouping across them matters.
- Your incident process uses roles, workflows and ServiceNow or Salesforce.
- You have the budget for the platform plans or the add-ons you’ll need.
PagerDuty is probably not the right fit if:
- You used OpsGenie mainly for schedules, escalations and phone alerts.
- Your stack is small, so AIOps would cost more than the noise it removes.
- You want one bill that covers status pages and call routing.
What people who used both say
Reddit threads that compare the two tools keep landing on the same trade-off. These comments come from r/devops, about three years ago, before the shutdown was announced.
One user summed up the common view:
OpsGenie is cheaper, in every other way PagerDuty is leagues ahead.
Another praised PagerDuty’s app and feel:
PD has much better phone app, a lot better user experience, and overall feel.
A third had used both at a startup and saw little reason to pay more:
To my knowledge, PD doesn’t have anything that would make me say its worth the higher price.
Several people in the thread chose OpsGenie because it was cheaper. With OpsGenie closing, that price question comes back. It’s worth answering on total cost rather than habit.
If neither fits: Try Spike
PagerDuty is the right call for large teams with many monitoring tools and a formal incident process. JSM suits teams whose incidents already live in Jira. Teams in between used OpsGenie for a few rotations, escalations and phone alerts. For them, we compare the wider field in two guides, one for startups and one for enterprise teams, plus a list of PagerDuty alternatives.
Spike covers on-call schedules, escalations, unlimited phone and SMS alerts, a status page and call routing on one bill. Here’s how it compares with PagerDuty Professional on the points above:
| PagerDuty Professional | Spike Business | |
|---|---|---|
| Price | $25 per user per month, plus add-ons | $14 per user per month |
| Status page | One external page, 250 subscribers | Public status page included; private pages on Business |
| Live call routing | Add-on | Included on paid plans |
| Heartbeats | Event Orchestration recipe or a cron-monitoring tool | Through integrations like Healthchecks.io and Cronitor |
| Migration help | Offer for the first 50 customers | Our team imports your schedules and escalation policies; you get MCP, API and Terraform too |
Sources: PagerDuty pricing, Spike pricing.
HitPath moved from OpsGenie to Spike and ran both tools side by side first. CTO Mark Brody described the move:
The migration was easy. Most of the integrations were webhooks, and I ran different escalation policies depending on the different roles we were monitoring. It was a two or three-stage approach, so it wasn’t like flipping the switch on everything at once. We ran OpsGenie and Spike together for about a month, and everything lined up, just to make sure nothing was falling through the cracks. Once we were confident, we canceled our OpsGenie service and opened the gates on Spike.
You can run both tools for as long as you need. OpsGenie users also get 20% off their first year on an annual plan.
Why you can trust this comparison
We built Spike, and we tried our best to give you a fair comparison. I set up PagerDuty myself and tested its schedules, overrides and notification rules. Those notes are in the scheduling and alerting sections above. Prices and limits come from each vendor’s own pages, checked on November 2, 2026. Where another comparison quoted a figure we couldn’t find on a vendor page, we left it out.
These are the sources behind the prices and limits:
- PagerDuty pricing, with add-on prices for AIOps and Advance, Status Pages and Runbook Automation
- PagerDuty OpsGenie migration offer
- PagerDuty community migration offer
- PagerDuty heartbeat guide
- OpsGenie pricing and what happens when OpsGenie is turned off
- Jira Service Management pricing
FAQ
Is PagerDuty better than OpsGenie?
It depends on your team. PagerDuty does more, with 750+ integrations, Event Orchestration, AIOps and a well-liked mobile app. OpsGenie was simpler and cheaper, with built-in heartbeats. Since OpsGenie shuts down on April 5, 2027, the real question is whether your team needs PagerDuty’s depth at its price.
Why is OpsGenie shutting down?
Atlassian is folding OpsGenie’s alerting and on-call features into Jira Service Management. In its email to customers, it said the goal is “to simplify collaboration between the development and IT operations teams”. Our OpsGenie end-of-life guide covers the dates and what stops working.
Does OpsGenie still exist?
Yes. Existing customers can use it until April 5, 2027. Nobody new has been able to buy it since June 4, 2025. Existing customers can add seats and renew, as long as the new term ends before the shutdown.
What is OpsGenie being replaced with?
Atlassian’s lasting home for OpsGenie’s features is Jira Service Management. It also listed Compass as an option, but Compass is being phased out. Standalone on-call tools are the other common choice.
Who are PagerDuty’s main competitors?
The main names are Jira Service Management, incident.io, Rootly, Splunk On-Call, Grafana Cloud IRM, Squadcast (now part of SolarWinds), and standalone tools like Spike. Our list of PagerDuty alternatives compares them.
Is PagerDuty cheaper than JSM?
It depends on the plan you need. JSM Standard includes unlimited SMS and voice alerts but no status page, and heartbeats need Premium. PagerDuty Professional includes a small status page but charges extra for noise reduction and call routing. Comparing the total for your team size gives a fairer answer than the per-user rate.
