Layer 5 — The proof

Open, verifiable, and developer-friendly.

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.

Transparency builds trust. Proof drives adoption.

Four forms of evidence

“Is this a real system or a landing page?”

GitHub

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?”

Sandbox

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?”

Policy Exchange

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?”

Connectors

Proof it is deployable.

Every place Decionis becomes available — checkout, ERP, ITSM, agent tool calls — reached without rewriting the system it governs.

Published distribution proof

Zapier reviewed and published these templates on August 4, 2026. Each activation route is tied to the published template id, not a guessed directory URL.

Published on ZapierAug 4, 2026

Google Sheets

Create Decionis decision dossiers for new Google Sheets rows

Turn spreadsheet rows into governed actions—not blind automation.

For Approvals, finance operations, and spreadsheet-driven imports.

Govern this workflow with Zapier Watch the workflow demonstration

Published on ZapierAug 4, 2026

HubSpot

Create Decionis decision dossiers for new HubSpot deals

Every new HubSpot deal gets a signed policy decision.

For Deal governance, revenue operations, and CRM-controlled handoffs.

Govern this workflow with Zapier Watch the workflow demonstration

Published on ZapierAug 4, 2026

Shopify

Create Decionis decision dossiers for new paid Shopify orders

Every paid Shopify order produces verifiable decision evidence.

For Commerce operations, margin controls, refunds, and order governance.

Govern this workflow with Zapier Watch the workflow demonstration

Which proof do you need?

Pick the role you are reading as. Each route lists the questions that audience actually asks, and where each one is answered.

Developer

You will wire this into a codebase and need to know how it behaves under failure.

What you are asking

“How long does the setup actually take?”
“What does the call look like, and what comes back?”
“Is it deterministic — same input, same verdict?”
“What is the added latency?”
“What happens when Decionis is unreachable?”
“Can I test it locally without an account?”

Where it is answered

Security & compliance

You have to defend this in an audit and know exactly what is retained and where.

What you are asking

“Which policy version governed a given action?”
“How do I verify a signature without trusting you?”
“Who held the authority, and is it separated from execution?”
“What is retained, for how long, and where does it run?”
“How does this map onto our control framework?”

Where it is answered

Business buyer

You are deciding whether this pays for itself and how risky the rollout is.

What you are asking

“How much money would this have protected?”
“How many actions would have been restrained?”
“What is the false-positive rate on my own traffic?”
“How long until I see a number I can defend?”
“What is the risk of turning it on?”

Where it is answered

Platform partner

You are evaluating whether to list, co-sell or build against Decionis.

What you are asking

“Is there real demand from your shared users?”
“How mature is the integration, honestly?”
“What support burden lands on us?”
“What is the security posture for a review?”
“Which joint use cases actually close?”

Where it is answered

If you want to go further

Evidence for the specific claims teams push back on hardest — money, signatures, drift, and compliance posture.

Prevented-loss methodology

How a blocked action becomes a defensible number, and where we refuse to claim one.

Verify a Decision Dossier

Check an Ed25519 signature against the published JWKS yourself.

Public dossier corpus

Synthetic dossiers signed by a published key, archived with a DOI (10.5281/zenodo.22692903) and checked with @decionis/verify — the verifier's behaviour, reproducible without an account.

Public drift dashboard

Live policy-drift signals, published rather than described.

Trust and compliance posture

The exact certification status, stated without rounding up.

Published Zapier workflows

Three reviewed templates with durable activation ids for Google Sheets, HubSpot, and Shopify.

Transparency builds trust. Proof drives adoption.

Independently checkable

Verify it with our service switched off.

Every claim on this page about evidence rests on one test: can a party who does not trust Decionis check the record without Decionis in the loop? The public corpus and the open verifier let you run that test now, with no account and no network call to us.

Step 1
Download the evidence
The Decision Dossier corpus — v0.1.4, Apache-2.0, archived with a DOI — is a set of signed dossiers with their inputs snapshot, execution binding and JSON-LD, plus the negative cases a verifier must refuse. The signing key is published on purpose, so you can regenerate the corpus instead of trusting the fixtures.
DOI 10.5281/zenodo.22692903
Step 2
Leave Decionis out of the loop
@decionis/verify is an open verifier that runs from two local files: the dossier and the key set. It recomputes the RFC 8785 canonical form, checks the Ed25519 signature and the execution-binding and dossier digests, and refuses anything altered. Disconnect if you like; it needs nothing from us.
@decionis/verify@0.3.0
Step 3
Verify the decision
The corpus proves the verifier behaves correctly, including when it should refuse. It does not prove that a production dossier verifies — that needs a real dossier and the live JWKS, and the repository documents that check separately rather than shipping a production artifact it should not have. The technical note walks through both halves, including the live key set a production dossier is checked against.
Verify a Decision Dossier without an account

npx -y @decionis/verify \
  --file dossiers/vectors/owned-execution-bound.json \
  --jwks dossiers/corpus-jwks.json

