If you run Robusta's AI SRE or self-host HolmesGPT, your vendor is now part of an ITSM company, and the announcement gives you no answer on pricing, product continuity or the open-source project. Freshworks said on October 28 that it has acquired Robusta Dev Ltd. and will build Robusta's incident investigation into Freshservice and FireHydrant. Terms were not disclosed. The post does not mention HolmesGPT, the Apache-2.0 agent Robusta created, and gives no timeline. The decision in front of you is whether to follow Robusta into a Freshworks bundle, pin the open-source agent you already run, or use the uncertainty to re-price against Datadog and the other AI SRE vendors.
An AI SRE agent is software that picks up an alert, queries your monitoring, logs and recent deploys on its own, and returns a probable root cause with evidence. Robusta sells one. Freshworks now owns it.
What Freshworks Actually Bought
Freshworks bought an incident investigation engine plus the team that maintains the most visible open-source agent in the category. The announcement describes Robusta's product as three steps: agents investigate telemetry and recent code or configuration changes when an anomaly fires, identify the root cause and blast radius, then recommend remediation "within customer-defined guardrails," with engineers approving anything that touches production. Co-founder and CEO Natan Yellin is quoted saying "LLMs are fantastic at troubleshooting incidents." Yellin and co-founder Arik Alon join Freshworks.
Robusta was founded in 2021 in Israel and lists customers including Playtika, Betsson, NetApp, Bottomline, Fireflies.ai and Infineon. Its own site adds Absa, Jedox, OpenSpace, AB Lindex and Cynet, and says the product runs as SaaS, inside your VPC, or fully self-hosted, with your own LLM keys. It claims SOC 2 compliance, read-only access by default through IAM and RBAC, and no training on customer data. Pricing is quote-only; there is no public list price to compare against a Freshworks one.
The stated plan is all about integration into Freshworks' own products. Freshworks says it will use Freshservice's CMDB dependencies and change history to steer investigations, push findings into FireHydrant incident timelines and Slack or Teams, and feed post-incident data back into Freshservice change guardrails. Every customer benefit in the post (fewer duplicate alerts, lower MTTA and MTTR) is an expectation with no figure attached.
Why This Is Freshworks' Third IT Ops Deal of 2026
Freshworks is assembling an ITSM, incident and AIOps stack piece by piece. It closed FireHydrant on January 1, 2026 for $88.7 million in cash, including $4.3 million of acquired cash, with $51.3 million booked as goodwill. On October 12 it agreed to acquire Torii for SaaS and AI spend governance, expected to close in its fiscal fourth quarter. Robusta is the third.
The pattern points at ServiceNow's turf: a CMDB, change management, incident response and now automated root cause analysis, sold as one Freshservice story. Freshworks reported Q2 2026 revenue of $237.4 million, and it announced plans to cut about 11% of its workforce, roughly 500 people, earlier this year to push AI into product work. It reports Q3 results on November 3, after the close. That call is the first place management may say what Robusta costs and how it will be packaged.
We covered the Torii deal when it was signed: Freshworks to Acquire Torii for AI and SaaS Spend Governance. The same continuity questions apply here, with an open-source wrinkle Torii did not have.
What Happens to HolmesGPT
HolmesGPT stays Apache-2.0 and stays in the CNCF sandbox, but the people who maintain it now work for Freshworks. The repository describes it as an open-source agent that investigates production incidents, "originally created by Robusta.Dev, with major contributions from Microsoft," with built-in toolsets for Kubernetes, Prometheus, Grafana, Datadog, Loki, the three big clouds, PagerDuty, OpsGenie and more. It was accepted as a CNCF sandbox project in October 2025, and the CNCF blog post announcing it was co-written by Yellin and a Microsoft product manager.
The maintainer list is the number that matters. Of the 12 current maintainers in MAINTAINERS.md, 11 list Robusta as their affiliation and one lists Microsoft. As of today, the project's direction is effectively set by one company's engineering team, and that team's priorities now come from Freshworks.
The steel-man case is reasonable. Freshworks has every reason to keep HolmesGPT healthy: it is the top of a funnel into Freshservice, CNCF sandbox status brings community contributions, and Microsoft's contributions suggest at least one other large company depends on it. The project was shipping fast before the deal: release 0.45.0 was tagged October 15, its fourth release since mid-September.
The risk is the familiar one. When an acquirer owns the maintainers of an open-source project that feeds its commercial product, new features tend to land first, or only, in the paid tier. We saw the same question when Nscale bought Anyscale: Ray stayed open, but the control plane above it did not. Robusta already runs two open-source repositories beside its commercial product. Its older Robusta Classic repository (MIT licence) handles Prometheus alert enrichment and points to HolmesGPT for AI root cause analysis.
What It Means if You Run PagerDuty, incident.io or Rootly
Robusta's neutrality is the asset most at risk. The company's site lists integrations with incident.io, PagerDuty, FireHydrant and Rootly and accepts alerts from Prometheus Alertmanager, Grafana, Datadog and CloudWatch. Today FireHydrant is one integration of four. Freshworks' stated plan is to "deepen interoperability with FireHydrant" specifically, and it says nothing about the other three.
Nobody has announced that those integrations will break. But a buyer who chose Robusta because it sat neutrally beside PagerDuty should assume the FireHydrant path will get the engineering attention from here, and should put that assumption to the account team in writing.
The cost comparison is worth running now, while you have the leverage of a vendor in transition. Datadog's pricing page prices AI credits from $500 a month for 500 credits on an annual commit, $1.30 each on demand, with no rollover, and estimates about 4 credits per autonomous Bits investigation. Robusta's own site uses a benchmark of $2.50 per investigation for a build-your-own setup and argues that alert grouping is the real saving, by cutting how many investigations you run at all. Those are vendor figures on both sides, but they give you a per-investigation number to demand from whoever quotes you next. For the wider field, see our earlier look at AI SRE agents and Resolve AI's $1.5B valuation.
What to Do Before Freshworks Reports on November 3
The action depends on which of three groups you are in.
This Week:
- Robusta SaaS customers: email your account contact and ask for four things in writing: whether standalone Robusta remains sold and supported, for how long, whether your current price holds through renewal, and whether the PagerDuty, incident.io and Rootly integrations stay on the roadmap. Then pull your contract and find the assignment and change-of-control clauses; our vendor exit clause review lists what to look for.
- Self-hosted HolmesGPT users: pin the version you run today (0.45.0 or earlier) in your Helm values or container tags, so an upstream change does not reach production unreviewed. Record which toolsets and which LLM provider you depend on.
- Security teams: confirm whether Robusta's hosted service holds any of your telemetry, and ask for an updated sub-processor list now that Freshworks owns it.
This Month:
- Listen to the November 3 call for packaging. If Robusta capability turns into a Freshservice add-on, standalone buyers will be pushed toward a bundle.
- Freshservice customers: ask your Freshworks rep when Robusta investigation reaches Freshservice, at what price, and whether it needs FireHydrant. No timeline is published, so treat any demo as preview until you have a date in your order form.
- Run one bake-off on last quarter's three worst incidents: HolmesGPT self-hosted, your observability vendor's agent, and Robusta as sold today. Score root-cause accuracy and time to answer against what your engineers found by hand.
Before Renewal:
- If you renew Robusta, negotiate a price cap and a migration window tied to any end-of-sale notice. A vendor that has just been acquired is usually willing to trade terms for retention.
The Bottom Line
Consolidation in incident tooling has a long history of turning a neutral layer into a feature of a larger suite, and this deal fits it: an ITSM vendor bought the team behind a neutral, multi-vendor investigation agent and said it would integrate with its own incident product. That can be good for Freshservice shops, which get root-cause analysis tied to a CMDB without another vendor. It is less clearly good for teams that picked Robusta because it was not tied to anyone's suite. HolmesGPT gives you a fallback, as long as you pin it and keep an eye on who commits to it. Get the continuity answers in writing before November 3.
Continue Reading
- Freshworks to Acquire Torii for AI and SaaS Spend Governance
- ServiceNow, Jira and Freshservice Ship Their Own AI Desk Agents
- An AI SRE Agent Fixed 35,000 Incidents While Engineers Slept
- Resolve AI Hits $1.5B Valuation as AI SRE Goes Mainstream
- Dynatrace to Acquire Arize for $915M to Expand AI Observability
- Ray Is Open Source. The Control Plane Above It Isn't.