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?
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
What does AI-native mean in the context of on-call and incident management?
simantel•8mo ago
I've never heard of anyone using Opsgenie or Splunk for on-call, and Opsgenie's 3-week outage or whatever is pretty damning.
jjtang1•8mo ago
lawrjone•8mo ago
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!)
https://incident.io/customers/intercom