Local execution
Benchmarks execute on your own hardware. The runtime, the dataset, and the results never leave the machine.
Keystone runs ML-KEM, ML-DSA, Falcon, and SPHINCS+ against classical baselines on your own hardware, and keeps the evidence.
Post-quantum cryptography benchmarking and quantum runtime workbench.
| Algorithm | Status | Started | Iterations |
|---|---|---|---|
| kyber | failed | 2:59:51 AM | 10,000 |
| kyber | failed | 3:00:27 AM | 10,000 |
| kyber | completed | 3:25:57 AM | 10,000 |
| kyber | completed | 3:37:27 PM | 10,000 |
Four NIST post-quantum families, timed on the machine in front of you. Every figure below comes from a run you can reproduce.
Benchmarks execute on your own hardware. The runtime, the dataset, and the results never leave the machine.
Every run records its algorithm, parameter set, iteration count, and timing. A result you can't trace is a result you can't trust.
Runs resolve into reports you can hand to a reviewer, with parameters and integrity checks attached.
Download stays closed until the DMG, manifest, checksum, signing, notarization, filename, version, and live response all agree.