Loading…
Noa cannot stop an action that never reaches it. NOA Mandate has one way of use: all four rules. There is no partial mode. We are building the supported vault lock for companies whose AI agents touch money, data or production. The Gate — the program that holds an action, asks for approval and issues a one-time grant — is an open-source reference (prototype); the vault lock (vault guard) is being built. Customer pilots start after the vault lock’s core parts are built and checked by someone other than its builders.
An agent that can refund money, delete records or deploy code needs rules at the place where the change happens. A door guard alone is not enough.
All four rules are required.
Our Signal series contains dated articles and source references. The English capability blocks carry a 2 October 2026 correction; article evidence keeps its original date.
Read the Signal seriesThe door guard holds the request for the approvers named by the rules. Today the MCP proxy is published on npm; the Gate is an open-source reference (prototype); the vault lock (vault guard) is being built.
The phone signs an approval or a denial. The signature identifies the enrolled device’s key, not a person’s understanding. Phone approval through the relay was last proven for our own workspace on 29 September 2026; the app is not publicly downloadable yet.
A receipt is a signed record. Check its signature and links offline with trusted public keys. Keep the key’s validity record and required checkpoints for later-retired keys. A valid receipt does not prove a physical outcome.
The receipt format is an individual Internet-Draft, a proposal for review. It is not an adopted standard. The receipt format and verifier are public.
The core is open source under Apache-2.0. The hosted console is private and free during beta. Paid enterprise plans may follow; the supported vault lock is being built.
We publish verified, sourced analysis of real agent-accountability incidents — and correct ourselves in public when we get a detail wrong. That is how a category earns the right to define itself.
We state what a receipt proves and what it cannot prove. We separate published building blocks, the live console beta and the supported vault product being built.
Three open-source packages — noa-receipt, noa-mcp-proxy, noa-mcp-adapter-core (all Apache-2.0) — were downloaded 1,194 times from npm in the month to 2026-09-30 (1,072 + 64 + 58), measured 2026-10-02 against the public npm downloads API — whose counts include mirrors and CI, as every npm number does.
4 Apache-2.0 packages — noa-receipt@0.9.0, noa-mcp-proxy@0.5.0, noa-mcp-adapter-core@0.5.0, and noa-signer-sidecar@0.1.0 — were publicly available on npm when checked 2026-10-06. This is a package-availability fact. The open-source core — wire-format specifications, verifiers and conformance vectors — is public at https://github.com/NordenSoft/noa-mandate-core; the hosted product and its console are private.
The enterprise console ships SSO/SCIM (company sign-in and account management), retention settings, SIEM export (records for security monitoring), audit anchoring (saved signed chain heads) and per-tenant signing keys. Signup is open in a free beta. Customer adoption and revenue are not established by the download figures above.
Both mobile apps (iOS and Android) are coming to the App Store and Google Play. Neither is in a store yet, so neither can be downloaded today — and this line changes the day that happens.
You will not find invented logos, a fabricated user count, or a ten-person team on this page. What is here is real and checkable — which is the whole point of the product.
One person built this — and here is the honest answer to that risk.
The business has a founder concentration risk. The open-source verifier lets customers keep checking their records with the required trusted keys and checkpoints. Staffing security response, support and compliance is a plan, not a claim that those teams exist today.
Our intended buyers lead security or platform engineering at companies whose agents touch money, data or production. Our commercial plan is managed enterprise operations alongside a free open-source core.
These teams need rules before a payment, deletion or production change. They can inspect the core and try the free console beta today. Vault pilots begin after the vault lock’s core parts are built and checked by someone other than its builders; we do not promise an afternoon production installation.
Market size, bottom-up — argue with the inputs
We size bottom-up rather than quoting an analyst headline: organizations running agents with write access to real systems × approver seats per organization × an assumed per-seat price. Each input is an assumption, published so it can be attacked:
Multiplying the midpoints (20,000 organizations × 27.5 seats × $17.50 × 12 months) gives about $115 million per year. We publish the method instead of the headline so you can swap any input for your own and get your own number.
Leaving a protected action without an approval check is the baseline this product is designed to change.
A homegrown approval queue is the pattern Noa is built to replace. Ask whether its decision is tied to the exact action, enforced at the vault, and exported as a signed record you can check offline. A chat button alone does not establish those properties.
A confirmation prompt asks for a decision. Check whether the particular system also enforces that decision at the vault and provides a portable signed record; we make no blanket claim about every platform.
Logs and security monitoring record reports about events. Ask separately what checks approval before the action. A record by itself is not an approval control.
The honest risk: any large platform could bolt signed approvals onto its own stack. Our bet, stated plainly, is that accountability evidence is only worth something if it outlives any one vendor — which favors a neutral, open format over a platform feature. That is a bet, not a certainty.
We are not running a raise. We are open to conversations with investors who work on agent infrastructure and security — the honest state of the company is on this page, and what capital would accelerate is listed below, in priority order. If that is a future you want to back, we would like to talk.
What capital would accelerate, in order
First hires, in order: a security engineer who owns incident response, an enterprise support engineer, and a compliance lead. The founder keeps building product.
This page makes no forward-looking financial promises, and every number on it carries its measurement date. Re-run them yourself: api.npmjs.org/downloads/point/2026-09-01:2026-09-30/noa-receipt (same URL shape for the other two packages), npm view noa-receipt@0.9.0. The market sizing above is labeled assumption, not measurement.