What do you see as different to incident.io?
Launch HN: Rootly (YC S21) – Manage Incidents in Slack
11–20 of 96 posts
Re: Launch HN: Rootly (YC S21) – Manage Incidents in Slack
#12I do t get the pricing on things like this and pingdom. This stuff seems like it should be cheap, like $5/user/mo. But everyone seems to go expensive. There are other industries that are similar, but this always stood out to me as an industry where the pricing never felt right to me.
I appreciate the feedback.
We tried to think of our pricing as the value a user would get out of the tool. The amount of time and headache we'd save them when actually responding to an incident. We've found a lot more pushback for smaller sized companies (e.g. Just curious for my own learning, is the thinking behind "should be cheap" motivated by potentially not everyone would need access to tools in monitoring, alerting, response?
Re: Launch HN: Rootly (YC S21) – Manage Incidents in Slack
#13I do t get the pricing on things like this and pingdom. This stuff seems like it should be cheap, like $5/user/mo. But everyone seems to go expensive. There are other industries that are similar, but this always stood out to me as an industry where the pricing never felt right to me.
[deleted]
Re: Launch HN: Rootly (YC S21) – Manage Incidents in Slack
#14Re: Launch HN: Rootly (YC S21) – Manage Incidents in Slack
#15I’ve always wondered about building a startup on another startup’s back. What happens if they cut you off? Is getting bought up by Slack the end goal here? Seems like a big risk, one whim at Slack and you’re toast.
Re: Launch HN: Rootly (YC S21) – Manage Incidents in Slack
#16Congrats on the launch. How is this different than FireHydrant?
The CEO of FireHydrant had a less charitable answer last year: https://twitter.com/bobbytables/status/1403090735038189573
FireHydrant was my worst experience out of every incident manager I experimented with - literally nothing worked during our tests - and after two months of asking they're still refusing to remove our account; we still get a weekly email dashboard.
Re: Launch HN: Rootly (YC S21) – Manage Incidents in Slack
#17I’ve always wondered about building a startup on another startup’s back. What happens if they cut you off? Is getting bought up by Slack the end goal here? Seems like a big risk, one whim at Slack and you’re toast.
Let's hope slack itself doesn't start using rootly for incident response :)
Re: Launch HN: Rootly (YC S21) – Manage Incidents in Slack
#18I’ve always wondered about building a startup on another startup’s back. What happens if they cut you off? Is getting bought up by Slack the end goal here? Seems like a big risk, one whim at Slack and you’re toast.
It’s actually pretty common to start on the back of an incumbent. As a startup gains success it can do more to reduce dependency by building more of the end to end experience and distribute risk to more than one partner.
Re: Launch HN: Rootly (YC S21) – Manage Incidents in Slack
#19What do you see as different to incident.io?
Great question.
Incident.io is likely our closest competitor and are doing amazing work over there. They have a strong team and smart founders that have been in the trenches before. From a product perspective they are my favourite of our competitors if I had to pick one myself to use.
Our differences are largely driven by the customer segment we serve and the needs of SMB vs. enterprise. We've found by going upmarket to enterprises such as Canva, Shell, Bolt, it is quite difficult to develop an opinionated platform based on only industry best practices as each organizations approach to incidents (regardless if it's the same tooling) vary greatly in their process. You'll find Rootly to be a lot more pluggable, customizable, and can turn any knob the make the product work for you if needed. The reason for this is because we find change is hard, even small process tweaks in process. We want to reduce as much of that as possible when a new tool is brought in.
We've been around longer so naturally our product maturity is further along. Such as Workflows (https://rootly.com/changelog/2021-11-30-workflows-2-0), integrations (30+), Terraform/Pulumi provider, and security (https://rootly.com/security).
Again, they do a great job. Just different needs and requirements for startups vs. enterprise.
If helpful, customers have written reviews for us on our respective G2 pages: https://www.g2.com/products/rootly-manage-incidents-on-slack...
Re: Launch HN: Rootly (YC S21) – Manage Incidents in Slack
#20no pricing, no thanks