PagerDuty plans and prices in 2026
PagerDuty now shows two families on its pricing page. Incident Management (Free and Professional) is priced per user. The PD Reliability Platform is priced per year, with seats, events and AI actions included and more sold as credit packs.
| Plan | Price | Seats and events | Main inclusions |
|---|---|---|---|
| Free | 0 USD | Up to 5 users | 1 on-call schedule, 1 escalation policy, 100 SMS or phone notifications a month |
| Professional | 21 USD per user per month annual, 25 USD monthly | Per user | Unlimited schedules and escalation, Slack and Teams app, post-incident reviews, external status page up to 250 subscribers |
| Platform Starter | 2,800 USD per year | 10 seats, 5,000 events | AIOps, PagerDuty Advance AI, private and external status pages, ServiceNow and advanced ITSM integrations, round robin scheduling, 1 live call routing line |
| Platform Essential | 12,000 USD per year | 20 seats, 40,000 events | Everything in Starter, 2 live call routing lines |
| Platform Plus | 48,000 USD per year | 50 seats, 150,000 events | Workflows with conditionals, loops and delays, incident tasks, bi-directional ServiceNow field sync, 3 live call routing lines |
| Platform Ultimate | Custom quote | 500 seats, 2,000,000 events | Enterprise scale |
Source: PagerDuty's public pricing page, checked in October 2026. Two rules matter for budgeting. Platform seats include stakeholder licenses, so people who only read count toward the 10, 20 or 50. Seats are billed at the highest number used during the previous month, so a busy month raises the bill. PagerDuty changes packaging from time to time, so confirm the numbers on their site before you sign.
What PagerDuty charges extra for
On Professional, the add-on list is where most budgets drift. PagerDuty sells these separately and lists them without prices, so you get the number from sales:
- Status Pages: anything beyond the external page with 250 subscribers, including private pages.
- AIOps: alert grouping, suppression, triage and noise reduction.
- PagerDuty Advance: the generative AI assistant and AI-written status updates.
- Runbook Automation: automated diagnostics and remediation.
- Live Call Routing: a phone number that routes callers to the on-call engineer.
On the platform plans, AIOps, Advance and status pages are included. What you buy extra there is capacity: credit packs for more seats, events or AI actions, also without a public price. Ask for the credit pack price in writing before you sign, because it decides what month 13 costs if your team grows.
How much does PagerDuty cost for a team of 5, 15 and 40?
The table uses list prices with annual billing. Professional counts responders only and leaves out the quoted add-ons. Platform rows show the smallest plan whose seat bundle covers the team without credit packs, and the seats include anyone who only reads.
| Team | Professional, per year | Smallest platform plan that fits, per year | Platform cost per seat per month |
|---|---|---|---|
| 5 | 1,260 USD | Starter, 2,800 USD | about 47 USD (10 seats paid, 5 used) |
| 15 | 3,780 USD | Essential, 12,000 USD | about 67 USD (20 seats paid, 15 used) |
| 40 | 10,080 USD | Plus, 48,000 USD | 100 USD (50 seats paid, 40 used) |
The Professional math is seats times 21 USD times 12, so 15 responders cost 15 x 21 x 12 = 3,780 USD a year before add-ons. The platform math is the fee divided by the seats you actually fill. A 10 person team that fills Starter pays about 23 USD a seat; an 11th person either needs a credit pack or pushes you to Essential. Larger teams often negotiate, so treat list price as the ceiling for seats and the floor for the total.
Is the PagerDuty Free plan enough?
The Free plan works for a side project or a team of up to 5 with one schedule and one escalation policy. It stops being enough the moment you need a second rotation or more than 100 SMS and phone notifications a month. Production teams usually hit one of those limits early.
Why the PagerDuty invoice ends up higher than the seat price
Three patterns show up in almost every renewal conversation.
- People who only read. Support, account management and leadership want to follow incidents. On Professional they need stakeholder licenses, and on the platform plans they use up seats in the bundle.
- Features split across tiers. Private status pages, ServiceNow and AIOps start on the platform plans, and workflows with conditionals, loops and incident tasks start on Plus, so a team that needs one of them moves from a per-user price to a yearly platform fee.
- Separate tools around the pager. Many teams still add a Slack incident bot, a status page product or a postmortem tool next to PagerDuty, each with its own bill.
None of this makes PagerDuty a bad choice. It is the most established tool in the category, with a very large integration catalog. It does mean the per-user price alone is not the number to compare.
PagerDuty pricing vs IncidentBot pricing
Here is the honest comparison, list price against list price, annual billing.
| PagerDuty | IncidentBot | |
|---|---|---|
| Entry paid plan | Professional, 21 USD per user | Starter, 24 USD per user |
| Next step | Platform Starter, 2,800 USD a year for 10 seats | Team, 49 USD per user |
| Larger teams | Essential 12,000 USD for 20 seats, Plus 48,000 USD for 50 | Business, 99 USD per user, Enterprise 199 USD |
| Read-only stakeholders | Add-on on Professional, count as platform seats | Included in every plan, never billed |
| Status page | External page up to 250 subscribers on Professional, private pages on platform plans | 1 page on Starter, 3 public or private on Team, unlimited on Business |
| SMS and voice paging | Included on paid plans | Through your own Twilio account: 100 per user a month on Starter, no limit on Team and above |
| Incident run in Slack | Slack app on every plan, 1 incident workflow on Professional, unlimited on platform plans | /incident channels, roles and timeline on every plan |
| Postmortem drafts | Post-incident reviews on Professional and up | Built from the timeline on Team and above, action items to Jira and Linear |
Where PagerDuty is cheaper: Professional costs 3 USD less per seat than our Starter, and a team of exactly 10 that fills Platform Starter pays about 23 USD a seat with AIOps and private status pages included, less than half of our Team plan. Where IncidentBot comes out ahead: teams between 11 and 50 people, because there is no jump to a 12,000 or 48,000 USD platform fee, readers never use a seat, and a status page and Slack incident roles come with the base price. Our on call management software pricing page has a seat calculator for your exact numbers, and the PagerDuty vs Opsgenie comparison prices both for 10 and 40 responders.
Questions to answer before you sign a PagerDuty renewal
Put these in the email to your PagerDuty rep, and ask any other vendor on your shortlist the same questions.
- How many people are responders and how many only read? Price both groups.
- Which features on our must-have list sit on a platform plan or an add-on, and what does a credit pack for 10 more seats cost?
- What does noise reduction cost at our alert volume?
- Do we still need a separate status page or Slack incident tool on this plan?
- What does a two to three week parallel run with another tool look like, contractually?
If your monitoring stack is small and part of the paging bill comes from checks that only ask whether a site is up, a dedicated tool for uptime monitoring every 30 seconds can feed alerts straight into your on-call rotation and keep the incident platform for real incidents.
What switching costs in time
Schedules and escalation policies import from PagerDuty into IncidentBot, including rotation layers and overrides. You re-point integrations service by service and run both tools in parallel until the same person is paged at the same step. Most teams do it in two to three weeks. The step by step plan is on the PagerDuty alternative page, and teams leaving VictorOps can follow the Splunk On-Call alternative migration plan. To see paging, a Slack incident channel, a status page draft and a postmortem skeleton before you commit, run the incident simulator.