Layer 5 — The proof
These are not four products in a navigation bar. They are four answers to four different doubts — which is why they only make sense once you know what Decionis is for.
“Is this a real system or a landing page?”
Proof we are real.
The govern Action and the Node SDK are public, and every Decision Dossier can be verified against our published JWKS without trusting our code.
“Does the protocol actually stop anything?”
Proof the protocol works.
Try to overspend, violate policy, delete production, expose secrets or bypass approval, and watch the verdict come back. No account required.
“Can we express our own authority in it?”
Proof people can build on it.
Open, forkable decision recipes — the executable policies other teams already run, ready to adapt rather than author from scratch.
“Can we actually deploy it where we work?”
Proof it is deployable.
Every place Decionis becomes available — checkout, ERP, ITSM, agent tool calls — reached without rewriting the system it governs.
Evidence for the specific claims teams push back on hardest — money, signatures, drift, and compliance posture.
How a blocked action becomes a defensible number, and where we refuse to claim one.
Check an Ed25519 signature against the published JWKS yourself.
Live policy-drift signals, published rather than described.
The exact certification status, stated without rounding up.
Transparency builds trust. Proof drives adoption.