Book a pilot.
One outbound surface, Observe only, six weeks. The engine reads a mirror of your traffic out of band and cannot affect the production path. No card at the start. No invoice on walk away. At week six, your Head of Compliance signs against two binary conditions, or you walk with every byte of the on ledger evidence.
What is in, what is out.
| Duration | Six weeks from signed Letter of Intent to acceptance review. Week one is wiring; weeks two to six are the live Observe run. |
| Mode | Observe only across the full six weeks. No Enforce. No blocking. No path by which the engine can prevent an outbound send. |
| Surface | One outbound marketing surface of your choosing: email, SMS, or both, routed through a one way mirror at egress. |
| Rule set | Regulator aligned baseline composed with one overlay your compliance team writes. UKGC LCCP is available today; FCA CONC, PRIN 2A, FSMA s.21, UK GDPR, and EU AI Act Article 12 baselines are scheduled for release. |
| Topology | Three validator single tenant cluster: one Kronaxis validator, one buyer validator in your VPC, one independent auditor validator hosted by your existing audit firm under a separate engagement letter. |
| Buyer side commitment | Approximately one engineering FTE for week one; approximately 0.3 FTE across weeks two to six. One HSM (CloudHSM, YubiHSM2 or equivalent). |
| Pilot fee | No card at the start. No invoice on walk away. Founding rate conversion only on acceptance per the table below. |
Two binary conditions. Nothing else.
At week six, your Head of Compliance signs against the two conditions below. Both must land for acceptance. Either does not, and the walk away triggers. The integrity test is whether we hold the line in writing: a vendor that promises walk away and then walks back from it has failed the first GC review.
1. Gate availability
At or above 99 per cent across the live traffic window of weeks two to six, measured per minute against the per minute reachability of the three validator cluster.
2. A regulator readable refusal
At least one refusal across the six weeks that your compliance team agrees would otherwise have proceeded to act. The refusal is signed, dated, and re derivable from the on ledger evidence.
Anchor high. Per brand, per rule set, per year.
Kronaxis Compliance is priced against the cost of one regulatory penalty avoided, not against the cost of a SaaS seat. The buyer’s frame is a single tier five UKGC enforcement (up to fifteen per cent of brand GGY) or a single FCA Consumer Duty settlement of half a million to eight million pounds plus a skilled persons review. The platform price is set so that the worst case loss avoided pays for the platform several hundred times over.
- No card at pilot start
- Founding rate held twelve months
- 25 per cent off additional rule sets during the founding window
- A short written reference after one quarter on live traffic
- Unlimited
certify(action)calls per brand per rule set - Multi brand operator: 10 per cent off per additional brand, capped at 40 per cent at five brands or more
- First overlay (your own) bundled in the annual fee
- Single tenant audit console, signed proof PDF export, bulk evidence export on request
Send a Letter of Intent. No card. No commitment beyond writing.
Three places open. Allocation is in order of signed Letter of Intent. The conversation begins with a 30-minute call between your Group GC, Chief Compliance Officer and Head of Engineering jointly.
Three buttons
Pick the one that fits where you are.
Six weeks. Six concrete deliverables.
Each week ends with a stated artefact in the buyer’s hands. The acceptance call at week six is against the two binary conditions above, not against vendor narrative.
| Week | Activity | Buyer side deliverable at week end | Kronaxis side commitment |
|---|---|---|---|
| Week 1 | Wiring: mirror configuration on the chosen outbound surface; descriptor extractor for the surface; one tenant overlay drafted with your General Counsel team. | A live Observe deployment receiving descriptors. First per action proof committed on the testnet cluster. | Two engineers full time for the week; on call for descriptor mapping questions. |
| Weeks 2 to 3 | Live observation begins. Refusal codes start landing in your incident channel. Compliance team confirms each refusal is the right code for the right reason. | A weekly refusal report: count by code, distribution by hour, distribution by campaign, false positive rate (zero by design). | Engineer support for tuning the overlay against the first wave of real traffic. |
| Week 4 | Midpoint review: read the refusals together. Decide whether any refusal class needs the overlay tightening; surface any descriptor extractor bugs. | A signed checkpoint memo from your Head of Compliance summarising what the gate has caught so far. | Engineer cycle to tighten overlay or extractor if the review surfaces a real defect. |
| Weeks 5 to 6 | Steady state observation. Audit console walkthrough with your General Counsel. Independent verifier walkthrough with your audit firm. | A bundle export per refusal, validated locally by your audit firm running kc-verify on their own machine. |
Engineer cycle for any audit firm queries on the bundle format. |
| Week 6 acceptance | Your Head of Compliance signs against the two binary conditions: gate availability above 99 per cent, and at least one refusal your team agrees would otherwise have proceeded to act. | Either: a signed acceptance, conversion to founding rate. Or: a signed non acceptance, walk away with every byte of evidence. | Either: founding tier paperwork. Or: written confirmation of walk away within five business days. |
The evidence is yours. Whichever way the call goes.
The six week record belongs to the buyer. The gate writes it; the buyer holds it. If the pilot converts, the record is the foundation of the GA deployment. If the pilot does not convert, the record is still the buyer’s independent audit trail of six weeks of outbound traffic.
1. The per action proof archive
Every descriptor that passed through the gate, every verdict the gate issued, every signature that sealed it, every audit path, every freshness stamp. Stored in the buyer’s own validator node; the buyer also receives a portable JSON export of every bundle.
2. The on chain violation log
Every refusal the gate issued, on chain, signed, tamper evident. The buyer’s Head of Compliance can hand this log to a regulator or to an independent auditor as a contractable record of what the firm prevented.
3. The audit console snapshot
A single tenant audit console that walks the refusals by code, by hour, by campaign, by surface. A signed PDF export per refusal for the buyer’s evidence packs. Bulk export of the full pilot window on request.
4. The verifier and the kit
The kc-verify binary, the regulator self verify kit, and the source repository at the version it ran during the pilot. The buyer’s audit firm can rebuild and rerun the verifier from source at any time.
No vanity numbers. Six contractable measurements.
Every measurement below is deterministic and independently verifiable from the on ledger record. Nothing relies on vendor side telemetry.
| Measurement | Definition | How a regulator could reproduce |
|---|---|---|
| Per minute availability | Per minute, did the gate respond to ingest within the SLA window, with all three validators reachable. | Read the per minute health attestations on the ledger; verify the signatures. |
| Total descriptors received | Count of NormalisedAction entries ingested across the pilot window. |
Count entries in the on ledger ingest log; deduplicate by descriptor hash. |
| Refusal count by code | For every named refusal code in the taxonomy, the count of refusals carrying that code. | Aggregate by code from the on chain violation log; cross check against the audit console. |
| Refusal latency | Time from descriptor ingest to refusal verdict landing on the ledger, percentiles 50, 90, 99. | Subtract the descriptor timestamp from the block timestamp for every refused action. |
| Freshness SLA compliance | For every consulted register, the fraction of checks where the snapshot age was within the contracted SLA. | Read the freshness stamps from every per action proof; compute the fraction where AgeAtCheckSeconds ≤ SLAWindowSeconds. |
| Independent verifier pass rate | Fraction of exported bundles that pass kc-verify on a fresh machine (target: 100 per cent). |
Build kc-verify from source on the audit firm’s own machine; run against the exports. |
What conversion buys. What it does not.
Conversion to the founding rate at week six unlocks the platform for twelve months at the rate stated in the table above. The table below names every line item that does and does not sit inside the founding rate, so the buyer’s CFO is not surprised by a chargeable extra at month two.
| Line item | Included | Note |
|---|---|---|
Unlimited certify(action) calls per brand per rule set |
YES | No per call billing. No throttled tier. |
| Regulator aligned baseline (UKGC LCCP at GA) | YES | FCA CONC, PRIN 2A, FSMA s.21, UK GDPR, and EU AI Act Article 12 baselines are scheduled for release. |
| First tenant overlay (your own counsel’s rules) | YES | Engineer support to land it in week one. |
| Single tenant audit console | YES | Hosted on your subdomain; signed PDF export per refusal. |
kc-verify CLI plus regulator self verify kit |
YES | Open source; the buyer’s audit firm can build from source. |
| Additional rule sets beyond your first | OPT IN | 25 per cent off during the founding window; standard rate at GA. |
| Additional brands under the same operator | OPT IN | 10 per cent off per additional brand, capped at 40 per cent at five brands or more. |
| Your own validator infrastructure | NO | One VPC class node, standard cloud rates; you own the host. |
| Auditor validator hosting | NO | Indicative GBP 6,000 to 18,000 across the six week pilot with a Big Four audit firm; you contract this separately. |
| Your HSM | NO | CloudHSM, YubiHSM2, AWS CloudHSM, Azure Dedicated HSM all supported. |
| Custom rule sets beyond the GA shipped baselines | NO | Quoted per scope; usually a few weeks of engineer time. |
| Engineering integration into surfaces beyond your nominated trigger | NO | The first nominated surface is in scope; additional surfaces are quoted per scope. |
A vendor that promised a walk away and then walked back from it
… has failed the first General Counsel review. The integrity test of this offer is whether it holds in writing. It does, in section six of the Statement of Work, and in the Letter of Intent. If your reading of the walk away clause is different from ours after the call, that is a defect in the document, and we fix the document.