← Use cases & case studies

Case study · Self-healing · Customer zero · Ayurak, on its own platform

Two out of three fixes never touched production

Aribot's self-healing proposes a fix for a cloud or design finding, runs it as a dry run, waits for approval and checks the result after it applies. On our own platform, 49 of 73 remediation runs stopped at the dry run. Of the 24 live runs, eight were applied and verified and three failed. Thirteen from February never finished; we checked every resource they targeted before closing them.

Download as PDF
49 of 73

remediation runs that were dry runs only, February to September 2026

8

live fixes applied and then verified against the resource

3

live fixes that failed and were left open, not marked fixed

The situation

Automatic remediation is easy to demo and hard to trust. The risk is not that a fix fails. The risk is a tool that reports a fix as done when the resource never changed.

We ran self-healing on our own estate to see what it does when things go wrong, not only when they go right.

What we built

Dry run first, every time

Each fix is planned and rehearsed before anything changes. The dry run shows what would be touched. Most of our runs ended there, because the dry run answered the question.

Approval before a live change

A live run waits for a person to approve it. Nothing applies on its own.

Verify after applying

After a live change, Aribot re-reads the resource. A finding closes only when the resource agrees.

Failures stay visible

When a fix fails, the run stays failed and the finding stays open.

Results

  • Of 24 live runs, 8 were applied and verified, and 3 failed and stayed open until they were reviewed.
  • Thirteen live runs started between 14 and 21 February never reached a final state. Before closing them we re-read every target, read-only: seven resources no longer existed, two still lacked the change the run had targeted, one cluster was stopped, and three sat in a project with billing switched off.
  • Each of those runs is now closed as abandoned, with what we observed written into its record. None was marked as fixed.
  • Remediations with no cloud account, such as design-level fixes, now reach the company that owns them. Before 30 September they were invisible to that company's users.

Next

Still to do: flag a run as stalled automatically when it has not moved for a set time, so no run waits months for someone to notice.

Related use cases

Customer zero: this is Ayurak running Aribot on its own platform. Every figure comes from our own workspace, counted on 1 October 2026 and updated on 2 October after the stuck runs were checked. Products: Cloud Security & Digital Twin.