PagerDuty plans and prices in 2026
PagerDuty publishes four incident management plans. Prices are per user, and a user in PagerDuty terms is anyone with a full license, which normally means anyone who can be on call or act on an incident.
| Plan | Annual billing | Monthly billing | Main limits and inclusions |
|---|---|---|---|
| Free | 0 USD | 0 USD | Up to 5 users, 1 on-call schedule, 1 escalation policy, 100 SMS and phone notifications a month, no chat integration |
| Professional | 21 USD per user per month | 25 USD per user per month | Multiple schedules and policies, basic Slack and Microsoft Teams, external status page up to 250 subscribers, 1,000 one-time AI actions |
| Business | 41 USD per user per month | 49 USD per user per month | Custom fields, up to 3 custom incident types, advanced admin, status page up to 500 subscribers, 5,000 one-time AI actions |
| Enterprise | Custom quote | Custom quote | Full chat experience, incident workflows, ServiceNow sync, status page up to 1,000 subscribers, stakeholder licenses and live call routing included |
Source: PagerDuty's public pricing page, checked in September 2026. PagerDuty changes packaging from time to time, so confirm the numbers on their site before you sign.
What PagerDuty charges extra for
The add-on list is where most budgets drift. On Professional and Business, PagerDuty sells these separately, and its pricing page lists them without prices, so you get the number from sales:
- Stakeholder licenses: read-only access for support leads, account managers and executives who follow incidents but do not respond. Included on Enterprise.
- Status Pages: extra capacity and premium status page features beyond the subscriber limit of your plan.
- AIOps: event correlation and noise reduction.
- PagerDuty Advance: more AI actions than the one-time allowance in your plan.
- Live Call Routing: a phone number that routes callers to the on-call engineer. Included on Enterprise.
Two of these matter to almost every team. Stakeholder access decides whether you pay for the people who only read, and noise reduction decides whether your on-call engineers are woken by duplicate alerts. Ask for both prices in writing before you compare vendors.
How much does PagerDuty cost for a team of 5, 15 and 40?
The table below uses list prices with annual billing and counts only responders. Add-ons are left out because they are quoted, which is exactly why you should ask for them.
| Responders | Professional, per year | Business, per year |
|---|---|---|
| 5 | 1,260 USD | 2,460 USD |
| 15 | 3,780 USD | 7,380 USD |
| 40 | 10,080 USD | 19,680 USD |
The math is seats times the monthly rate times 12. A 15 person team on Business pays 15 x 41 x 12 = 7,380 USD a year before any add-on. Larger teams often negotiate a discount on annual contracts, so treat the 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, Slack or Teams integration, 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 and Business they need stakeholder licenses or full seats.
- Features split across tiers. Custom incident types, workflows and the full chat experience sit on higher tiers, so a team that needs one Enterprise feature prices the whole team at Enterprise.
- 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, per responder per month.
| PagerDuty | IncidentBot | |
|---|---|---|
| Entry paid plan | Professional, 21 USD | Starter, 24 USD |
| Mid plan | Business, 41 USD | Team, 49 USD |
| Upper plan | Enterprise, custom | Business, 99 USD, Enterprise custom |
| Read-only stakeholders | Add-on below Enterprise | Included in every plan, never billed |
| Status page | Included with subscriber limits, premium features as an add-on | 1 page on Starter, 3 with custom domain on Team, unlimited on Business |
| SMS and voice paging | Plan allowances | 100 per user on Starter, unlimited (fair use) on Team and above |
| Incident run in Slack | Basic on Professional and Business, full on Enterprise | /incident channels, roles and timeline from Starter |
| Postmortem drafts | Varies by plan | 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 its Business tier costs 8 USD less per seat than our Team tier on list price. Where IncidentBot comes out ahead: stakeholders are free, SMS and voice paging is unlimited on Team, and coordination, status page and postmortems are in the same seat price, so there is no second or third tool to buy. For a team with many readers and few responders, that difference is usually larger than the seat price gap. Our on call management software pricing page has a seat calculator for your exact numbers.
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 higher tier or an add-on?
- 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.