"It's an open secret that every company is on fire," said Kintaba co-founder John Egan. "At every moment, something goes terribly wrong in a way that has never happened before." Downtimes due to code errors, server failures and hack attacks affect engineering teams. But the tools that can be used to wake up the right people, put together a team, and fix the problem to assess how to prevent the problem after death can be as messy as the crisis.
Text messages, Slack channels, Task Manager and Google Docs are not enough to learn from mistakes. Warning systems like PagerDuty focus on the quick response, but not on the educational process as a result. Finally, with today's launch of Kintaba, there is a more holistic incident response solution.
The Kintaba team experienced this pain firsthand while working on Facebook after the data transmission startup Caffeinated Mind, supported by Egan and Zac Morris Y Combinator, was discontinued in 2012. Years later, they tried to build a blockchain startup, and the whole stack was constant. In flames, they longed for a better incident tool. So they built one for themselves and named it after the Japanese art of Kintsugi, which uses gold to fill cracked pottery "that teach us to accept the imperfect and appreciate the repaired," says Egan.
With today's launch, Kintaba offers a clear dashboard in which everyone in the company can see which main problems have occurred and who is reacting how. Live activity log from Kintaba With Collaboration Space for Responders, they can discuss and analyze their remedial actions. It integrates with Slack and allows team members to subscribe to different warning levels or search for problems with categorized hashtags.
"The ability to turn disasters into opportunities is one of the biggest differentiators between successful and unsuccessful teams and companies," says Egan. Therefore, Kintaba does not stop in the event of a failure.
Once the fire is contained, Kintaba provides a rich text editor that is connected to its dashboard. This enables you to quickly understand what went wrong, why, what corrections have been tried, what works and how you can secure systems for the future. Its automated scheduling assistant helps teams schedule meetings to internalize post-mortem.
Kintaba's experienced team and approach to an understated but critical software-as-a-service solution raised $ 2.25 million, led by New York's FirstMark Capital.
"All of these features help Kintaba take away the annoying administrative and tedious organization associated with successful, modern incident management practice," said Egan.
Egan, Morris and Cole Potrocky met on Facebook, which is known for creating other business productivity startups based on its world-class internal tools. Facebook co-founder Dustin Moskovitz built a task management system to reduce the number of sessions he had to hold, and then converted them to Asana, which was released this week.
The trio worked on internal communication and engineering tools and the procedures for their use. "We saw firsthand how powerful these practices can be from companies like Facebook, and we wanted them to be easier to implement for everyone without having to put together a set of tools," said Egan. He co-founded Facebook's corporate collaboration suite Workplace, while Potrocky built technical architecture there and Morris became Uber's security manager for mobile devices.
Like many blockchain projects, Kintaba's predecessor, the Crypto Collectibles wallet Vault, proved to be a technical nightmare with no clear match with the product market. So the team let go of it and built the internal alerting tool they had been working with. This original story sounds very similar to that of Slacks, which started out as a game company that turned its internal chat tool into a business.
What is the difference between Kintaba and using Slack and email or a monitoring tool like PagerDuty, Splunks VictorOps or Atlassians OpsGenie? Here's how Egan cancels a sit down time situation treated with Kintaba:
"You are on call and your pager is going up because all your servers are out of data. You are overwhelmed and the root cause could be one of the many systems that send you alerts. With Kintaba, you are not on your own. You declare a high-severity incident and the system creates a collaborative area that automatically adds an experienced IMOC (incident manager on call) and other relevant incidents on demand.Kintaba also posts on a company-wide incident slack channel to resolve the issue directly in the incident collaboration or in Slack while keeping stakeholders informed by directing them to the Kintaba incident page instead of sending update emails post stuck comments and #tags, and once the incident is resolved, help Kintaba to postpone what went wrong, how it was fixed, and what is being done to prevent it. Kintaba then automatically distributes the post-mortem and creates an incident check in your calendar. "
Instead of panicking an employee about what to do until the team struggles to coordinate across a number of fragmented messaging threads, Kintaba runs a smooth incident reporting and discussion process. And if there's a security breach that a non-engineer notices, he can trigger a Kintaba warning and put the legal and PR team together to help too.
Alternatively, Egan describes downtime Fiasco that he would experience without Kintaba:
On-call duty must begin to wake up its management chain to find out who needs to be involved. The team may throw a slack channel together, but since there is no common high-severity incident management system and so many teams are affected by downtime, other teams also throw slack channels together, email threads run everywhere and in several groups people try to solve the problem immediately. The engineers approach each other and the sales teams begin emailing managers who want to know what's going on. Once the problem is resolved, no one thinks about writing a postmortem, and even if it does, it will only be distributed to a few people and will not be saved outside of this email chain. Managers blame each other and point their fingers at people rather than reviewing the process that led to failure. In short: panic, thrash and poor communication.
While monitoring apps like PagerDuty does a good job of pointing out a problem, they are weaker in the collaborative solution and in the post-mortem process, and are designed only for engineers and not for everyone like Kintaba. Egan says, "It's like comparing the difference between the warning lights on a machine part and the big red emergency button in a factory floor." We are the big red button. , , This also means that you don't have to tear out PagerDuty to use Kintaba as this can be the trigger that starts the Kintaba flow.
However, Kintaba has to prove that it is so much better than a shared Google Doc, an adequate replacement for surveillance solutions, or a necessary add-on that companies have to pay $ 12 per user per month. PagerDuty's deeper technical focus put it on the stock market a year ago, though it has since dropped about 60% to a market cap of $ 1.75 billion. However, customers like Dropbox, Zoom, and Vodafone rely on SMS incident notifications, while integrating Kintaba with Slack may not be enough to wake up encoders when something catches fire.
If Kintaba succeeds in resolving incidents with today's launch, the team of four will see neighboring markets in prioritizing tasks, sharing knowledge, observability, and team collaboration, even though they would take on some massive competitors. If this is not possible, Slack or Microsoft teams could be a suitable soft landing for Kintaba and bring more structured systems to deal with serious problems on their communication platforms.
When asked why he wanted to build legacy software that might seem a little boring at first glance, Egan concluded that “companies that use Kintaba should learn faster than their competitors. , , Everyone deserves to work in a culture that is strengthened by failure. "