PagerDuty Pricing 2026: Plans, Tiers, and Total Cost
Oct 22, 202615 min read
You'll settle most of what you pay in a sales conversation rather than on the page, because PagerDuty publishes a per-user price on few plans. The Reliability Platform tiers lead with a platform fee instead.
PagerDuty Pricing in October 2026, Plan by Plan
What PagerDuty is and what the price buys
PagerDuty is an incident-response platform: it takes an alert from your monitoring, decides who is on call, and keeps paging until someone acknowledges. The price buys that routing and escalation, plus whatever each tier layers on top.
Per-user plans scale with headcount, while platform-fee plans scale with seats and event volume, so they punish different team shapes. That is the whole commercial trade-off.
The plan table with limits
Treat every "contact sales" cell as a quote you must collect before comparing plans, because some plans still carry no published figures. The table below is drawn from PagerDuty's pricing page as checked on 22 October 2026, and lists every current plan.
Per-user plans scale with headcount, while platform-fee plans scale with seats and event volume, so they punish different team shapes. That is the whole commercial trade-off.
| Plan | Price per user (annual vs monthly) | Inclusions | Usage limits |
|---|---|---|---|
| Free | $0 per year | 5 users, 1 on-call schedule, 1 escalation policy | 100/month SMS/phone notifications |
| Professional | $21 per user / month billed annually; $25 per user / month billed monthly | Contact sales | Contact sales |
| Business | Contact sales | Contact sales | Contact sales |
| Enterprise | Contact sales | Contact sales | Contact sales |
| Reliability Platform Starter | $2,800 platform fee per year; monthly: contact sales | 10 seats | 5,000 Signal Intelligence Events |
| Reliability Platform Essential | $12,000 platform fee per year | 20 seats | 40,000 Signal Intelligence Events |
| Reliability Platform Plus | $48,000 per year | 50 seats | 150,000 Signal Intelligence Events |
Prices and plan limits checked against pagerduty.com on October 22, 2026.
If your rota is larger than 10, you hit Starter's seat ceiling quickly, and every extra responder pushes you toward a higher tier.
The 5,000 Signal Intelligence Events cap matters for the same reason: a noisy monitoring setup can use it up, so measure your alert volume before assuming the entry price holds.
Add-ons priced outside the plans
If you attach add-ons, the table understates your bill, because some capabilities are sold separately from the plan. Ask for each add-on as a written line item, with its usage limit and overage terms, before signing.
If you route alerts into wider workflows, for example through Activepieces, which Alan and FundingSocieties run in production, confirm which of those integrations count against event limits. The next section shows how to match a plan to your actual paging pattern.
If you are running this arithmetic for your own team, see what the same workload costs on Activepieces.
Renewal day cost shock
Matching plan to paging pattern matters because of mornings like this one. At 09:40 on renewal day, an illustrative ten-person team opens its PagerDuty invoice and finds it's $3,360 over the budget sheet.
Ten seats on Professional, billed annually, at $21 per user per month: that was the sheet. It comes to $2,520 a year.
It was a clean number, and it counted everyone on the team as the same kind of user, so the plan was bought on headcount rather than on who actually gets paged.
On Business, billed monthly, the invoice came back at $5,880 a year. Two choices drove it: the higher tier, and the monthly billing that carries a premium over the annual rate.
Nobody in the meeting had questioned either, because the list price on the pricing page looked close enough to the sheet. It wasn't close enough once both choices stacked.
Annual versus monthly PagerDuty billing cost
Annual billing is cheaper at both tiers, and the tier jump costs more than the billing choice. The chart shows the yearly cost of ten seats across five options.
Billed monthly, Professional costs $480 a year more ($3,000 against $2,520), and Business costs $960 more ($5,880 against $4,920). Moving from Professional to Business on annual billing adds $2,400.
Add those two choices together and you get the team's $3,360 miss. Starter, at $2,800, sits between the two Professional bars, so it's cheaper than monthly Professional but not annual.
Real bills spread much wider than this example. Vendr, which tracks negotiated software deals, reports a median PagerDuty contract of $40,000 a year.
A ten-person team at $2,520 is a small fraction of that, so tie your budget to your own seat count and paging pattern, not to a typical contract.
The gap here is only list price. Add-ons and usage limits sit on top of it, and they're where the next surprise comes from.
Hidden Costs and Limits Behind the Higher Invoice
The invoice grows from five places, and only the first is a seat price. The set below is the order most teams meet them, and each one scales with something other than headcount.
- Who counts as a paid seat: anyone PagerDuty can page, not everyone who logs in.
- Features that PagerDuty gates to higher tiers, which you discover only after buying the lower one.
- AIOps from $799/month, a fixed floor you pay before noise reduction has saved anything.
- Runbook Automation at $125/user/month plus a fee, so you pay per person and again on top.
- Caps on events and AI actions, which a noisy month can hit.
The sections below take them in the order they tend to hurt.
Seats for people who rarely get paged
In a 100-engineer organisation, Flashduty's PagerDuty cost breakdown assumes 15 responders and 85 stakeholders. Giving all 100 a Business seat costs $49,200 a year, roughly $492 per head, so 85 of those seats pay for people who only need to watch.
Move those 85 to stakeholder licences and Business drops to $10,980 a year, a saving of $38,220.
Flashduty's own Pro plan, an alternative on-call product, comes to $5,220 a year. That's about half of even the trimmed PagerDuty bill, so the comparison belongs in any renewal conversation.
Don't assume a plan that covers paging also covers the routing, reporting or automation you expected. The cost shows up as a tier upgrade for the whole seat count, not for the one feature you wanted.
List the features you depend on before choosing a tier, and price the tier that includes them.
PagerDuty add-ons and usage limits
At $799/month, AIOps is hard to justify for a team whose alert volume is already manageable. Runbook Automation at $125/user/month plus a fee is worth it only if those users run automation regularly.
You meet event and AI-action caps in a busy month, not at signing, which makes them the least visible item. Ask what happens at the limit before you rely on the feature.
If your responder count is 15 today but you bought for 100, the gap is yours until renewal, because annual terms turn a seat estimate into a fixed obligation.
Before signing, ask whether seats can be reduced mid-term, and size the first contract to the people PagerDuty actually pages.
Worth checking against a plan that does not meter every step: one credit covers a whole run on Activepieces.
PagerDuty Against Its Closest Alternatives on Price
Sizing the contract to the people who get paged only works if the tool is the right one. PagerDuty's closest rivals differ less in headline price than in what they gate behind higher tiers.
Comparison table: price, free tier, features
Read the last column first, because that's where your bill grows after signing. The table below, checked in October 2026, shows how each vendor prices entry, whether a free tier exists, what on-call basics come included and what is held back.
| Tool | Entry price | Free tier | Included on-call features | Gated items |
|---|---|---|---|---|
| PagerDuty | Per user, per month, rising by plan | Limited plan for small teams | Schedules, escalation policies, mobile alerting | Automation, AIOps and extra incident tooling sit in higher plans or add-ons |
| Opsgenie | Per user, but being retired | None worth planning around | Schedules, escalations, routing | Atlassian is steering customers to Jira Service Management, so a new commitment carries migration risk |
| Grafana IRM | $20 per user after the free users | Free for 3 users | Alert routing, schedules, incident management inside Grafana Cloud | Usage follows your Grafana Cloud plan |
| incident.io | Per user, with on-call priced apart from incident response | Basic free plan | Schedules, escalations, Slack-based response | On-call and advanced workflows need paid plans |
| Splunk On-Call | Per user, by edition | None confirmed | Routing, schedules, escalation | Fuller features sit in higher editions |
For a three-person team, Grafana IRM costs nothing, which makes it the obvious starting comparison. Opsgenie's status is the one to resolve before anything else, since a cheap seat on a retiring product is a cost deferred, not saved.
When a cheaper tool is the right call
When your alerting is simple, a cheaper tool is the right call: a small rota, a few services, and no need for automated remediation or deep analytics.
If you already run Grafana, its IRM product keeps alerts, dashboards and on-call in one place. If your incidents live in Slack, incident.io fits that habit. Splunk On-Call suits teams already invested in Splunk. Pay PagerDuty's premium only for something you'll use weekly.
You rebuild schedules and escalation policies, re-point every integration that sends alerts, and retrain responders, while running both tools in parallel so no page is missed.
That is why switching costs are mostly labour, not licences. Budget that overlap and the engineering hours before you call the alternative cheaper.
Fix Noisy Paging Costs with Activepieces
To cut paging cost, keep low-urgency alerts away from PagerDuty with Activepieces, whose core is MIT-licensed. Only alerts above a severity threshold page a paid responder, and everyone else reads Slack or a ticket queue.
Alert severity rules to cut PagerDuty seats
Start with the commercial point: every alert that reaches PagerDuty is one more reason to keep someone on a full seat.
If a monitoring tool sends everything straight in, you end up sizing the plan you buy to the noise rather than to the pages that matter.
Putting a severity gate in front changes what you're buying for.
State the rule simply: high severity goes to PagerDuty and pages a responder. Everything below the line goes somewhere else.
Write the threshold down and get the team to agree it. Then audit seats against it: anyone the rule wouldn't page is a candidate for a cheaper role or no paid seat at all.
Routing low-urgency alerts without a page
High-severity alerts go to PagerDuty and a paged responder; low-severity alerts go through an Activepieces connector, one of 744 integrations in its open source repo, to Slack or a ticket.
Take from it that the paid path is the short one, and the volume sits on the other branch.
Activepieces sits on that second branch and prices differently from a pager seat: flows are unlimited on every plan, including free, which comes with 1,000 credits a month and up to 5 users.
Credits meter AI usage, so a flow with no AI step doesn't use them. Per-seat pricing rations automation; consumption pricing doesn't, which is why the low-urgency branch can carry the volume without adding a licence line per person.
Nobody wakes, and nothing counts against your PagerDuty usage.
Checking severity and choosing the branch can sit in that same Activepieces flow too, so the rule lives in one visible place rather than in several monitoring configs.
That also makes the trade-off plain. You're taking on a workflow to build and maintain in exchange for a smaller, better-matched PagerDuty plan.
Why PagerDuty escalation still matters
It doesn't replace on-call scheduling, escalation policies or acknowledgement tracking. Those are what you pay PagerDuty for, and a Slack post that nobody answers doesn't escalate to a second person. If an alert is genuinely urgent, it belongs on the paged path.
So the gate has to be conservative: when you're unsure, page. A threshold set too low turns a cost saving into a missed incident, and that's the more expensive surprise.
Renewal planning checklist
Set the thresholds from your own paging data rather than a guess, by working through six steps in order before anyone signs the renewal.
The list below is the sequence. Each step feeds the next, so skipping one means the quote you receive is priced on assumptions.
- Tag every user as responder, stakeholder or inactive.
- Compare those counts to the plan table.
- Check your usage against the plan's limits.
- Get a written quote that itemises the add-ons.
- Set a 90-day review.
- Price one alternative.
You must finish the first three steps, which are your homework, before you can start the last three, which are what you do with the vendor.
Audit seats against actual pages
Export the user list and sort each person by whether they were paged, only needed to see incident status, or did neither. Responders need a full seat. Stakeholders may not, and inactive accounts shouldn't be billed at all.
Then lay those counts against the plan table. If most of your headcount is stakeholders, the question is whether a cheaper tier covers them, not which plan has the longest feature list.
Finally, check alert volume, notification channels and integrations against each plan's limits. Hitting a cap mid-year is how a plan that looked cheaper becomes the expensive one.
Get your PagerDuty quote in writing
Ask for the full price, with every add-on you need named line by line. A verbal "that is included" is not a commitment you can hold anyone to at the next renewal.
Confirm what happens when you exceed a usage limit, whether you're throttled or billed overage, because those two outcomes carry very different risks.
Pricing one alternative at this stage is leverage as much as diligence. Even if you never switch, a comparable quote shows you which line items are negotiable.
Put a review on the calendar 90 days out, with an owner, so it doesn't slip. Rerun the seat tags then, since rotations, new hires and reorganisations change who gets paged.
Catching drift early lets you adjust the plan at the next opportunity, not discover it on the invoice.
Frequently asked questions
Does PagerDuty have a free plan?
Yes, PagerDuty has offered a free tier for very small teams, but it's limited in users and features. It suits a trial or a tiny rotation.
Once you need things like richer escalation or more integrations, you move to a paid plan. Check the current plan page for what the free tier includes before you build a workflow on it.
Is PagerDuty cheaper billed annually than monthly?
Generally yes. PagerDuty's public pricing lists a lower per-user rate when you commit annually and a higher one month to month.
The trade-off is flexibility: an annual contract locks in your seat count, so if you're still working out who is on call, pay monthly briefly, then commit once the rotation settles.
Do stakeholders need a paid PagerDuty license?
Stakeholders need a license of some kind if they're to be added to incidents, but not a full seat. PagerDuty sells stakeholder licenses separately from full users, and they cost far less.
Give full seats to people who get paged and stakeholder licenses to everyone who only needs visibility.
Can I negotiate PagerDuty pricing at renewal?
Often, yes, particularly on larger contracts, though the list price is rarely where the room is. Your leverage is seat count, contract length and a competing quote.
Arrive with an audit showing how many people were actually paged; that is the strongest move, because you can renew fewer full seats and more stakeholder licenses rather than haggling over the per-seat rate.
Is PagerDuty worth it for a team under ten people?
It can be, but only if the plan matches how you're alerted. A small team where everyone shares the pager may get what it needs from a lower tier or the free one.
Paying for a higher plan with add-ons you won't use is the usual mistake. If the on-call group is only a few people, buy for them and treat the rest as stakeholders.
Related reading
Running the numbers
See what the same workload costs here.
Free forever plan, and every paid plan self-hosts at no extra cost.
See pricing Talk to sales
