Start
Try it on your machine.
Two binaries: decern to prove and verify, decern-serve to answer requests. You only need cvc5 on PATH for the proofs — not to serve answers.
Prebuilt binaries
Prebuilt, signed binaries for Linux (x64/arm64), macOS (Apple Silicon) and Windows (x64) are on the releases page. Each one carries a Sigstore bundle; how to check a signature is in SECURITY.md. Name them decern and decern-serve and put them on your PATH.
Releases ↗
From source
cargo install decern-cli decern-server
Or clone and build with the pinned toolchain from rust-toolchain.toml.
# 1 · prove every invariant over the model's input space (cvc5)
decern prove
# 2 · run the PDP (writes a tamper-evident ledger); this walkthrough is its own caller.
# --key keeps the signing key: without it a restart refuses the ledger it already wrote.
decern-serve --ledger /tmp/decern.jsonl --key /tmp/decern.key --trust-proxy &
# 3 · decide over HTTP (AuthZEN-shaped) — corp reads a claim it owns
curl -s localhost:8080/access/v1/evaluation -H 'content-type: application/json' -d '{
"subject": {"type":"Principal","id":"corp"},
"action": {"name":"Read"},
"resource": {"type":"Resource","id":"claim1"}
}'
# 4 · verify the ledger (hash chain + every signature)
decern verify --ledger /tmp/decern.jsonl \
--pubkey "$(curl -s localhost:8080/pubkey | jq -r .kid)"
Sovereign · one process
--ledger <PATH>
One ledger file. Binds loopback by default; starting requires the caller posture to be named — bearer, signed request, SPIFFE, AAuth, or a declared front.
Hosted · one host
--sharded <DIR>
Several server processes share one ledger, one hash chain per tenant, coordinated by a file lock.
Hosted · many hosts
--sharded postgres://…
Advisory-lock head store for replicas across hosts. Build with --features postgres; a URL to another host must carry sslmode=require, and the URL is never logged.
--ledger and --sharded are mutually exclusive, and --sharded requires --key, the key every replica signs with, a postgres:// URL also --missions-per-host, and --retired-key names each key it replaced. Audit a directory store with decern verify --sharded <dir> --pubkey <kid>, with --pubkey once per key GET /pubkey lists under keys — it checks every shard and exits non-zero if any fails; a Postgres head store has no decern verify path. A start, and that verify, read each shard's whole history under the shard's lock, so an append to it waits until the read ends.
Integrations & clients
Five worked examples ship in the repository, all runnable and CI-tested and none published as crates: examples/mcp consults decern before every tool call, examples/ext_authz_adapter puts it behind NGINX, Traefik or Envoy, and signed-request, spiffe and aauth each run a workload posture end to end. Thin AuthZEN 1.0 clients are published for applications: uv add decern (Python), npm install decern (TypeScript) and go get github.com/anivar/decern/sdks/go (Go).