Respond faster, see patterns, learn from your incidents
Jeli.io
Respond faster, see patterns, learn from your incidents
The Jeli.io platform allows users to respond to, manage, and analyze incidents to build more resilient infrastructure and teams. Jeli aggregates incident data across the tools and people involved to reveal clear, actionable recommendations for your org.
Automated security compliance for your business in weeks
Hey PH!
We built Jeli.io because incidents are always going to happen. But they don’t have to suck. Incidents can be opportunities to make our technology better and our lives easier. We’re a group of engineers and SREs exhausted from trying to manually find and improve all the gaps in our incident response processes. So, we built Jeli to fill the gaps in incident management and create a more positive culture of learning.
We built an incident response Slack bot to streamline processes without getting in the way; setup takes minutes, not weeks. We also made what we always wanted for post-incident reviews: a way to not only create a timeline of an incident but to tell the story of response with the words of the responders themselves using our Narrative Builder. Jeli has grown to include cross-incident analytics to help dig into theories & trends, and surface on-call needs.
Our integrations, webhooks, and APIs ensure you can get your incident data to wherever else it needs to go. We partner with our customers regularly, from enterprise groups like Indeed and Zendesk to growing badasses like Honeycomb and Quizlet, to help Jeli solve as many problems as possible, and sometimes just because we like jammin’ with ‘em.
Download our free IR bot, give our trial a go (we’ve even got a sandbox with demo incidents to play around with), and let us know what you think!
When you signup, make sure to check out your own personal demo environment! This is a great way to see an example analysis of an incident, done the Jeli way.
From its suite of real productivity tooling, which is paramount in the heat of an outage, all the way down to the language throughout the product focused on people, learning, and connections, Jeli is helping us improve our incident response even as an organization several years into a deliberate incident response journey.
I'm curious how the Jeli team uses Jeli at Jeli! Any fun stories to share?
@danehillard thank you so much! We're excited to get to work with you all to make response easier for everyone. We use Jeli quite a bit internally! We're still a small team, but part of our onboarding process is to have a new hire partner with a more experienced team member to do their first incident review in Jeli. It helps introduce new hires to our technology and people as they interview folks and run the learning review. Their perspective is invaluable as a first time user, but also because they're new to our sociotechnical system, they ask amazing questions and we all learn a ton! We also use Jeli in every single one of our incidents and as active users we've inspired a lot of our own features, like the recent addition of scheduling the archive of an incident channel after it's closed. When we say we built the tool we always wanted, we really mean it!
@em_ru Love it. I'm curious, what is the smallest thing y'all tend to create opportunities for? I know it's a balance between overhead and moving forward, but wonder if "more is better" up to a certain point!
@em_ru @danehillard internally, we use Jeli for a lot of different things besides incidents. We like to use it for gamedays, for example. We typically do gamedays in order to make sure knowledge and context are getting dispersed among our engineers to avoid having single points of failure in the org. Because it helps to write things down in order to disperse knowlege, we'll often "narrate" in Slack how things are going and what people got confused by or learned during the process. It's a great way to spread knowledge!
@em_ru @danehillard we actually did an experiment earlier this year where we did a full investigation for every single incident we had and definitely got a sense for what that point was. One challenge we had was that everyone doing an investigation wanted to do as a good a job as possible, but that meant we had a couple weeks where it felt like everyone at Jeli was interviewing everyone else all the time, which was a little bit too much. On the other hand, we learned about some really interesting patterns in our incidents by doing all of those investigations -- one thing we found was that a lot of our minor incidents that we might not normally have done a full review for were related to Apollo cache, which turned into a really good opportunity to teach the entire team about how Apollo cache works. If you get a chance to try a similar experiment I recommend it, it's a good way to build an intuition in your org about how often you should be investigating incidents.
So easy it is to set up and use. Is there a caveat to its implementation process? This is too good lol! But im excited to try it.
@amelia_william2 no caveat- you can get set up in minutes on the Free Tier! Connect to your favorite tools with our integrations (
https://www.jeli.io/integrations) and start responding. Or, get started in the sandbox if you want to play around with what post-incident analysis can look like. Thanks- we're excited for you to try Jeli.io too!
