21–30 of 135 posts
I like this! Thanks for building it. What’s the biggest differences between PagerDuty?
Why is the pricing per user? Is that what your costs are most dependent on? I bet not. I'd argue $5/user is just teaser pricing on its way to PagerDuty's $21+/user. Regardless, cool project—happy to see more competition.
I found PagerDuty to be grossly underwhelming when our team moved to it. I'd focus on stupid-easy integration & some reasonable calendar management to differentiate. PagerDuty Calendar/Holiday/Workday management and cross-regional scheduling were very poorly implemented. The amount of manual schedule adjustment when someone actually wanted to take their 1 week vacation was insane. We ended up with overrides on top of…
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 inte…
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.
Why is the pricing per user? Is that what your costs are most dependent on? I bet not. I'd argue $5/user is just teaser pricing on its way to PagerDuty's $21+/user. Regardless, cool project—happy to see more competition.
Since when does anyone set or scale their price on their costs?
Earlier quoted context omitted.
Since when does anyone set or scale their price on their costs?
Presumably when someone says that such a model frustrates them. But perhaps not.
Why is the pricing per user? Is that what your costs are most dependent on? I bet not. I'd argue $5/user is just teaser pricing on its way to PagerDuty's $21+/user. Regardless, cool project—happy to see more competition.
You base prices on what people are willing to pay.
> That's why All Quiet notifications are app only. This is prone to loss. I've struggled with notification delivery reliability on Android for years . If I don't touch my phone for a few hours and then wake the screen, I get a flurry of notifications all at once from the last few hours. But I need to be aware of pages in real-time. There should really be a call and text notification channel else I don't see this gett…
I found PagerDuty to be grossly underwhelming when our team moved to it. I'd focus on stupid-easy integration & some reasonable calendar management to differentiate. PagerDuty Calendar/Holiday/Workday management and cross-regional scheduling were very poorly implemented. The amount of manual schedule adjustment when someone actually wanted to take their 1 week vacation was insane. We ended up with overrides on top of…
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 inte…
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)?
> Don't lose alerts. We believe that crucial incidents need to have a dedicated context. Alerts sent out through Slack or Email can often be overlooked in those channels. That's why All Quiet notifications are app only. Question - How does your app ensure incident notifications are received? I haven't used PagerDuty before, but for others I've used, we got a phone call for alerts and sometimes texts for warnings. Rec…
I cannot ensure that notifications are received. But neither can you with Email or SMS. Technically a Call might be more reliable, but still, your phone could be turned off or might not even have reception for a call.
Furthermore if a call can't be placed the originating system is aware of this immediately, and can proceed accordingly (e.g. move to the next person in line). This isn't the case for any other notification method, which requires the (absense of) an explicit ack by the user to infer that the notification failed.
Pagerduty handles this very well. If you have the app it will first try to notify through the app. If there is no ack within a couple of minutes it calls you.
If you persevere with this project you'll quickly realize you need phone calls.
What about a?
It won't do b, c, d, x, and y, that's a deal breaker for me.
Can I do d, f, t, m - no? Ugh, nice try good luck on your project.