Search company, investor...

Founded Year



Seed VC | Alive

Total Raised


Last Raised

$2.25M | 4 yrs ago

About Kintaba

Kintaba is a modern incident management platform that makes it easy for teams and companies to respond to, collaborate, track, and self-repair during major incidents and outages.

Headquarters Location

1202 Lexington Ave Suite 126

New York, New York, 10028,

United States



Latest Kintaba News

Kintaba Creates the First Conference Dedicated to Incident Response – Techstrong TV

Sep 13, 2022

John Egan, Co-founder and CEO at Kintaba , talks about IRConf, the first conference fully dedicated to Incident Response . The company behind the conference is Kintaba — a modern incident management platform for the entire organization. The video is below followed by a transcript of the conversation. We have got another segment for you here. I’m happy to be joined by John Egan. John is the CEO of Kintaba Incident Response. Hey, John. John Egan: Thanks, Alan. Good to be here. Alan Shimel: Nice to have you. So, John, you know, I might have messed up what your position with Kintaba is. John Egan: That’s right. CEO and Co-Founder. Alan Shimel: Okay. And you know what? I mean I’ve heard of Kintaba, but that doesn’t mean our audience knows Kintaba, so if you wouldn’t mind, give us maybe a quick little background on Kintaba and maybe a little bit of your own background? John Egan: Yeah. So, Kintaba is an incident response platform. We’re designed to let any organization be able to easily implement best practices for responding to critical moments within the company, so this tends to be things like site outages, major customer issues, and other sort of technical and non-technical problems that require kind of a group real-time response, you know, separate from like project management where you might have planned things that are happening. You take, like, the outage that happened, I think yesterday, at GitLab was a good example, right? Or a slack outage like that, that has an incident response team that’s responding to that situation and making sure it gets fixed quickly, and they’re probably using some kind of tool, either internally or off the shelf, and we’re that tool that any organization can implement in minutes instead of bringing in a consultant and spending months on this kind of stuff. Alan Shimel: Absolutely. You know what was interesting, John, is I mean look, I’ve seen, for whatever reason since I’ve started eight years ago, incident response has always been like this, you know, it’s part of the DevOps story, and we’ve seen of course, you know, several companies have very successful exits and be, you know, very successful. They all kind of follow this pattern where they, you know, were replacing the beeper, then they became incident response. Then it becomes a whole platform, and APIs and integrations, and so forth. What makes Kintaba different? John Egan: So, we’re really purists on the incident response side of things. I think a lot of organizations that come into this space end up either kind of pivoting over towards alerting, all right, which is sort of Pagerduty’s world –  Alan Shimel: Right. John Egan: Which is more about automated detection, ping someone, it gets closed out, you know, you might get thousands of these things across the organization, or they go broad and start to become, you know, more of like an SRE platform to try to handle all of these different things that the site reliability engineers are really managing inside of the organization. But we really believe that incident response stands on its own as a practice that cuts across all of the organizations inside of your company. So, something unique about Kintaba is normally when you’re rolling it out within the organization you might start small. You might start with five or six seeds, a couple of people in SRE, but really rapidly we tend to get deployed across the entire organization and what we do really well is we’re a collaborative layer that helps everyone from customer success, to your SREs, to even your PR and marketing guys all be connected during these critical moments and all have one place that they can go to see what’s happening and participate in that response. It’s a bit more of, you know, we call it an evolved sense of incident response, right? Versus kind of the old-fashioned way of looking at it, which might be two or three people in your SRE team are responsible for this. It’s really more about the entire community of your organization that responds to these company critical moments and building software that makes it easy for all of those people to participate. So, we’re a very non-technical feeling piece of software. We’re very human driven, everything from our reporting, to our collaboration experience, to the way you go and write documents, which is a new feature we’ve just released, all of this information is designed to be as easy to use as something like Google, as opposed to being, you know, more like a, you know, almost like a service now, kind of like complex enterprise implementation. Alan Shimel: Got it. Good stuff. And, John, we’re going to talk about this conference you guys are putting on, but before we go, before we dive into that, you know, so we understand what Kintaba is. You know, in your go-to market here what are you guys finding? What are you seeing? You know, what’s kind of the state of the market, if you will? John Egan: So, we’re really learning a lot about this community as it’s just starting to form, right? I think when communities are young and they’re new you actually find the best practices are pretty fluid and I think it’s one of the unique things about this space is Google put out a book back in 2016 where they sort of defined how they handle incident response internally. It was the first time anyone really wrote it down in a way that could be absorbed, but it turns out every organization has a slightly different attitude that they take towards this space and when you’re implementing a product, something like Kintaba, it really turns out that that product has to be pretty flexible on its way in to make sure that it’s easy for people to adopt, and then it also has to bring with it sort of almost like a light hand to say these are the very high-level macro steps you’re going to take to be successful, right? And so, what we’ve learned early on is when Kintaba first launched, you know, over a year ago, we were very rigid about the way that you sort of had to come in and step through, you know, each part of incident response. What we’ve really learned and what the products evolve towards is to have rigidity around the high level steps report openness around visibility to when incidents are happening, like easy to use collaborative spaces, post mortems that editable and changeable, but also, be flexible in terms of who’s getting access to this thing, how are you giving people titles that are non-technical in the, like, customer success roles, you know, and in the marketing and PR roles, and how do you bring all of that together at once. We thought when we came in that, okay, maybe this would be a couple of seat experience for people, you know, you come in and maybe you need two or three seats, greater, four or five, and what we’ve really learned is these are company practices, like I was saying before, and I think that’s been kind of our big learning about the space is as the community grows this is really a cross-functional community inside of organizations rather than just a technical practice inside of DevOps and I think that’s really exciting. Alan Shimel: Yeah. Absolutely. Absolutely. So, John, you guys are coming in behind the first dedicated incident response virtual conference coming up in April. Why don’t you – well, I already said it I guess, but why don’t you take it from there? Tell us more. John Egan: Yeah. So, IR Conf, or Incident Response Conference, was really built out of the fact that we just couldn’t find another one to be part of that was focusing purely on the incident responder. When we talk about communities internally, you know, you think of communities as what makes people put their hands up and say, “I’m part of that,” right? I think DevOps, and SRE, and a lot of these spaces have done a good job, right? We have crowds and people will say, “Okay. I’m part of that.” Incident response has always  been one of those ones where I think people sort of nervously said, “Well, I think I’m part of that.” What IR Conf really does is it focuses not on sort of that statement of I’m in the incident response department, but instead focuses on the idea that I’m a responder, right? I’ve been part of responding to a major incident and when you ask that question it turns out a lot of hands go up and it turns out that there’s a community there that’s really looking for other practitioners to come together and talk about these things I was just talking about, right, best practices, right? What are other companies experiencing? How are we defining this role and the people who are involved? And so, what’s really cool about this conference is we get to focus really directly on that incident response process, you know, not even necessarily as it relates to other parts of DevOps, but just how we deal with this very specific problem that faces all organizations. So, I’m really excited we have one our keynote is Emily Freeman, who’s out of AWS –  Alan Shimel: Sure. John Egan: And has done all kinds of great talks about kind of the wider, softer development lifecycle inside of DevOps, and here she can speak much more directly, you know, to this response, incident response space. I think you can see the excitement around it. You know, we have sponsors, basically everyone across the DevOps world, Honeycomb, Commodore, Rookout, BridgeCrew, Gremlin, Teleport. All of these folks, you know, really came running in and said, “Yes. This is great. We need a space to come in and talk to our sub-communities that are already using our products that care about this space,” and so really, we just felt like there was a hole in the market and so this is a free conference. Anyone can join. This is a virtual conference. It’s on April 1st. It’s at IRCONF.IO if you’re out there looking for it. We’re really hoping to just get everyone to come along who’s ever been involved in an incident before and has experienced that fire moment inside of a company of, you know, hopefully not panic, but maybe panic, and wants to come together and talk to other folks, who have had the same experience. Alan Shimel: Sure. I’m thrown back to my cyber – we didn’t call it cyber then – to my infosec days in the war room, you know, when stuff hit the fan. You know, best practices that were to set up a war room on how to respond to a breach, you know, some sort of attack. John Egan: And that’s really where a lot of this grew out of, right? Alan Shimel: Sure. Alan Shimel: Yeah. John Egan: And it’s one of these parts of the evolution of the space, right, that now we’re adopting, you know, that process that really got its feet inside of the security incident response space across the organization to say, “Wow. These guys are doing a great job,” like, “We should be doing similar work across the org.”  Alan Shimel: Not all companies had such a great job on their war room, but that’s a whole other story. Hey, John, you mentioned Emily Freeman speaking. Who are some of the other speakers? John Egan: We’ve got two more who are announced right now and it’s Emily Freeman, and it’s Dave Rensin. Dave Rensin was previously at Google and ran a good chunk of the SRE Team there. He’s at a new organization now and he’s spoken at a couple of other conferences in the DevOps space, specifically about the process of incident response. I’m really excited about him being able to come in as well and talk, both, from a large company standpoint, right, a company like Google, where he really pushed a lot of customer metrics, right, for dealing with incidents, not just internal technical metrics, as well as the smaller company, like where he’s moved to now is a startup. Those two are kind of our cornerstones. Then we’ve got a series of other speakers, who are announcing over the next couple of weeks –  Alan Shimel: Who? John Egan: Who are coming in from all over industry, so I’m really excited. I’m can’t announce them here yet. They’re not finalized yet. Alan Shimel: Okay. Good. John Egan: Really exciting. Great organizations. Alan Shimel: Can’t blame me for asking. All right. Hey, John, for people who are interested, that was IRCONF.IO? John Egan: That’s right. IRCONF.IO. You go in there and just click Attend and register. We’re still at early bird, so everything is free right now. Alan Shimel: And it’s April 1st. Do you have times on that? John Egan: I believe we’re planning to start it early, around 8:30 is the beginning of it. Alan Shimel: East Coast time? John Egan: It’s technically a half-day, but it runs until about 2:00, I believe. Alan Shimel: So, that’s East Coast time though? John Egan: East Coast time. Yes. Alan Shimel: Yep. We’ve got a global audience here, so that’s East Coast U.S. time. John, sounds great. You know, if there’s a need in the market, you know, the market has a vacuum, so it’s good to see it getting filled here. I want to wish you the best with it, with the conference and with Kintaba. John Egan: Great. Thanks, Alan. Alan Shimel: It was great having you. John Egan, CEO, Co-Founder, Kintaba, the folks behind IRCONF and you can find out more about that at IRCONF.IO. That’s coming April 1st. Check it out. We’re going to take a break here on Techstrong TV and we’ll be right back. Recent Posts By Alan Shimel

