Key generationComplete
- Avg time
- 0.006041 ms
- Throughput
- 165,546 ops/s
- Peak memory
- 196.6 MB
Built for Mac
Post-quantum benchmarking, built for Mac.
Keystone is a native desktop instrument for measuring, comparing, and reporting post-quantum and classical cryptographic algorithms with reproducible local evidence.
- macOS first
- Local benchmark runs
- Windows and Linux planned
Benchmarks
PQC and classical cryptographic algorithm performance benchmarking
ConfigurationKyber benchmark run
ReadyEncapsulationComplete
- Avg time
- 0.005462 ms
- Throughput
- 165,546 ops/s
- Peak memory
- 16.4 MB
DecapsulationComplete
- Avg time
- 0.006474 ms
- Throughput
- 165,546 ops/s
- Peak memory
- 0 KB
VisualizationAverage Time (ms)
Algorithm coveragePost-quantum and classical baselines
ML-KEM
Key encapsulation
512, 768, 1024ML-DSA
Digital signatures
44, 65, 87Falcon
Compact signatures
512, 1024SPHINCS+
Hash signatures
SHA2, SHAKEClassical
Baseline comparison
RSA, ECDSA, AESRelease evidence
Designed around the proof a cryptography tool has to carry.
Every surface maps to a real workflow — benchmark phases, visualization, workload scheduling, and exports. Nothing decorative, nothing you can’t reproduce locally.
Local execution
Benchmark runs stay on the Mac that produced them.
Parameter evidence
Schemes, variants, iterations, and backend context remain visible.
Exportable reports
Results are shaped for review, audits, and research notes.
Native instrument
Not a cloud dashboard pretending to be cryptography.
Keystone is positioned as a Mac-first lab bench: run locally, inspect the output, and package results only after native dependency and benchmark gates pass.
Read the docsBenchmarks resolve into evidence.
Keystone keeps the path from primitive execution to export visible: run settings, phase metrics, throughput, memory profile, and report output.
Visualization remains analytical.
Charts are treated as inspection tools rather than decoration, with sorting, comparison, and realistic algorithm range pressure.
Quantum workload setup is explicit.
Batch scheduling exposes runs, shots, parameters, and backends so complex experiments can be repeated without guessing.
Sample comparisonAverage time, lower is better
ML-KEM (Kyber)Key encapsulation0.0060 ms512
ML-DSA (Dilithium)Digital signature0.0157 ms512
FalconDigital signature0.0108 ms1024
SPHINCS+Hash signature0.5033 msSHAKE
Export posture
Keep release claims honest until every platform is packaged.
macOS leads because it is the current local package target. Windows and Linux remain visible as planned paths, not finished promises.
verify-nativebuild-addonverify-crypto-addonsbuild-benchmarkspackage-mac-prod
Download
Start with the Mac build. Keep the rest in the release path.
Keystone’s primary package is macOS first. Windows and Linux follow after native artifacts are built and smoke-tested on their target operating systems.
macOS
Apple Silicon and Intel, DMG release path.
Windows
NSIS package target, validation pending.
Linux
AppImage target, distro validation pending.