Recent submissions

Comment · 2 years ago
Hey, incident.io CEO here. I'm sorry to hear that. Can you explain a little bit more?
Comment · 2 years ago
Thank you: let us know what you think!
Comment · 2 years ago
Hello: incident.io CEO here. Thank you for the kind words, it's much appreciated. I countersign your last point around business value being in incident response.

There's truth to this: as with all new product categories, there's some education that needs to go along with the sale, and budget that needs to be found, that doesn't currently exist. On the whole, we haven't found this to be a large challenge so far. Most people look at our product, see a very fair exchange of value, and are happy to pay.

However, that isn't why we built On-call. We built it - along with many other reasons - because it's part of the trifecta that we think you need to do incident response well:

1. A way to alert people that something is wrong 2. A way for them to respond, resolve and learn from the incident 3. A way for them to communicate to their customers about it

We have built all of these respectively in On-call, Response and Status Pages. Consolidating all of these into one cohesive product makes obvious sense, to us at least. We'll see what the market says!

Comment · 2 years ago
Hello Rootly CEO! Worth disclosing next time you post, I think
Comment · 2 years ago
incident.io CEO here! This is such a cool and unique usecase. Love it.
Comment · 3 years ago
Hey, incident.io CEO here! Thanks for mentioning us.
Comment · 4 years ago
Hey, incident.io CEO here. Glad to hear you’re happy with the product. The people at Grafana are great - congrats on the launch! Will have to take the product for a spin sometime :)
Comment · 4 years ago
Hey JJ. Appreciate the hustle, but please disclose that you're supporting your own product here (disclosure: I'm the incident.io CEO)
Comment · 4 years ago
CEO here! Indeed we did :)

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton