Verify it yourself

Don’t take our word for it.
Reproduce it.

Nervos sells governance, so our claims must survive your scrutiny. Every important claim below is independently verifiable — against live endpoints, your own browser’s crypto, or the behavior of the system itself. Pilots include a sandbox tenant so your security team can run the full replay script, not a demo.

The audit ledger is hash-chained and tamper-evident

Tenant token

How to verify: Export any execution ledger (GET /api/actions/proposals/[id]/ledger), then recompute each SHA-256 entry hash from the canonical step JSON — or paste the export into /ledger-verify and let your own browser do it via Web Crypto.
What you’ll see: Every recomputed hash matches its entry_hash and each entry links the previous one. Alter any field and the chain visibly breaks at that exact row.

Tenants are isolated at the database layer (RLS)

Tenant token

How to verify: Authenticate as org A and request a proposal ID belonging to org B. Row-Level Security policies (org_id = current_org_id()) are enforced by Postgres, not application code.
What you’ll see: “Not found” / 401 — never another org's data. Forged org_id inserts are rejected by policy.

The write-gate is server-side and locked

Tenant token

How to verify: POST an action type that is not in the locked registry (lib/actions.ts) to the execute endpoint. Agents and users can only propose registry-defined actions with defined risk levels.
What you’ll see: The request is rejected server-side. There is no code path for an arbitrary write.

Executed actions are idempotent and reversible

Tenant token

How to verify: Execute an approved proposal twice — the second call short-circuits on the idempotency key with no duplicate write. Then roll it back: reversible actions map to a compensating write (e.g. createVendorBill ↦ voidTransaction).
What you’ll see: Second execute returns { status: "executed", idempotent: true }. The rollback lands in the same hash-chained ledger as a compensation step.

Security headers are enforced, not report-only

Public

How to verify: curl -I https://www.thenervos.com and read the response headers — no account needed.
What you’ll see: Content-Security-Policy (enforced), Strict-Transport-Security with preload, and the rest of the hardening set, on every response.

A proposer can never approve their own action

Tenant token

How to verify: Create a proposal, then attempt to approve it as the same user (web or Slack). Separation of duties is enforced in the transition logic and the attempt is counted as a governance metric.
What you’ll see: The approval is blocked with a self_approval reason and appears in the governance summary as a blocked attempt.

What we don’t claim

Honesty is part of the product. Nervos is notyet SOC 2 Type II attested (in progress), and holds no CMMC or FedRAMP authorization — you’ll never see those presented as credentials here. Our NIST 800-171 self-assessment, System Security Plan, and control mappings are available under NDA, stated exactly as far as the evidence goes.

Verify a ledger in your browser Request a sandbox tenant

Don’t take our word for it.
Reproduce it.

What we don’t claim