7 points by skullum 2 days ago
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.
I'm one of the engineers at incident.io, so thanks for the mention! But yes, when we first started the majority of our customers bought us for incident management and used PagerDuty as their on-call provider (phones them, receives the alerts, hands-off to us when an incident starts).
We've since built on-call directly into our product and we've had loads of those customers migrate entirely into us, dropping PagerDuty. The biggest customers we're onboarding now tend to buy us as their sole on-call and incident management tool, too.
We have a bunch of case studies of people who've moved if that's useful to anyone. My favourite is probably Intercom who migrated from PagerDuty into our on-call in a few weeks (the Intercom team are great fun to work with!)
JJ here, obviously bias as I am the founder of Rootly.com that's building in this space.
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.
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.
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.
If you're a small team Rootly has a pretty discounted version for startups. Here is a full comparison if you're interested: https://rootly.com/comparisons/pagerduty-vs-rootly-on-call
The biggest knock against pagerduty is its both expensive and doesnt have simple features like connecting Pagerduty schedules to slack user groups.
For example if I want to have a slack group that pings (not pages) to current oncall person
```
@oc-platform
```
I need to pay $25/month to a random third party slack app.
Its insane, do they even use pagerduty internally?
Tbh this took us about a day to build and well worth it. Makes on-call lives so much easier. Not sure why they don't yet https://rootly.com/changelog/sync-on-call-schedules-with-sla.... Sorry to be promotional.
Pretty much everyone still uses PagerDuty, but Incident.io is starting to be competitive as well.
I've never heard of anyone using Opsgenie or Splunk for on-call, and Opsgenie's 3-week outage or whatever is pretty damning.