Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Launch HN: Rootly (YC S21) – Manage Incidents in Slack

news.ycombinator.com

Post reply on HN
Print view View original

31–40 of 96 posts

Re: Launch HN: Rootly (YC S21) – Manage Incidents in Slack

#31

Post by kwent »

midislack wrote: post #15

I’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.

We have seen Slack start investing in this area with their own Workflow Builder they announced last year. One of the big use cases they highlighted was incident response. We haven't ran into any customers trying to leverage that just yet though as still a lot of heavy lifting required.

IMO what makes Slack so power is their app ecosystem. We aren't too worried about them shutting that down or competing with us. We see the awesome folks on the Slack Platform team continue to invest heavily there.

But if Slack wants to seriously compete in this space we'd welcome it. The more attention and competition the better. Most accounts we approach we've found they didn't know off the shelf solutions existed!

Re: Launch HN: Rootly (YC S21) – Manage Incidents in Slack

#34

Post by btables »

mchusma wrote: post #7

I 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.

firehydrant.com has a free tier that allows people to open incidents from Slack. It also includes the service catalog, runbooks, and status pages.

Re: Launch HN: Rootly (YC S21) – Manage Incidents in Slack

#35

Post by hijinks »

dneri wrote: post #32

Congrats on the launch, I would use this for my smaller team. Why have a pricing page with no pricing on it though?

because they want to look at crunchbase and find out how much funding you got then charge you based off that.

I wish companies would boycott companies doing contact us for pricing

Re: Launch HN: Rootly (YC S21) – Manage Incidents in Slack

#36

Post by kwent »

dneri wrote: post #32

Congrats on the launch, I would use this for my smaller team. Why have a pricing page with no pricing on it though?

Thank you for the kind words and feedback.

If you email jj@rootly.com we can get you some pricing ASAP. It'll be dependent on number of users and level of support/onboarding/custom feature development required.

But if you're a small team, Rootly is powerful and ready to go out of the box with defaults and you might not require some of the custom stuff.

To answer your question directly, we customize each package for each individual customer on a bunch of variables.

Re: Launch HN: Rootly (YC S21) – Manage Incidents in Slack

#37

Post by btables »

ceejayoz wrote: post #27
btables wrote: post #22

Earlier quoted context omitted.

Yikes! Never like seeing that. Can you email me directly and I will get this sorted? robert@firehydrant.com

Tickets #1452, #1454, #1588. Was told "the account has been removed" on March 22nd, but I continue to receive "Last week on FireHydrant" emails specific to our org, most recently on May 29.

Thanks, emailed you as well. Sorry you ran into this!

Re: Launch HN: Rootly (YC S21) – Manage Incidents in Slack

#38

Post by kwent »

evnsio wrote: post #30
evnsio wrote: post #28

Earlier quoted context omitted.

Hey folks. Co-founder of incident.io here. Firstly, thanks for the kind words Quentin – appreciate it, and congrats on your progress so far. incident.io is pitched slightly differently to Rootly, insomuch as we're not building an engineering product, but instead something that's designed to work for entire organisations. I saw first hand what this looks like at Monzo – a bank here in the UK – where incidents weren't…

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

The open source option from Netflix is quite popular too: https://github.com/Netflix/dispatch

Re: Launch HN: Rootly (YC S21) – Manage Incidents in Slack

#39

Post by kwent »

danpalmer wrote: post #26
kwent wrote: post #12

Earlier quoted context omitted.

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, aler…

For non-technical purchasers, it makes sense to price by the value the organisation will get out of the tool. However for tools that technical users are involved in you have to fight against the "I could build this myself" factor. There are lots of tools that are basically CRUD apps, or maybe CRUD with a chat interface in this case, which are fundamentally straightforward to build a first-pass version of. I'm sure th…

This was an awesome response and you absolutely nailed it.

A vast majority of our customers actually have some sort of internal bot built. It's quite limited usually and largely focused on the "creation" portions of an incident. Most commonly create an incident channel, create Zoom, link to a few integrations, and that seems to be it.

But depending on who you speak with that can be enough which is totally fair. Especially when complexity and incident volumes are low.

And yes agree not every user on the platform will value it the same. An SRE vs. someone in legal will find different value out of it. Our goal is to make this accessible to the entire org not just engineering teams.

Thank you for the feedback on the pricing page as well!

Re: Launch HN: Rootly (YC S21) – Manage Incidents in Slack

#40

Post by ezekg »

porpoisemonkey wrote: post #29
kwent wrote: post #12

Earlier quoted context omitted.

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, aler…

Not the OP, but in one of the smaller companies (~30 people/~12 engineers) you describe that's currently looking for a tool like this. I can't actually see the pricing because it's behind a nebulous "contact us" link, but if this is more than about $5/user/month I would definitely balk at the price. Larger companies already have dedicated platform and tooling teams with enough technical talent and bandwidth to build…

You'd balk at more than $5/user/mo? For 12 engineers, that's only $60/mo (and for all 30 employees, $150/mo). I'd guess that you're not a C-level since you said you'd balk at that price, which is incredibly cheap. I pay more for my business's status page.
Post reply on HN