For a regulated institution this is the test that matters: evidence that remains checkable by a party who does not trust the operator, and that stays checkable if the operator disappears.

Verify a dossier on this site Corpus on GitHub Production signing keys (JWKS)

Next — step 6 of 7DevelopersThe public artifacts and the fastest path to a first verdict.

Everything under Proof

What you can check yourself, before you trust any of it.

Loading…

Layer 5 — The proof

Open, verifiable, and developer-friendly.

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.

Transparency builds trust. Proof drives adoption.

Four forms of evidence

“Is this a real system or a landing page?”

GitHub

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?”

Sandbox

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?”

Policy Exchange

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?”

Connectors

Proof it is deployable.

Every place Decionis becomes available — checkout, ERP, ITSM, agent tool calls — reached without rewriting the system it governs.

Published distribution proof

Zapier reviewed and published these templates on August 4, 2026. Each activation route is tied to the published template id, not a guessed directory URL.

Published on ZapierAug 4, 2026

Google Sheets

Create Decionis decision dossiers for new Google Sheets rows

Turn spreadsheet rows into governed actions—not blind automation.

For Approvals, finance operations, and spreadsheet-driven imports.

Govern this workflow with Zapier Watch the workflow demonstration

Published on ZapierAug 4, 2026

HubSpot

Create Decionis decision dossiers for new HubSpot deals

Every new HubSpot deal gets a signed policy decision.

For Deal governance, revenue operations, and CRM-controlled handoffs.

Govern this workflow with Zapier Watch the workflow demonstration

Published on ZapierAug 4, 2026

Shopify

Create Decionis decision dossiers for new paid Shopify orders

Every paid Shopify order produces verifiable decision evidence.

For Commerce operations, margin controls, refunds, and order governance.

Govern this workflow with Zapier Watch the workflow demonstration

Which proof do you need?

Pick the role you are reading as. Each route lists the questions that audience actually asks, and where each one is answered.

Developer

You will wire this into a codebase and need to know how it behaves under failure.

What you are asking

“How long does the setup actually take?”
“What does the call look like, and what comes back?”
“Is it deterministic — same input, same verdict?”
“What is the added latency?”
“What happens when Decionis is unreachable?”
“Can I test it locally without an account?”

Where it is answered

Security & compliance

You have to defend this in an audit and know exactly what is retained and where.

What you are asking

“Which policy version governed a given action?”
“How do I verify a signature without trusting you?”
“Who held the authority, and is it separated from execution?”
“What is retained, for how long, and where does it run?”
“How does this map onto our control framework?”

Where it is answered

Business buyer

You are deciding whether this pays for itself and how risky the rollout is.

What you are asking

“How much money would this have protected?”
“How many actions would have been restrained?”
“What is the false-positive rate on my own traffic?”
“How long until I see a number I can defend?”
“What is the risk of turning it on?”

Where it is answered

Platform partner

You are evaluating whether to list, co-sell or build against Decionis.

What you are asking

“Is there real demand from your shared users?”
“How mature is the integration, honestly?”
“What support burden lands on us?”
“What is the security posture for a review?”
“Which joint use cases actually close?”

Where it is answered

If you want to go further

Evidence for the specific claims teams push back on hardest — money, signatures, drift, and compliance posture.

Independently checkable

Verify it with our service switched off.

Step 1
Download the evidence
The Decision Dossier corpus — v0.1.4, Apache-2.0, archived with a DOI — is a set of signed dossiers with their inputs snapshot, execution binding and JSON-LD, plus the negative cases a verifier must refuse. The signing key is published on purpose, so you can regenerate the corpus instead of trusting the fixtures.
DOI 10.5281/zenodo.22692903
Step 2
Leave Decionis out of the loop
@decionis/verify is an open verifier that runs from two local files: the dossier and the key set. It recomputes the RFC 8785 canonical form, checks the Ed25519 signature and the execution-binding and dossier digests, and refuses anything altered. Disconnect if you like; it needs nothing from us.
@decionis/verify@0.3.0
Step 3
Verify the decision
The corpus proves the verifier behaves correctly, including when it should refuse. It does not prove that a production dossier verifies — that needs a real dossier and the live JWKS, and the repository documents that check separately rather than shipping a production artifact it should not have. The technical note walks through both halves, including the live key set a production dossier is checked against.
Verify a Decision Dossier without an account

npx -y @decionis/verify \
  --file dossiers/vectors/owned-execution-bound.json \
  --jwks dossiers/corpus-jwks.json

For a regulated institution this is the test that matters: evidence that remains checkable by a party who does not trust the operator, and that stays checkable if the operator disappears.

Verify a dossier on this site Corpus on GitHub Production signing keys (JWKS)

Next — step 6 of 7DevelopersThe public artifacts and the fastest path to a first verdict.

Everything under Proof

What you can check yourself, before you trust any of it.