Wants to demonstrate the EU AI Act to a regulator, not just describe it in a policy paper.
Compliance · EU AI Act
Risk class and data sensitivity determine what the platform does — blocked, audited, labelled or routed as standard. Enforced on the control plane, recorded for the regulator.
Wants to demonstrate the EU AI Act to a regulator, not just describe it in a policy paper.
Wants prohibited and high-risk use handled at the source, per class.
Wants risk decisions deterministic and traceable, not dependent on a human judgement per case.
The problem
The EU AI Act sets requirements per risk class, but a PDF of guidelines enforces nothing. Without technical enforcement, "compliant" is a promise, not a fact.
Numaga translates the risk classes into behaviour on the control plane: prohibited use is blocked, high risk gets validation evidence, limited risk gets transparency labels — and every decision is immutably logged.
Risk-aware routing & data classification
Not as a guideline — as policy, enforced on the control plane.
| EU AI Act class | Platform behaviour |
|---|---|
| Prohibitede.g. social scoring | Blocked on the control plane. |
| High riskdecision & process support | Audit · validation evidence. |
| Limited risktransparency required | Transparency labels added in-line. |
| Minimal risk | Standard routing with monitoring. |
| Sensitivity | Behaviour |
|---|---|
| Public | Standard routing. |
| Internal | Identity + audit. |
| Confidential | EU-compliant provider + redaction. |
| Strictly confidentialpersonal data, trade secrets | Strictest provider class + redaction + long-term retention. |
We show how risk classes are enforced and recorded on the control plane.
Get demo access