Comparison
CallHeim vs PagerDuty.
CallHeim is on-call alerting, escalation, scheduling and incident response for SRE, platform, IT operations and security teams who want rules they can read end to end. Plans cover up to 200 seats on Business. Below is how CallHeim compares with PagerDuty on pricing, alert handling and incident workflow, and how to move.
Competitor information last verified October 2026. Sources are linked beside each fact.
Why teams evaluate CallHeim
What CallHeim does differently.
- 01
Rule-based alert handling, published, on every plan
The rules behind the noise handling are published. A repeat attaches to its open incident, within 24 hours of the incident opening unless the sender supplies its own dedup key. A series that changes state 4 times in 600 seconds is treated as flapping. Near-identical titles from the same source and service group together at a similarity of 0.6. Title grouping can be switched off for your organization.
- 02
Predictable, explainable decisions
CallHeim’s alert handling is rule-based and deterministic: given the same alert, settings and state, it makes the same decision.
- 03
A severity suggestion, not a decision
CallHeim suggests a severity from a fixed keyword ruleset plus your own resolved incidents, shows the matched terms, and a person applies it. Suggestions never change severity or page anyone.
- 04
An append-only audit log with a retention-locked daily copy
The audit log is append-only: no client can modify or delete an entry. Audit records are copied daily to an S3 Object Lock archive (governance mode) with a 7-year retention lock, held by CallHeim. An audit-log export downloads straight to your device, and CallHeim keeps no copy of it.
- 05
A list price with no separate add-on for noise handling or analytics
Starter $9, Pro $15 and Business $29 per user per month. Enterprise is negotiated.
PagerDuty Advance for Incident Management starts at $415 a month with an annual commitment. (PagerDuty AIOps pricing page, checked 2026-10-19) The PagerDuty Status Pages add-on starts at $89 per 1,000 subscribers a month. (PagerDuty Customer Service Operations pricing page, checked 2026-10-19)
Product screenshots
What the console looks like.

Escalation policies in the CallHeim console: tiers, per-tier timeouts and a fallback target.

