AILeash · what it costs to prove it
At enterprise scale the model is rarely the expensive part. Ingestion, log storage, monitoring, compliance pipelines and the engineering time to hold it all together usually cost more — and none of it proves anything on its own.
Everything below recalculates from this.
Potential annual saving
—
—
—
These are the figures the saving rests on. They are illustrative, and yours will differ — so put yours in. The arithmetic follows whatever you type.
The two halves of this page are not the same kind of number, and it matters which is which.
A seal is a SHA-256 digest. Thirty-two bytes, whether the decision behind it is one line or a megabyte. That is not a claim about our architecture, it is what a hash is — and it is the whole reason the cost stops tracking the volume.
Two honest notes on the figures above. A liveness beat seals a block every five minutes, so most of that block count is heartbeat rather than customer decisions — it is not a usage number. And external timestamping is per proof: a proof is submitted first and confirmed later, so the split above is what is actually confirmed against what is still pending. Both are readable at /x/ots/status.
Nobody can prove what an organisation would have spent. That number does not exist anywhere to be measured, here or in any vendor's business case. What this page can do is make the assumptions visible and let you replace every one of them.
Puts your inputs and the result into the audit chain, dated and tamper-evident, and hands you a receipt anyone can check. Then what was modelled, and on whose assumptions, is a matter of record rather than of memory — including ours.
It is not a discount on the same architecture. It is less architecture.
Most of that cost is moving and keeping data. Sensitive records get shipped somewhere central, held for years, indexed so they can be searched, and watched so nothing goes missing — because the plan is to reconstruct what happened by reading it all back later.
A proof-based layer answers the question at the moment the decision is made. The decision is scored, sealed into a hash chain, submitted for external timestamping and recorded by independent platforms. What survives is a proof that the decision happened, under stated rules, and has not been altered since.
So the volume stops being the problem. A seal is the same size whether the record behind it is a line or a megabyte, and it does not have to leave your systems for the proof to hold. You keep your own data where it already is.
It does not replace your logs, and it is not meant to. It replaces the machinery built to make logs trustworthy — which is the part that scales badly.