KloudMate 2.0 - AI-powered Full-Stack Observability & Agentic SRE-Ops

3 years ago, we launched KloudMate on Product Hunt as an AWS serverless monitoring tool.

A lot has changed since then.

What started with helping developers understand their Lambda functions, has evolved into something much bigger, viz... a full-stack, AI-powered Observability and Agentic SRE-Ops platform built for the complexity of modern, complex and distributed systems.

From monitoring Networks, to Infrastructure, to Applications and Databases. And anything else in between.

And perhaps the biggest change is that we’re no longer just helping teams 'see' issues. We're also helping resolve them.

With KloudMate AI, teams can ask questions, build dashboards and alarms, investigate incidents, get to root cause in minutes, and even turn operational knowledge into documentation. Replete with 4 AI agents: The Assistant, the Builder, the Investigator and The Docs agent.

But the journey from serverless monitoring to AI-powered SRE-Ops wasn't a straight line. It was shaped by years of conversations with developers, SREs and engineering teams, and by constantly asking ourselves:

What if observability could do more than just tell you there’s a problem? What if it could also help you solve it?

Today, we’re bringing that vision back to Product Hunt.

If you’ve been following our journey, thank you. And if you’re discovering KloudMate for the first time, sign up for a free account, and tell us what you think.

Let's go 🚀🚀🚀

If you work with SLOs, see if the compliance and error budget views give you enough context to decide on the stuff that needs your attention.

We rebuilt KloudMate’s core around agents that work directly on your telemetry.

The Investigator can automatically investigate alerts, correlate logs, metrics and traces, group related alerts into a single incident, and drive the investigation toward root cause. The Builder turns plain-language questions into dashboards, queries and alarms.

Everything is OpenTelemetry-native, and with our MCP server, you can bring investigations directly into your editor and AI workflows.

The goal is to move beyond “here’s an alert” to “here’s what happened, why it happened, and what you should look at next.”

Would love to hear how this works on your stack and especially where it breaks.

We built the Investigator to take you from an alert to a root-cause investigation, instead of yet another dashboard to keep checking. Try it on an incident you already know well and tell us if it misses any context that you'd prefer it to have?

With KloudMate 2.0 we want incident handoffs to carry the investigation context with them, so that the next person doesn't have to start from scratch again. What would you want in front of you when you pick up an incident?

2.0 brings logs, metrics and traces into one investigation flow. Start with a slow request and see if the path from the trace to the relevant logs feels clear. That would be the real test.

Congrats on the launch!!!

Over the last couple of years we kept hearing the same thing from engineering leaders, that small teams drowning in alerts, senior people spending nights on incidents that should take minutes.

KloudMate 2.0 is our answer: Agents that do the digging so your team doesn’t have to. Would love to hear what your on-call reality looks like.

looks cool!

Yea, bouncing between logs, traces, alerts, and incident tools gets old fast. Graaats! @pranabgohain @amitava82 @bidyutbaruah @rwitesh_bera1