|
|
|
|
|
|
by pancaku
1818 days ago
|
|
|
Both the website, and product look very polished. I like the design. Is this a competitor to PagerDuty? I'm curious what features you're offering to take on them as the incumbent in the space. I've never actually used either software. The companies I've worked for all use their own in-house incident/oncall frameworks. But would love to know more! |
|
|
Yes, and no. Almost all of our customers already use PagerDuty, with Opsgenie a distinct second. They predominantly use them to wake people up when things go wrong, but don't use them to actually _run_ their incidents.
I think there's a variety of reasons for this from it not being easy to imprint your process onto PagerDuty, to it being harder to use for non-technical folks, and it not being where you communicate with the rest of your organisation (often Slack).
The most common competitors we come up against are:
1. Your process being written down on a piece of paper, which humans then remember to follow (spoiler: it's hard to do this) 2. In-house tooling that folks have built to help fix this problem. Many scale-ups have built their own (Stripe, Monzo, Robinhood, Transferwise, Influx Data, etc).
We take people from thing went wrong, to response, to debriefing, to following up on actions afterwards. Right now, we don't wake people up through alerting, but it's a natural next step for us to go and do that as well.