The analysis behind the numbers.
Methodology decisions, field developments, and what the migration costs — written for the people who have to justify the decision to someone else. Every figure carries the run that produced it.
How we measure — and where our own numbers are soft.
The run protocol, the hardware, the sourcing bar, and the week the audit trail caught our own instance throttling. If you're going to cite a number from here, this is the page that tells you how much weight it holds.
Read →CBOM tells you what you run. P-CBOM tells you what it costs.
A Cryptography Bill of Materials inventories the algorithms in your estate. It says nothing about what they cost to run. P-CBOM is the CC0 extension that closes that gap.
Read →The benchmark didn't lie. The library changed underneath it.
Why static PQC benchmark numbers rot within weeks — and why continuous cross-validation against eBACS and liboqs, not a one-time report, is the only defensible way to measure post-quantum performance.
Read →Know what your migration could cost.
We’re working with a small number of organizations to model the economics of their post-quantum transition.