We Raised $25Million to Redefine Kubernetes Troubleshooting

It’s been a wild ride so far and we are humbled by the great response to our vision from customers, investors and – most importantly – the Komodor team that chose to join us on this journey. It was a ‘friendship from the first pint’ and we quickly found ourselves spending days and nights brainstorming about possible business ideas, while participating in every entrepreneurship program the university had to offer. That race, we knew, almost always started with the same question: “What changed?” Trying to find the answer would end up eating hours of time as you log in and out of multiple monitoring and observability tools, CI/CD, code repositories, and communication channels… Back-and-forth and back again, looking for that needle in the (hay)stack. We quit our day jobs and within a few months raised a seed round, were joined by the first Komodorians, got an office (even though it didn’t see much use during the lockdowns), and started working on the beta. From these conversations two things became apparent: • The task of troubleshooting often fell on the shoulders of the most experienced developers and DevOps, who had an almost intuitive understanding of the system’s inner workings.