Pagerduty feels like it used to be the dominant player especially for small teams but I found it surprisingly expensive and cumbersome to use for a small team and Ops-genie is EOL, splunk on-call feels weird to use w/o splunk.
Pretty much everyone still uses PagerDuty, but Incident.io is starting to be competitive as well.<p>I've never heard of anyone using Opsgenie or Splunk for on-call, and Opsgenie's 3-week outage or whatever is pretty damning.
JJ here, obviously bias as I am the founder of Rootly.com that's building in this space.<p>We are a modern AI-native on-call and incident management platform here at Rootly.com. We are helping fast-growing companies like from Replit, Figma, NVIDIA, and 100s of others respond faster.<p>Some of the biggest frustrations with legacy providers like PagerDuty (who I have a lot of respect for in pioneering on-call) is their lack of innovation (only a phone call) and how expensive it is.<p>Some fan favourites include request coverage for overrides, automatic adjustments based on PTO and holidays, native Slack/Teams collaboration (not just paging), native shadow rotations, syncing with Slack user groups, a beautiful UI and mobile app, and an all-in-one platform for status pages, workflows, communications, retrospectives, and metrics.<p>If you're a small team Rootly has a pretty discounted version for startups. Here is a full comparison if you're interested: <a href="https://rootly.com/comparisons/pagerduty-vs-rootly-on-call">https://rootly.com/comparisons/pagerduty-vs-rootly-on-call</a>
The biggest knock against pagerduty is its both expensive and doesnt have simple features like connecting Pagerduty schedules to slack user groups.<p>For example if I want to have a slack group that pings (not pages) to current oncall person<p>```<p>@oc-platform<p>```<p>I need to pay $25/month to a random third party slack app.<p>Its insane, do they even use pagerduty internally?