Freshworks has acquired Robusta Dev Ltd., an AI-powered incident intelligence engine, in a move to bring automated root-cause investigation into its Freshservice IT service management platform.
Key Takeaways
- Freshworks has acquired Robusta, an AI incident-investigation engine, to strengthen Freshservice’s root-cause diagnosis and prevention capabilities.
- Robusta’s AI agents investigate monitoring data, infrastructure telemetry and recent code or configuration changes to pinpoint the cause of an outage before a human responder begins work.
- The deal connects Robusta’s diagnostics with incident orchestration platforms like FireHydrant, aiming to cut mean time to resolve (MTTR) and prevent repeat disruptions.
From Reacting to Outages to Preventing Them
Robusta functions as an always-on AI site reliability engineer: when an anomaly occurs, its AI agents immediately investigate monitoring data, infrastructure telemetry and recent code or configuration changes, then map the blast radius across dependent services before recommending remediation within customer-defined guardrails. Responders start with a diagnosis already under way rather than piecing together logs and dashboards from scratch.
“LLMs are fantastic at troubleshooting incidents. Our technology lets AI agents do that effectively in large enterprise environments, where there are so many raw events that investigating each one individually would be exorbitant from a token cost perspective. We’re incredibly excited to join Freshworks, which gives us the scale and platform to bring that experience to engineering teams everywhere, while keeping humans firmly in control of decisions that touch production,” said Natan Yellin, co-founder and CEO of Robusta.
Connecting Diagnosis, Response and Prevention
Bringing Robusta into Freshservice, and aligning it with incident orchestration platforms such as FireHydrant, is designed to create a continuous operational lifecycle: contextual investigation that draws on Freshservice’s business service data and change histories, diagnostic evidence that flows directly into incident timelines and Slack or Teams command channels, and post-incident data that automatically updates change-enablement guardrails to harden systems against the next disruption.
For IT and engineering teams, Freshworks says the combination should cut through alert noise, accelerate mean time to assemble and resolve incidents, and turn recognised incident patterns into automated pre-flight checks — without slowing release velocity.



