Loading…
Regulations
A capability-to-requirement map, not a compliance claim. Every row below cites either an exact versioned public package artifact, a same-site qualified product-evidence boundary, or an explicit public nonclaim — verify the stated boundary instead of taking our word for it.
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 — A risky action is held as a signed DEFERRED receipt until a human approves it — producing a DEFERRED → ALLOWED → EXECUTED chain, not a silent auto-run.
Noa provides — Each receipt link-hashes to the one before it (chain.prevHash → chain.hash); altering or removing a past record breaks every hash that follows it.
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 a resumable SIEM NDJSON stream (cursor-based; applying it requires a durable sink). The /security page states the same status for each surface.
Noa provides — Not shipped. 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.
Noa provides — 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 policy verdict (ALLOWED / BLOCKED / DEFERRED / EXECUTED / …), the mode the gate ran in, and which rule produced the decision — a durable record of the governing policy itself, not just the outcome.
Noa provides — Every gated action carries an explicit risk-class label — LOW, MEDIUM, HIGH, CRITICAL, or IRREVERSIBLE — set before the action runs.
Public evidence boundary — The public playground exposes browser-verifier behavior for inspection. A public cross-implementation corpus or conformance report is not currently served; this page therefore makes no implementation-status or automated-gate claim for that work.
Public evidence boundary — Current public package artifacts do not serve the gate implementation needed to substantiate a TTL-expiry claim. This page therefore makes no implementation-status claim or public-verification credit for that behavior.
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; unavailable source or conformance evidence is explicitly not claimed.