Software — Theralon
The operating system for operational risk and assurance.
Vigil keeps watch over what an operation is exposed to. It sifts hundreds of signals into the few concentrations of risk that genuinely matter, shows the evidence and confidence behind every figure, and holds a record of what was believed, decided and done that cannot quietly change.
Built for owners, leadership, finance and risk — the people who answer for the operation.
Built around your data, your systems and how you actually operate, at whatever size the operation is.
In the risk register
With Vigil
Hundreds of signals consolidated into the concentrations that would actually cost you.
Every number carries its sources and a stated confidence. Nothing is taken on trust.
What was believed, decided and done, kept exactly as it stood on the day.
Reports drawn from the record, for any date, in the format they ask for.
Inside Vigil
01 — Escalate
When an exposure crosses your risk appetite, Vigil routes it to the person accountable for it, with what is happening, why, and what it would cost.
02 — Own
Each item is acknowledged, assigned and given a treatment, reduce, transfer, avoid or accept, with a due date and a next review. The trail records each step.
03 — Oversee
Exposure across the register, the severity and likelihood matrix and every breach of appetite, so a risk committee sees what it needs and nothing it doesn't.
04 — Assure
Certificates and policies coming due, external factors and owners, and the full register generated as a formatted report in PDF, Excel, CSV or JSON.
Screens from the product, on synthetic data.
Two questions
Vigil does. It consolidates the signals into the few exposures that matter, ranked by what they would cost.
Theralon does. Terra reconciles the records into one view, with the source of each, and every figure Vigil builds on them can be questioned down to that source.
How it works
Vigil keeps watch over the whole operation for what it is exposed to: suppliers, routes, assets and sites, and what depends on each.
It consolidates many signals into the few concentrations of exposure that matter, ranked by consequence rather than by volume, and checks whether each problem is in the operation or in the data describing it.
It keeps the evidence, the decision and the outcome as one record, so any figure or choice can be explained later to a board, an auditor, an insurer or a customer's quarterly review.
Exposure
Risk attaches to the entities that actually carry it. When three apparently unrelated supplier risks trace back to one sub-tier facility, Vigil recognises a single concentration and counts it once — weighted by what depends on it and how long an alternative would take. The register shows what the operation is exposed to, not how many alerts it produced.
Inside Risk Protection →
Capabilities
Exposure collapses many alerts into the underlying concentrations, ranked by consequence rather than by volume.
Supplier dependencies traced through the network to the single source nobody had written down, and the lead time to replace it.
Every figure carries its sources, its model version and a stated confidence, and shows which part of the reasoning is holding it back. A feed that goes quiet is reported as a gap in the evidence, never read as an all-clear.
Every change to the model, the register and a decision is kept in one tamper-evident history, so any item can be traced back to what was recorded on the day.
What a seven-day supplier failure or a sudden surge would do, which exposures it turns into losses and from which date, answered against the live model rather than a spreadsheet copy of it.
Strict isolation, access scoped per person, a deployment region named before any data moves, and no external model calls.
What Vigil keeps watch over
Works with what you run
Vigil reads what your systems already produce and holds the exposures, the evidence and the decisions as one record. Nothing the operation depends on is touched.
Imperfect data is fine.
Every organisation's model is held in strict isolation, in a deployment region named before any data moves, with access scoped per person. No external model calls.
What changes
Risk counted alert by alert
Exposure counted once, at its source
Numbers taken on trust
Numbers questioned down to their source
Decisions explained after the fact
Decisions recorded as they are made
How to start
Show us where the operation breaks down. We build Vigil around the systems you already run and show you the few exposures that would cost you, each traced to its source. Then compare it with what you run today.
Your data
Questions
A register lists risks people have written down. Vigil derives exposure from the live operation, recognises when separate risks share one source, and keeps the evidence behind every figure.
Owners, leadership, finance and risk: the people who answer for the operation to a board, an auditor, an insurer or a customer, and have to show how each decision was made.
Every organisation's model is held in strict isolation, in a deployment region named before any data moves, with access scoped per person. Questions are answered without sending data to any third-party model.
Show us where the operation breaks down. We build Vigil around the systems you already run, show you what it sees on your own operation, and you compare it with what you run today.
Nothing while we work with you, for the foreseeable future. You see what the software does on your own operation first. When it has shown its value there, we agree terms with you, sized to what you run, and nothing becomes a contract until you agree to it.
Because the software is best judged on your own operation, not on our word. It isn't a trial or a pilot: you see what it does on your own data first, and when it has shown its value there, we agree terms with you.
Terms are agreed only after you have seen what the software does on your own operation. They are sized to what you run: how much of the operation the software covers, the volume and the number of sites, not the size of Theralon. You start with the product that fits the problem in front of you and add the rest when it has earned it. Nothing becomes a paid contract until you agree to it. The same software runs owner-led operations and large ones alike.
No. We build around the operation in front of us, at whatever size it is, and it costs nothing while we work together.
Also from Theralon
Terra
Vigil watches what the operation is exposed to. Terra is where it is run.
Explore Terra →