When software can change a setpoint, open a valve or shed load, the change needs a gate and a record.
What you can do
- Let automation handle routine operations while risky changes wait for an operator.
- Keep one record across vendors and control systems.
- Show a regulator or an insurer what was changed, by what, and under whose approval.
What you are saved from
- Changes that nobody can attribute after an outage.
- Evidence split across every vendor's own logging.
- An AI assistant acting on a system it was never meant to reach.
What it costs
Free to download and use, with nothing to sign up for. Paid work, such as a readiness review or a pilot in your own environment, is scoped to your case and priced as a fixed amount agreed before it starts. No subscription, no per-seat fee. Vaara is dual-licensed: free under the AGPL-3.0, or under a commercial licence when you build it into a product you ship closed, run a modified version as a service without publishing your changes, or your policy does not allow copyleft. Write to hello@vaara.io.
What it saves you
- Root-cause time after incidents.
- Duplicate evidence work for each regulator and insurer.
- Downtime from changes that should have waited for a person.
Every action ends in one of three states, and leaves a receipt
Allowed
Inside the rules: it goes through.
Needs a person
Unusual or risky: it waits until a person says yes or no.
Refused
Against the rules: it never happens.
Receipt
Every one of the three leaves a signed record of what was decided and why.