Who it’s for

Start from the decision you’re already trying to make.

The same underlying rating, read three ways. The buyer carries the risk and pays; the insurer recognises the evidence; the OEM embeds the standard. Pick the seat you sit in.

THE BUYER

Technical risk evidence for bankability decisions.

The party that owns or operates the asset carries the risk — and pays for the evidence. Grade the book, price the exposure, defend the number.

Portfolio concentration

See where risk concentrates before it shows up in a covenant breach.

Residual & bankability

Degradation and residual value, grounded in a validated model — not a spreadsheet assumption.

Grade movement

Month-over-month A–F movement across the whole book, per asset and in aggregate.

Scope a portfolio pilot
PORTFOLIO ROLL-UPREEF SYNTHETIC
240 assets
grade distribution · MoM ▲ +1.2
62
A
88
B
51
C
26
D
9
E
4
F
⚑ concentration flag · 2 assets slipped to D this month
Who pays for what

One buyer. Two amplifiers.

The evidence has one budget line — the party that owns the risk. Insurers and OEMs make it worth more; they don’t replace the buyer. Keeping that straight is what keeps the pitch honest.

THE BUYER
Operators & funds pays.

Owns the asset, owns the risk — so it carries the budget line for the evidence. This is the party we sell to.

RECOGNITION
Insurers recognises.

Reads evidence a risk committee can act on. Better terms are a possible outcome — never sold raw data, never a fabricated loss number.

CHANNEL
OEM & integrators embeds.

Distributes the rating as a white-label surface. One code, many partners — the standard travels through the channel.

We sell the evidence to the party that carries the risk. Insurers recognise it; OEMs distribute it. Every figure shown is decision-support on synthetic references — not a market price (DR-236).

However you arrive

Bring a data feed, a health model, a portfolio or an incident hypothesis.

We’ll scope the rating, replay or evidence-readiness pilot around the decision you actually need to defend — not around a feature list.

See the proofBring your decision →