All 35 PQ Crypta algorithms — real API timings, run in your browser against api.pqcrypta.com. From classical ECDH to Quad-Layer maximum security.
NIST FIPS 203NIST 2025 HQCLive DataDual-KEM
37 entries — 35 PQ Crypta API algorithms, the browser-native ECDH P-256 baseline, and Dual-KEM parallel.
Each runs 9 times (plus 1 warmup discarded). Median + min–max range reported. API timings include full round-trip to api.pqcrypta.com.
All 35 algorithms are selectable in Encryption and Streaming.
★ Dual-KEM runs ML-KEM-1024 + HQC-256 in parallel — total ≈ slowest single KEM, not the sum. This is how Share works.
Why these numbers matter
Per message, not per byte
The post-quantum work (key encapsulation, signatures) is done once per message, whatever its length; the AES-256-GCM layer that carries the data adds about a millisecond per megabyte. A 3-word note and a 10,000-word document cost almost the same. The exception is Post-ZK-Homomorphic: it encrypts every byte under TFHE (about 1.7 KB of ciphertext per byte, at most 4096 bytes), so its cost grows with the message.
Constant, not variable
Apart from Post-ZK-Homomorphic, the timings depend on the algorithm and security level, not on the message: every run uses the same 64-byte payload, and a larger one changes them only by the AES-GCM time above.
Front-loaded, not per session
Key generation pays most of the cost once. In longer sessions with reused keys, only the cheaper encrypt + decrypt phases apply — overhead amortises over time.
This is what runs in Share — ML-KEM-1024 + HQC-256 fired simultaneously. Two NIST Level 5 algorithms, two independent hard problems. Both must be broken to read a message.
run to see timings
Quad-Layermax security
4-layer encryption stack. The API's highest security mode. Upper bound of the performance envelope.