Hael
Sign inBook a call
About

Built by regulatory practitioners.

Hael is built on decades of hands-on regulatory practice — authorising and supervising regulated firms under FCA, EU and US regimes. We build AI governance the way regulators actually assess it, not the way generic compliance vendors model it.

Why Hael exists

The document is the obligation.

Existing GRC tools tell you which documents you are missing. They surface the gap and ask you to fix it elsewhere. That model worked when the obligation was a policy. It does not work when the obligation is a generated Annex IV technical file, an Article 27 fundamental-rights impact assessment, an ISO/IEC 42001 AIMS record, or a US Treasury FS AI RMF examination pack — substantive documents the regulator opens and reads.

Hael creates those documents and runs the controls behind them. The classification, the control evidence, the runtime telemetry, the artefact itself — generated from the system's real configuration and sealed with hash-chained provenance. Not a tracker. A producer.

We built this because we have spent over a decade producing the regulatory artefacts authorisation bodies actually open — FCA permissions, Section 166 skilled-person reviews, MiCA whitepapers, FinCEN MSB filings, CASS safeguarding frameworks. The standard the regulator applies is the standard of the artefact. Nothing else clears the bar. That is why only sealed documents count, why every line carries an owner, and why the record is built to be checked rather than admired.

Track record

Built by practitioners who have produced the regulatory artefacts that authorisation bodies and supervisors open and read.

What we believe

Three principles, applied everywhere.

Evidence over checklists

Regulators evaluate the substantive artefact, not a tracker showing that a policy exists somewhere.

Generated from real configuration

Every file Hael produces is derived from the actual system's classification, controls and runtime — not authored prose.

Built for agents, not retrofitted

Designed from day one for autonomous and tool-using systems, where prompts, scopes and runtime are the controls.

The standard we hold

Held to the standard we produce.

The same regulatory rigour we apply to artefact production applies to how we run Hael itself.

ISO 27001PENDINGSOC 2 TYPE IIPENDINGEU & US DATA RESIDENCYCURRENTSSO / SCIMCURRENTENCRYPTIONCURRENTAUDIT LOGGINGSEALED

See how we approach AI governance.

Built on the artefacts the practices produce. For the firms that will be assessed on them.