PagerDuty per-user pricing scales badly past 50 engineers, and the workflow is split between PD and a separate runbook tool.
PagerDuty does paging well. It does not do everything else, runbooks live elsewhere, postmortems live elsewhere, the on-call jumps between tools the moment they ack. And the per-user pricing model makes it the second-largest line item in many SRE budgets after Datadog. Teams stay because cutting over feels risky, schedules and integrations are operationally critical and can't break for a single shift.
Nova's on-call management imports the rotation and escalation model directly. Runbooks land next to alerts, so the on-call workflow is one tool instead of three.
Nova reads PagerDuty rotation exports and recreates them natively, follow-the-sun, primary/secondary, holiday overrides. Schedule continuity is preserved across the cutover.
Each PagerDuty escalation policy maps to a Nova policy with the same hop pattern (page primary -> 5min -> page secondary -> 10min -> page manager).
When the alert fires, Nova surfaces the matching runbook in-line. The on-call doesn't context-switch to Confluence or Jira to find the procedure.
Get Started Free, cancel anytime. Or book a 30-minute walkthrough with a founder.