The on-call schedule: rotation layers and the final schedule they produce.
How it works
How CallHeim handles an alert.
Six steps from the moment an alert arrives to the moment escalation stops.
- 01
Alert arrives
Send alerts to your CallHeim integration URL over HTTPS, in CallHeim’s alert format or through a field mapping you define. CallHeim queues each accepted alert durably and processes it asynchronously; acceptance is an HTTP 202.
- 02
Duplicates collapse
A repeat of an open alert attaches to its incident instead of paging again. A repeat matched on its title or e-mail subject attaches for 24 hours after the incident opens, and a P1 or P2 repeat on an open P3 to P5 incident opens its own incident. See how deduplication works.
- 03
Severity suggested
CallHeim suggests a severity from a fixed keyword ruleset plus your own resolved incidents, shows the matched terms, and a person applies it. Suggestions never change severity or page anyone.
- 04
Escalation runs
An unanswered tier times out and the escalation moves to the next tier, ending at the fallback. Escalation policies have up to 8 tiers, each paging a person, a team or a schedule, with per-tier timeouts from 1 to 240 minutes, optional repeats and a mandatory fallback. The whole chain must fit within 24 hours.
- 05
Paged by e-mail, text or call
Incident pages go out by e-mail on every plan, each with a signed acknowledge link, and sent, delivered and bounced status is recorded on the incident. Pages can also go out by push, text message and phone call. Acknowledge an incident from the page e-mail or text through a signed, single-use link. It opens a confirmation page that names the incident, and it expires within 24 hours.
- 06
Acknowledge stops it
Acknowledging an incident stops the escalation.
Key differences
Three places the two platforms diverge.
Explainability, pricing approach and add-on structure: the areas buyers ask about most, each side sourced.
Explainability
CallHeim Each alert the pipeline processes is stored with what happened to it (opened an incident, grouped as a duplicate, or suppressed) and the reason.
PagerDuty PagerDuty documents four alert-grouping methods: Intelligent, Alert Content, Intelligent plus Alert Content, and Time only. Grouping comes with the AIOps add-on, or as Signal Intelligence in the PD Reliability Platform plans. (PagerDuty alert grouping documentation, checked 2026-10-19)
Pricing approach
CallHeim Starter $9, Pro $15 and Business $29 per user per month. Enterprise is negotiated.
PagerDuty PagerDuty lists a Free plan (up to 5 users) and a Professional plan at $25 per user per month, or $21 on an annual plan. Larger deployments are sold as the PD Reliability Platform, an annual platform fee that includes seats. (PagerDuty pricing page, checked 2026-10-19)
Add-on structure
CallHeim Core analytics (MTTA, MTTR, alert volume by source, escalation rate and period-over-period comparison, over windows of 7 to 365 days) are not gated by plan; related-incident and responder insights start at Pro.
PagerDuty The AIOps add-on starts at $699/mo on an annual plan ($799/mo billed monthly), priced per accepted event, and needs at least one paid Incident Management user. (PagerDuty AIOps pricing page, checked 2026-10-19)
Pricing approach
A 25-seat scenario, at list price.
Formula: seats × rate × 12, list prices only, no tax or discounts.
CallHeim Pro
$4,500a year
25 seats × $15 / user / month × 12
Monthly list price per user.
Some features are tied to plan: the REST incident API and related-incident insights on Pro and above; audit-log export, an IP allowlist for administrative changes, private status pages and SCIM user provisioning on Business and above; email-to-alert (per-organization inbound alert e-mail addresses) on Trial, Business and Enterprise, not Starter or Pro.
PagerDuty Professional
$6,300a year
25 seats × $21 / user / month × 12
Annual-plan rate. Billed monthly it is $25 per user ($7,500 a year for 25 seats).
Professional includes an external status page (up to 250 subscribers), 2 teams and 2 predefined incident roles. (PagerDuty pricing page, checked 2026-10-19)
List prices, before tax or discounts. Paid plans are invoiced and activated directly by the CallHeim team; ask from Billing in the app. The two vendors’ plans bundle different capabilities, so compare inclusions against your own requirements, not the seat price alone. Scenario dated 2026-10-19; vendor prices change, so re-check before you rely on it.
Migration
Moving from PagerDuty.
The importer reads your PagerDuty or Opsgenie configuration from a US or EU account, and a dry run shows you the result before anything is written to your organization.
Run in parallel during a move: CallHeim receives PagerDuty Events API v1 and v2 requests and Opsgenie outgoing webhooks, and alerts forwarded from Splunk On-Call, Squadcast (now SolarWinds Incident Response), Zenduty (now Xurrent IMR) and Grafana OnCall. Every sender needs its own CallHeim integration URL; existing PagerDuty routing keys are not reused.
Snapshot
A selected capability comparison.
A short, sourced comparison of status pages, alert grouping, pricing and alert sources.
- Status pageavailable
- Alert groupingavailable
- Alert sourcesavailable
| Topic | CallHeim | PagerDuty |
|---|---|---|
| Status page | Available. Every organization has a public status page, and your team posts the updates. Additional pages for different audiences show only the services you add to them, with their posts and scheduled maintenance, and visitors can subscribe by e-mail or with a Slack webhook. | Professional includes an external status page (250 subscribers) and no private status page; the PD Reliability Platform tiers include external and private status pages. PagerDuty pricing page · checked 2026-10-19 |
| Alert grouping | The rules behind the noise handling are published. A repeat attaches to its open incident, within 24 hours of the incident opening unless the sender supplies its own dedup key. A series that changes state 4 times in 600 seconds is treated as flapping. Near-identical titles from the same source and service group together at a similarity of 0.6. Title grouping can be switched off for your organization. | PagerDuty documents four alert-grouping methods: Intelligent, Alert Content, Intelligent plus Alert Content, and Time only. Grouping comes with the AIOps add-on, or as Signal Intelligence in the PD Reliability Platform plans. PagerDuty alert grouping documentation · checked 2026-10-19 |
| Pricing model | List price per seat: Starter $9, Pro $15, Business $29 per user per month. Enterprise is negotiated. | PagerDuty lists a Free plan (up to 5 users) and a Professional plan at $25 per user per month, or $21 on an annual plan. Larger deployments are sold as the PD Reliability Platform, an annual platform fee that includes seats. PagerDuty pricing page · checked 2026-10-19 |
| Alert sources | 135 alert sources, each with a payload mapping for that tool’s webhook format and its own setup page. | PagerDuty self-reports 750+ out-of-the-box integrations. PagerDuty pricing page · checked 2026-10-19 |
Competitor facts checked October 2026. Vendor prices and inclusions change; re-check before you rely on a figure here.
Questions
About switching.
Who is CallHeim for?
SRE, platform, IT operations and security teams that want on-call alerting, escalation, scheduling and incident response with rules they can read end to end. Plans cover up to 200 seats on Business.
Can I run CallHeim next to PagerDuty?
Yes. CallHeim receives PagerDuty Events API v1 and v2 requests, so you can forward alerts to both tools while you compare. Every sender needs its own CallHeim integration URL; existing PagerDuty routing keys are not reused.
How does pricing work?
Starter $9, Pro $15 and Business $29 per user per month. Enterprise is negotiated. Alerts are not metered or billed. Seat caps are the only published plan limits. Some features are tied to plan: the REST incident API and related-incident insights on Pro and above; audit-log export, an IP allowlist for administrative changes, private status pages and SCIM user provisioning on Business and above; email-to-alert (per-organization inbound alert e-mail addresses) on Trial, Business and Enterprise, not Starter or Pro.
Try it on one service before you move the pager.
Start a 14-day trial, connect one alert source and send yourself a test page.