I don't get the pricing of PagerDuty and OpsGenie. It seems too expensive for us. We're only a few people on-call and we need something simple, barebones, that just works and works reliably.
You get on-call + incident response + status pages. And a pretty "defaults only" experience ootb.
However, one make-or-break feature - does Rootly have a Terraform provider? We rely heavily on Terraform for building out our Opsgenie setup.
[1]: https://registry.terraform.io/providers/rootlyhq/rootly/late...
We take extensibility pretty seriously. Outside the basics, we just released our own agent ready API (https://rootly.com/blog/introducing-rootlys-api-ai-agent-fir...), MCP, docs are now LLM ready (https://docs.rootly.com/llms-full.txt).
One small bit: maybe include a link to your website? That would make it easier to clickthrough and looksee
https://rootly.com/ || and Opsgenie comparison (features): https://rootly.com/comparisons/opsgenie-vs-rootly-on-call
There are some pretty low hanging fruit stuff that would make the PD experience palatable (e.g. ability to page teams not just services, allow for partial overrides). These things for us were <1 week projects.
I do think PD is trying to rectify it by acquiring Jeli, giving it away for free in their new pricing plan, etc. Def feeling the squeeze a bit if I had to guess.
To not give too much of our roadmap away in a public forum, some of the basic components of overrides, paging groups and the web UI - keep your eyes peeled this year, one of our big focus areas is looking at how not only do we eliminate some of these gaps around on-call management and UI, but also going beyond just filling these table stakes. As you might imagine, PagerDuty scaled pretty aggressively (while also keeping our high reliability standards in place - customer trust is our #1 priority, after all we need to be up when everyone else is down), and we've had to make some investments to unlock our roadmap for this upcoming year.
Real talk though, happy to continue the conversation/ meet up over a zoom. Send me an email: dgodbout[@]pagerduty.com. There are humans over here at PagerDuty who care a lot about folks like yourself and I consider myself lucky to get build products for people who are responsible for ensuring things just "work".
I championed and led the introduction of Rootly’s incident management product at two tech companies and counting. Rootly scales well - the Slack bot replaced chains of comms we used to have humans to handle. It’s reliable. And the attention to detail in their product feels like a love letter to SRE.
Rootly has the product chops to make a top notch incident management product. The domain modeling they’ve done for Rootly Oncall is solid - it feels like a superset of PagerDuty and Opsgenie.
Anyone moving off Opsgenie would benefit from a close look at it.
Is weirdly broken (at least for me) on Safari on desktop. Every mouse movement or key click causes all the tiles to enlarge.
It's fine on Chrome and Firefox.
Damn. As a founder in the incident management space (Rootly) I've had a lot of respect for Opsgenie. They had unique features like heartbeats and ran a lean but mighty team before selling to Atlassian. We saw them the most in Europe by far.
Okay here comes to promotional part (don't hate me). If anyone is looking for a modern alternative to Opsgenie that isn't as expensive as PagerDuty, Rootly is worth checking out (Slack-native, holiday scheduling, request coverage, clean mobile app, etc).
Previous to Rootly I worked at Instacart where I helped us transition from PD to Opsgenie. Afterwards, still not being happy I built Rootly.
Today, we've helped Trivago, Motive, Yahoo, and quite a few others make the switch. Pretty easy with our importer tool, etc.