Kerno [Public Beta]

No BS application reliability for devs that just works

SaaS

Software Engineering

Developer Tools

Hey Product Hunt! 👋 I’m Karim, co-founder of Kerno, and I’m excited to share with you what we’ve been building for the past few months. A bit about our story: We started Kerno with a mission to make business application reliability effortless for every developer. Developers are crucial allies in building and running reliable software, but today, they find it challenging to contribute effectively. 1. Applications have become more complex, dynamic, and unpredictable, making it difficult for developers to navigate and understand what's happening. 2. Today's tooling stack is multilayered, heavy-duty, and noisy, which might work for Ops, SRE, and Infra teams but not for developers who need a more streamlined, focused, and lightweight approach. Kerno provides a simple way for developers and on-call teams to cut through production noise, quickly identify business-critical application issues, and resolve them independently with minimal effort. This will ease pressure on Ops and SRE teams, who have to spend less time as support agents, reduce product risk, and, most importantly, improve developer happiness by removing the chaos and frustration of production troubleshooting. Here is how Kerno works: 🔗 We collect and correlate telemetry, event, and user data from infrastructure, applications, Git, and CI/CD. 🔔 When an issue arises, we automatically detect it, prioritize it based on business impact, and notify the right people based on code commits, service ownership, and blast radius. 🎯 We then provide a fully contextualized and correlated event and telemetry data down to the broken line of code. Now, let’s talk about tech a bit 🤓 ✨ Zero code instrumentation. Our agent runs as a DaemonSet leveraging eBPF. ⚡️ Hassle-free and almost instant. Deployments in sizable clusters take as little as 30 seconds. Two commands tops (no worries, scripts, and Helm charts are published on GitHub if you want to have a look, of course) 🪶 As light as it can get. We are talking as little as 0.125 CPU and 64MiB per node depending on your nodes’ size! (currently running at < 5% CPU in our highly-stressed test environments). 🧩 Low overhead, all across. We are minimalistic with data. We collect, process, and transmit data based on events of interest (from an error being detected to a user requesting N samples). We only transmit and store data in our cloud to provide a top user experience (it’s a hybrid approach). 💵 No billing surprises. Since we don’t base our business on charging for data ingestion and storage, pricing is quite predictable, allowing us to offer you flat pricing for the service. We price the service by unique workload, ignoring replication and associated resources (like configmaps or network services). 🔐 Data is secure at all times. We capture and manage trace storage encrypted in your cluster. Relevant logs are transmitted to the user on-request through a blind encrypted tunnel to facilitate access to all features. So… that’s it for now. I’m excited to put Kerno out there, and I look forward to hearing what you think. Please drop a comment below and let me know 🙏