Show HN: I was frustrated with pricing of PagerDuty et al., so made it myself

Re:Show HN: I was frustrated with pricing of PagerDuty et al... by mads_quist on Sunday April 23, 2023 @11:20AM (#35676990)

I tried to make managing the incident escalation policies as simple as possible. It currently works with a simple drag&drop mechanism. The way PagerDuty is doing this also seemed very cumbersome to me. Of course All Quiet is currently missing holiday / off hours features. I'm still figuring out what's the best approach there.

Regarding your last paragraph - can you elaborate on this? I tried to make All Quiet be integratable with basically every system by Email and Webhook integrations. Do you see this as a problem?

Thanks for your feedback in general!

[ Parent | on HN ]

Re:Show HN: I was frustrated with pricing of PagerDuty et al... by steveBK123 on Sunday April 23, 2023 @11:42AM (#35677191)

Re: cost & holidays/hours

On pricing - I don't think it matters for small orgs the way it does for big orgs. Let's say today I am in a role where I am effectively the CTO of a 5ish person startup, with only 3 technical. So whether I spend $200/year or $1500/year, I don't really care. Both are more than $0, and require me to review a contract, do a POC, have a lawyer or someone review things, etc.

My internal time to do all those things is more like $10-30k, easily.

Now, do I decide it's worth my time knowing that my devs are going to basically turn off their phones / go to do-not-disturb-mode still because it's sense of working hours is non-existent (making it worse than PagerDuty & Slack notification tuning, both of which I already despise)?

[ Parent | on HN ]

Re:Show HN: I was frustrated with pricing of PagerDuty et al... by steveBK123 on Sunday April 23, 2023 @11:31AM (#35677097)

I think the problem with integration is probably a man-hours thing. A lot of shops have a hodgepodge of 3rd party tools which are not necessarily the latest&greatest Cloud/FAANG darlings - Geneos, Jira, ServiceNow, ControlM, Autosys, Tidal.

These tools can vary by industry & org size, so maybe finding some traction in a particular slice so that you can really serve that niche can give you more traction, I dunno.

It just has to be dead simple to integrate, and it's worth considering some sort of professional services/customer success engineering layer.

The problem I've seen is that in every (financial services) org I have worked, the teams responsible for integrations to these types of tools are really operations type teams that do a little development in their spare time. So it never gets done well, or completely.

To me, the only benefit of PagerDuty type tool is when it becomes the single point of escalation. If its just one of many, the product will not be sticky within a given org.

[ Parent | on HN ]