response

As the person who originally wrote the Monzo Response project (https://github.com/monzo/response), I expect you'll find some traction in smaller orgs, but when folks start doing things at scale they'll hit an inflection point where running their own incident software/not having folks to log feature requests with will force them to pick something more off-the-shelf. Basically, nobody runs their on-call system on open-source because it's mission critical. At a certain point, IM platforms hit the same level of criticality.

Oh and if you're not in the market to buy something, I open sourced the tool I originally wrote at Monzo: https://github.com/monzo/response

It's great to see more competition in this space. Generally speaking, what I miss in these "incident management" products is also an integrated, flawless way to handle incidents when they're happening. I'm talking about: 1. Quickly creating a proper chat 2. Quickly creating an incident document where you can pin chat messages and use it in the post-mortem. Ideally, pinning some graphs that you'd extract from your observability solutions 3. Having a status page to put a small description for non-technical stakeholders. PagerDuty covers some of this. Monzo's Response [1] and now incident.io [2] try to cover it too. I'd like to have this experience end-to-end. 1 - https://github.com/monzo/response 2 - https://incident.io/