How it works · HelioStack

[ How it works ]

The journey of one problem

From a sentence in a chat window to a fixed server, a record you can review, and a fix kept for next time.

[ What it's like ]

Describe it, HelioStack handles it

A conversation that ends in a fixed server: it finds the cause, proves a fix, gets it approved, fixes it and tells you.

[ Changing a server ]

From a fix to a safe change, and back

The same journey for a fix, with the stops that make a change safe: proof, a second person's approval, a backup first, a health check after, and the undo ready. It runs twice: once with a fix that doesn't hold, then with one that works.

[ Proving ]

Tested before it touches

The fix runs first on an isolated test server built from a clean image. Then, where your rules allow, on a disposable copy of the real server, with no network, deleted afterwards.

HelioStack compares before and after. If the fix did anything it didn't say it would, it goes no further.

When a test catches something The fix said it would change two things. It changed three.
Files As described One file moved to a quarantine folder
Services As described One job stopped and run again
Settings Not described A scheduled task was turned off

Not proven. The fix goes no further, and nobody is asked to approve it.

[ Approving ]

Who approves, and what they see

A person named by your rules signs off every new fix before it reaches a real server.

  • A second person

    Named by your rules. Not the person who asked.

  • Two people

    For bigger production changes.

  • Never the AI

    HelioStack can ask for approval. It can never give it.

What the approver sees
  • The problem and its evidence
  • The fix's script, in plain language and in full
  • What it will change
  • The proof from the test area
  • The backup and undo plan
  • Who asked

[ Learn ]

Trust is earned

HelioStack only works on its own where it has proved itself, and one failure takes that away.

Running fixes on its own: coming later

[ Who does the work ]

One lead agent, specialists behind it

You talk to one assistant. It calls specialists for writing scripts, research, summarising and reviewing, and stays in charge.

Specialists can advise but never act. Work is always checked by a different AI model from the one that wrote it: two different AI model families check each other.

The lead agentTalks to you · plans · stays in charge
  • Writing scriptsAdvises only
  • ResearchAdvises only
  • SummarisingAdvises only
  • ReviewingA different AI model
None of them holds keys to your servers.
NextSafety by design →