Show HN: FireHydrant – A simple incident response tool
firehydrant.io
Show HN: FireHydrant – A simple incident response tool
1–10 of 17 posts
Re: Show HN: FireHydrant – A simple incident response tool
#2Re: Show HN: FireHydrant – A simple incident response tool
#3Hard for me to judge if I’d want to sign up for a trial. There weren’t enough screenshots on the homepage for how I personally evaluate services at a glance.
Re: Show HN: FireHydrant – A simple incident response tool
#4Re: Show HN: FireHydrant – A simple incident response tool
#5One thing that might be useful is to see aggregate incident data and find components that are operational burden for the team.
Shameless plug: I built http://nurtch.com for quick incident response with interactive runbooks. You can pull in graphs, get deployment status, rollback deployments, run SQL queries, run bash scripts and terminal commands over SSH directly from runbook.
Re: Show HN: FireHydrant – A simple incident response tool
#6Hard for me to judge if I’d want to sign up for a trial. There weren’t enough screenshots on the homepage for how I personally evaluate services at a glance.
Noted, did the features page hit that marker for you if you dont mind if I ask?
Re: Show HN: FireHydrant – A simple incident response tool
#7Hard for me to judge if I’d want to sign up for a trial. There weren’t enough screenshots on the homepage for how I personally evaluate services at a glance.
Noted, did the features page hit that marker for you if you dont mind if I ask?
* Features page has more screenshots snippets
* Is pricing monthly? Doesn't say.
* A slightly more usable Free tier might entice more trial sign-ups.
* Another tier between Free and Candle would probably fit more freelancers and small teams.
Re: Show HN: FireHydrant – A simple incident response tool
#8Re: Show HN: FireHydrant – A simple incident response tool
#9Congrats on the release.
Looking at this, it’s difficult to determine how it’s different or why it’s better than PagerDuty, OpsGenie, or VictorOps. The page talks about a close integration with Slack, but it’s unclear what problem that solves for me wrt incident management. Note keeping / scribing is one part of incident management, but theres also:
- mustering. Getting other SMEs on the call. Both knowing who to page and actually paging them are two important problems.
- triage. Quickly knowing the severity of an incident.
- context. Sorting through all of the incoming data and metrics to find the cause.
Does this tool help with those?
From what I recall about VictorOps, they started out with a similar thesis to incident management and focused on chat / mobile / collaboration out of the box. I don’t know if they validated their hypothesis, but their marketing material did change in recent years to cover other aspects of incident management. I take that as evidence that the chat piece alone wasn’t sufficient.
Final thing I’d recommend is making it easier for potential customers to self select on your home page. Right now you’re targetting the IM market at large with “Things break. Be ready.” Is that your customer though? Any sized organization? Could you take on a 500 user company? 1000 person? Maybe something like “we help small businesses manage incidents”.
“come fight fires with us” makes it sound like your team is actively helping resolve my incidents.