Provably
compliant.
One checkpoint sits in front of every regulated outbound action. The regulator aligned baseline and your own overlay both have to sign before the action can execute. The receipt is independent of us, and the regulator can rederive the verdict from scratch.
Compliance today is a promise.
Regulated firms must prove every outbound message, alert, or marketing push followed the rules. In practice, what the regulator gets is the firm’s own logs, written by the firm’s own systems, reviewed long after the damage is done.
Under the UKGC October 2025 framework, FCA Consumer Duty and EU AI Act Article 12, “trust us” is no longer a defence. The fine arrives after the breach.
Six doors. Pick the one that matters to you.
The microsite is split into six functional reads, plus the white paper above. Each is self contained and opens offline; the proof and industries pages run real cryptography in your browser.
How it works
An interactive eight chapter walk through the gate, the two rulebooks, the role typed quorum, the consensus check, freshness binding, and how the verdict turns into a receipt. Click any chapter to open the deep dive.
Read the explainerSee the proof
Pick a scenario, send a message through the gate, then recheck the proof. The browser recomputes the tamper evident receipt against real captured testnet artefacts. The six gate invariants are laid out symmetrically; the freshness binding card answers “without a real time lookup”.
Run the demoIndustries
Same gate, seven verticals: gambling, FCA debt collection, financial promotions, UK GDPR, Consumer Duty, community pharmacy, EYFS childcare. Each tab carries the actual rules modelled in its rule set, the named refusal codes, and one permit plus one refuse scenario. Gambling uses real captured proofs.
Browse verticalsIntegrations
Nine egress patterns catalogued, two deployment shapes (Inline enforce vs Out of band observe), four integration mechanics (SDK, sidecar proxy, webhook, bus interceptor), and the fail CLOSED vs fail SAFE table per surface. The pharmacy cabinet and the fire egress door are not the same question.
See the surfacesFor regulators
Download a proof bundle, verify it in your browser or with the kc-verify CLI on your own machine. The six checks the verifier runs, the four residual questions the verifier does not answer, and the open source path to building the verifier yourself. Don’t trust us. Recompute.
Book a pilot
Six week, single surface, Observe only deployment against your outbound marketing channel. No card at the start. No invoice on walk away. Two binary acceptance conditions. The buyer keeps every byte of evidence. Founding rate window is open.
Read the SOWCheck us. Don’t trust us.
Every regulated outbound action passes one gate. The gate evaluates two independent rulebooks at consensus time: the regulator aligned baseline and the firm’s own overlay. Both must sign. The verdict and its reasons are written to a ledger the firm, the regulator and an independent auditor all see. No single party, not even Kronaxis, can wave a message through or quietly delete a refusal.
Re running the rule on a fresh machine, against the same descriptor and the same rule text, gives the same answer. The receipt’s sealed inclusion can be re computed cryptographically in your browser. That is the difference between “trust us” and “don’t trust us.”