What Splunk On-Call and PagerDuty charge in 2026
| Item | Splunk On-Call | PagerDuty |
|---|---|---|
| Free plan | None, free trial only | Free for up to 5 users, 1 schedule and 1 escalation policy, 100 SMS or phone notifications a month |
| Entry paid price | 5 USD per user a month, annual, up to 10 seats | Professional 21 USD per user a month annual, 25 USD monthly |
| Price above 10 users | Quote; directories list Starter 10, Growth 35 and Enterprise 45 USD per user | 21 USD Professional, or platform plans from 2,800 USD a year for 10 seats |
| SMS and voice | Included in on-call notifications | Included on Professional with fair use |
| Mobile app | Native iOS and Android | Native iOS and Android |
| Status page | Not part of On-Call | Listed on Professional with 250 subscribers in the comparison table, while the plan card lists status pages as an add-on |
| ServiceNow integration | Through Splunk ITSM integrations | Not on Professional; on the PD Reliability Platform plans |
| Owner | Cisco, since its purchase of Splunk in March 2024 | PagerDuty, Inc. |
PagerDuty figures come from the PagerDuty pricing page, checked on November 18, 2026. Splunk On-Call figures come from the Splunk On-Call product page and the Splunk pricing page as checked in October 2026; the plan names above 10 seats are third-party listings, not prices Splunk confirms. Our full single-vendor breakdowns are Splunk On-Call pricing and PagerDuty pricing per user.
Splunk On-Call vs PagerDuty cost for 5, 15 and 40 responders
Monthly cost, every responder holds a seat. Splunk rows above 10 seats use directory list prices, which are a ceiling to negotiate from, not a quote.
| Setup | 5 responders | 15 responders | 40 responders |
|---|---|---|---|
| PagerDuty Free (1 schedule, 1 escalation policy) | 0 USD | Not available | Not available |
| Splunk On-Call published price (5 USD, up to 10 seats) | 25 USD | Quote only | Quote only |
| Splunk On-Call, directory Starter at 10 USD | 50 USD | 150 USD | 400 USD |
| Splunk On-Call, directory Growth at 35 USD | 175 USD | 525 USD | 1,400 USD |
| PagerDuty Professional, annual (21 USD) | 105 USD | 315 USD | 840 USD |
| PagerDuty Professional, monthly (25 USD) | 125 USD | 375 USD | 1,000 USD |
| IncidentBot Starter (24 USD annual, 1 public status page) | 120 USD | 360 USD | 960 USD |
| IncidentBot Team (49 USD annual, 3 status pages, SMS and voice through your own Twilio account) | 245 USD | 735 USD | 1,960 USD |
Three things stand out. At 5 responders Splunk On-Call at 25 USD a month is hard to beat, unless one schedule on PagerDuty Free is enough. At 15 responders the answer depends entirely on which Splunk tier your quote lands on: Starter would be the cheapest line in the table, Growth would cost about 210 USD a month more than PagerDuty Professional. At 40 responders PagerDuty Professional has a printed price and Splunk does not, so finance can approve one without a sales cycle.
The seat 11 cliff, worked through
A platform team of 9 pays Splunk On-Call 45 USD a month at the published price. This quarter it adds three engineers to the rota. If those hires are still in the pipeline, an AI agent that runs first-round screening interviews can shorten the wait, but the pager bill changes the day they join the rotation.
With 12 seats the team leaves the published price. If the quote lands at the directory Growth level of 35 USD, the bill goes from 45 to 420 USD a month, more than nine times as much for a third more people. The same 12 people on PagerDuty Professional cost 252 USD a month annual. On IncidentBot Starter they cost 288 USD a month, with a public status page included, which on the Splunk path is a separate purchase (Atlassian Statuspage Startup is 99 USD a month). The lesson is not that Splunk is expensive; a team inside a larger Splunk or Cisco agreement may get a good seat price. The lesson is to get the 11th seat priced in writing before you sign at 10.
What each seat actually includes
Both tools cover the core of on-call: rotations, overrides, multi-step escalation, push, SMS and voice, and acknowledgement from a native app. The differences sit around the edges.
- Alert routing. Splunk On-Call uses a rules engine (formerly Transmogrifier) to add context, runbook links and routing keys to alerts. PagerDuty uses event orchestration, with the more advanced rules on its higher plans. Both are capable; moving rules from one to the other is the slowest part of any migration.
- Integrations. PagerDuty lists more than 750 integrations. Splunk lists more than 100 monitoring and ITSM integrations and fits best when alerts already flow through Splunk Observability Cloud or ITSI.
- Status page. Splunk On-Call has none, so teams add Statuspage or another tool. PagerDuty lists an external page on Professional, but its pricing page also shows status pages as an add-on; ask sales which one applies to you.
- Stakeholders. On both, people who only want updates can end up needing a license, depending on plan. Count them before you compare.
- Incident workflow. Neither seat at the entry level includes a Slack channel with roles, a shared timeline and a postmortem draft. PagerDuty sells those on its platform plans; Splunk does not position On-Call for it.
Which one fits which team
- Splunk On-Call wins for teams of 10 or fewer who need a pager and nothing else, and for teams whose alerts already live in Splunk and who rely on its rules engine. Inside a broader Splunk agreement, an itemized On-Call line is often priced well.
- PagerDuty wins for teams above 10 that want a printed price, the largest integration catalog, and a path to AIOps, ServiceNow sync and automation on the platform plans. Our PagerDuty alternative page covers the reasons teams leave it, mostly platform plan costs at renewal.
- A third tool wins when the team runs incidents in Slack, customers need a status page, and finance wants one seat price for all of it. That is the gap IncidentBot fills.
Teams already planning to leave Splunk can follow the five step migration on our Splunk On-Call alternative page, including how to rebuild routing rules. If OnPage is also on your shortlist, the OnPage alternative page prices its Gold scheduler and SMS add-on for the same team sizes.
Where IncidentBot fits next to Splunk On-Call and PagerDuty
IncidentBot pages the right engineer by push, SMS and voice, escalates when nobody acknowledges, opens a Slack channel with /incident, drafts the status page update from the same timeline and builds the postmortem skeleton when the incident closes. Stakeholder viewers are included in every plan and never billed. Starter is 24 USD per responder a month billed annually with 100 SMS and voice pages per user through your own Twilio account and one public status page; Team is 49 USD with no IncidentBot limit on SMS and voice and three status pages. All plans are on the pricing page.
Where we do not compete: we have no native mobile app (engineers install the web app with push, then SMS and voice take over), no AIOps noise reduction and no two-way ServiceNow sync. If any of those is a hard requirement, PagerDuty on a platform plan is the better buy.
Questions to ask both vendors before you sign
- Splunk: what is our per-seat price at 11, 15 and 25 seats, in writing, on the plan that carries the rules engine we use?
- Splunk: does buying through our existing Splunk or Cisco agreement, AWS Marketplace or Google Cloud Marketplace change the price or the term?
- PagerDuty: is the external status page included on Professional for us, or billed as an add-on?
- PagerDuty: do stakeholders count as seats on the plan we are buying, and how are seats trued up mid-term?
- Both: what does a 30 percent head count change in the middle of the term cost?
- Both: which features in this quote does our team actually use today?
Is Splunk On-Call cheaper than PagerDuty?
For 10 users or fewer, yes. Splunk publishes 5 USD per user a month billed annually up to 10 seats, against 21 USD for PagerDuty Professional. Above 10 seats Splunk prices by quote and directories list 10 to 45 USD per user, so PagerDuty can be cheaper for larger teams.
Is Splunk On-Call the same as VictorOps?
Yes. Splunk bought VictorOps in 2018 and renamed it Splunk On-Call, and Cisco completed its purchase of Splunk in March 2024. It is one product with one price list, so VictorOps plan names and prices still shown on old forum threads no longer apply.
Does PagerDuty have a free plan and Splunk On-Call does not?
Yes. PagerDuty Free covers up to 5 users with 1 schedule, 1 escalation policy and 100 SMS or phone notifications a month. Splunk On-Call offers a free trial but no permanent free plan, though its 5 USD entry seat is low enough that small teams rarely mind.
Which is better for a team that runs incidents in Slack?
Neither entry plan includes a full Slack incident workflow with roles, a timeline and a status page. PagerDuty adds it on its platform plans from 2,800 USD a year. IncidentBot includes the Slack channel, timeline and a status page from 24 USD per responder a month billed annually.
How long does moving between Splunk On-Call and PagerDuty take?
A team of 10 to 40 usually needs two to four weeks: rebuild rotations and escalation, port the alert routing rules, run both pagers in parallel for one to two weeks and confirm every engineer receives push, SMS and voice before switching the old one off.