Savings proofs: a number you can audit
Estimates start arguments. A signed, reproducible proof ends them.
Every infrastructure vendor claims savings. Almost none of them can show you how the number was produced in a way you could reproduce without them. A Needset savings proof is designed to be checked by someone who does not trust us.
Inputs
A proof is computed for one plan against one set of unit costs that you enter: storage per GB-month, egress per GB, decode cost per second, and whatever else applies. The plan itself is deterministic and hashed.
What is counted
- Storage avoided: logical bytes of the selection minus physical bytes after deduplication.
- Transfer avoided: bytes a job would have pulled for whole objects minus the block set actually materialized.
- Decode avoided: decode time for whole objects minus decode time for the materialized set, from measured codec rates.
Each is reported in bytes or seconds first and in dollars second. The bytes are facts about the catalog. The dollars are your unit costs applied to those facts.
Why it holds up
The proof carries the plan hash, the unit costs, the catalog state and a signature. Recompiling the plan reproduces the selection; recomputing the proof reproduces the numbers. The approval that turned the plan into a pilot is in the audit chain, HMAC-linked to every event before it and anchored with a signed attestation. An auditor can verify the whole chain with a viewer key.
What it does not do
It does not claim model quality improvements. Coverage of demand is reported, but whether a plan makes the next model better is something your evaluation run decides, and we would rather import that result than predict it.
See what your corpus is actually worth to your model.
Start free with 50 GB under management. A pilot starts read-only, reports in bytes and dollars, and ends with a number you can audit.