Kintaba Frequently Asked Questions (FAQ)

  • When was Kintaba founded?

    Kintaba was founded in 2019.

  • Where is Kintaba's headquarters?

    Kintaba's headquarters is located at 1202 Lexington Ave, New York.

  • What is Kintaba's latest funding round?

    Kintaba's latest funding round is Seed VC.

  • How much did Kintaba raise?

    Kintaba raised a total of $2.25M.

  • Who are the investors of Kintaba?

    Investors of Kintaba include FirstMark Capital.

  • Who are Kintaba's competitors?

    Competitors of Kintaba include Jeli and 4 more.


Compare Kintaba to Competitors

Rootly Logo

Rootly develops an incident management platform and Slackbot designed to help companies resolve incidents faster. It automates manual admin tasks and offers status pages, incident retrospectives, metrics, integrations, and more. The company was founded in 2020 and is based in San Francisco, California.

Torq Logo

Torq offers a no-code automation platform for security teams. It enables users to connect security infrastructure and communication tools, automating workflows across these systems. It was formerly known as StackPulse. It was founded in 2020 and is based in Tel Aviv, Israel.

D3 Security Logo
D3 Security

D3 Security is a company that focuses on security orchestration, automation, and response in the cybersecurity industry. The company offers tools that aid in managing security operations, including incident response and case management, and it uses automation to transform these operations. Its primary market includes enterprises, Security Operations Center (SOC) teams, and Managed Security Service Providers (MSSPs). It was founded in 2004 and is based in Vancouver, British Columbia.

Tines Logo

Tines develops a security automation workflow for businesses. It enables security teams to automate any workflow and integrate with technological stack tools. It provides no-code software development kits (SDKs), pre-built templates, and more. The company was founded in 2018 and is based in Dublin, Ireland.

Exabeam Logo

Exabeam provides security intelligence and management solutions. It offers a way for security teams to approach threat detection, investigation, and response (TDIR) and also offers security log management, security analytics, security investigation, and more. The company serves financial services, healthcare, higher education, manufacturing, government, and other sectors. It was founded in 2013 and is based in Foster City, California.

DTonomy Logo

DTonomy operates as an artificial intelligence (AI)-based security operation platform. It offers solutions for reducing investigation time and eliminating the risk with AI-based analysis and response tools for security analysts. It provides tools to manage pattern discovery, adaptive learning, recommendations, manual context stitching, and false positive patterns. It was founded in 2018 and is based in Cambridge, Massachusetts.


CBI websites generally use certain cookies to enable better interactions with our sites and services. Use of these cookies, which may be stored on your device, permits us to improve and customize your experience. You can read more about your cookie choices at our privacy policy here. By continuing to use this site you are consenting to these choices.