Loading…
Regulations
Noa cannot stop an action that never reaches it.
A signed receipt records a decision. It does not prove a payment happened or make a company compliant with a law. This page maps the available tools to review topics in the EU AI Act, SOC 2 (an independent audit report) and NIST AI RMF (the US National Institute of Standards and Technology's AI Risk Management Framework).
The guarantee requires all four rules. The supported vault lock is being built; the open-source Gate is a reference prototype.
Not a certification
This page maps specific NOA capabilities to specific framework requirements — it does not mean NOA is “compliant,” “certified,” or “audit-ready” under EU AI Act, SOC 2, or NIST AI RMF. Every one of these frameworks requires organizational controls — policies, training, incident response, vendor management — beyond any single tool. Consult your own compliance team before relying on this for a regulatory submission or an audit.
Record-keeping, human-oversight, and traceability expectations for high-risk AI systems — the requirements a governance layer can most directly speak to.
Noa provides — Every gated action emits a signed, hash-chained receipt the moment it is decided — verdict, risk class, policy mode, and a hash of the parameters, never the raw parameters themselves.
Noa provides — The published door guard can hold a risky action for a human decision and record DEFERRED, meaning waiting. Approval permits an attempt; denial stops it. An approval receipt is not evidence that the action executed.
Noa provides — Each receipt links to the hash of the one before it. Changing or removing an earlier record breaks every hash after it. Removing the newest records is caught only if you keep a signed checkpoint.
Noa provides — Three export surfaces ship in the enterprise console today, each with its real bound stated: an audit-log JSON export (step-up-gated, hard-capped at 10,000 events per export — it refuses above that rather than silently truncating), an evidence-bundle export (one verified bundle at a time, by id — not bulk), and an operator-run SIEM NDJSON export (cursor-based; it needs a durable sink and stays off until our team configures a signing key and your destination). The /security page states the same status for each surface.
Not built yet — Not built yet. The three bounded surfaces above are what exists today; a single regulator-scale bulk package is not built, and we say that plainly instead of stretching the word “export”.
Trust-service criteria around audit-trail integrity and independently checkable evidence — and the one thing tooling alone cannot produce: the auditor’s report itself.
Noa provides — Signed, hash-chained receipts: altering any past receipt breaks the hash chain from that point forward, and every receipt is Ed25519-signed.
Noa provides — Verification runs fully offline against a public keyring — no NOA account, no network call — using the open-source (Apache-2.0) verifier.
Not built yet — Not certified. No independent SOC 2 Type I or Type II report exists and none is claimed — an attestation can only be issued by an independent CPA firm after its own examination. SOC 2 readiness materials are named on this site’s own pricing FAQ as a candidate for future paid plans — a stated plan, not a shipping date; the hosted service is free while in beta.
The four core functions — GOVERN, MAP, MEASURE, MANAGE — mapped to what current public evidence establishes and what it does not establish.
Noa provides — Every receipt records the verdict, the mode the gate ran in and, when one applies, the ID of the rule that decided it. It does not contain the policy text.
Noa provides — Every gated action carries an explicit risk-class label — LOW, MEDIUM, HIGH, CRITICAL, or IRREVERSIBLE — set before the action runs.
Noa provides — The playground lets you check receipts in your browser. The public matrix, observed on 2 October 2026, records comparisons between verifier ports using different test sets; it does not prove five independent implementations passed one identical set.
Noa provides — The open-source Gate reference checks whether a held request has expired. This is prototype evidence using a test ledger, not a supported production vault lock. Pilots start after the vault lock’s core parts are built and checked by someone other than its builders.
Read the spec. Verify a receipt yourself. Then ask your compliance team.
Apache-2.0 package artifacts. The receipt format and MCP proxy documentation are public. Each row separates available code, reference prototypes and planned work.