Autoheal's agent-fixing agents still need an engineer to approve every change

At Nomura, the work Autoheal took over starts in an alert queue. "Our production operations teams spend valuable time triaging alerts and managing incidents, while also pulling engineers away from their software development activities," said Sameer Jain, the bank's CIO for wholesale ^[4]. He gave speed and location as the reasons it fit: "Autoheal gives us a platform that takes investigation timelines down from hours to minutes. The fact that it runs entirely within our own cloud, in compliance with our controls, made it a natural fit for how we operate," he said ^[5].

The pitch around that quote is wider. Autoheal says off-the-shelf point agents failed to deliver at Nomura and AvidXchange ^[3]. It also says repetitive work such as incident response and vulnerability remediation takes more than a third of an engineering team's capacity ^[16]. Both are the company's statements. Jain's words are about alert triage and where the software runs ^[5]. According to SiliconANGLE, customers including AvidXchange and Empiric Earth say they cut incident resolution times and saved thousands of hours of engineering work ^[12].

In a "self-improving software factory" ^[1], a platform engineer opens a pull request the Healer wrote against an agent's configuration, already checked against historical benchmarks for regressions ^[7], and decides whether to merge it. Autoheal says engineers widen agent autonomy as agents prove reliable ^[14]. The Evaluator's evidence for that reliability arrives downstream of the work. A caused incident, the most serious of its signals, can only be counted once code is in production ^[6].

Sid Choudhury, Autoheal's co-founder and CEO, frames the problem as upkeep. "Our experience taught us that while building the first version of an AI agent is easy, scaling it consistently across the enterprise SDLC is the real challenge," he said ^[9]. He said the product lets platform engineers "immediately step into the role of AI engineers and accelerate ROI, without spending a year building the underlying infrastructure" ^[10]. The idea came at Harness, where he and his co-founders saw the need to "manage agents as code, overseen by continuously learning meta-agents," he said ^[13]. Autoheal says its goal is lower cost per successful task, along with higher accuracy and faster execution ^[17]. The announcement does not include a price, a deployment time, or any customer's cost per task.

I'd sort a team on two axes: how many agents already work its delivery pipeline, and whether production access has to stay inside its own cloud. One agent, data free to leave: a point tool is simpler to evaluate, and a shared context graph has little to share ^[11]. One agent, data kept in-house: self-hosting is the reason Jain gave ^[5], and the Healer's queue stays short. Several agents, data free to leave: the scaling problem Choudhury describes applies ^[9], and the open question is who owns the reviews. Several agents, data kept in-house: Autoheal's private-cloud deployment was built for this buyer ^[11].

In every quadrant, I'd score a pilot on cost per successful task with approval hours counted in. Every behavior change the Healer proposes waits for an engineer ^[8].