Home/Insights/Vendor tracker
Tracker

Who already ships post-quantum?

Post-quantum support in the products most organizations depend on. Use it to plan which of your systems can move now and which are waiting on a supplier.

Last reviewed Nov 2026
Vendor / productCategoryPost-quantum supportStatus
Google ChromeBrowserHybrid X25519MLKEM768 key exchange on by default (Chrome 131, Nov 2024), following an earlier Kyber-based hybrid in Chrome 124.Shipping
Apple iOS / macOS 26Operating systemHybrid ML-KEM key exchange for TLS in system networking APIs; iMessage PQ3 protocol since iOS 17.4.Shipping
CloudflareCDN / edgeHybrid post-quantum key agreement enabled by default for supporting browsers since 2023.Shipping
OpenSSL 3.5LibraryML-KEM, ML-DSA and SLH-DSA, with hybrid ML-KEM in the default TLS key-exchange groups (April 2025).Shipping
OpenSSH 10.0Protocolmlkem768x25519-sha256 is the default key exchange (April 2025); a hybrid NTRU Prime scheme was default from 9.0.Shipping
Go 1.24Languagecrypto/mlkem package; X25519MLKEM768 enabled by default in crypto/tls (February 2025).Shipping
Java (JDK 24)LanguageML-KEM (JEP 496) and ML-DSA (JEP 497) added to the platform (March 2025).Shipping
SignalMessagingPQXDH added post-quantum protection to its key agreement in 2023.Shipping
AWS KMSCloudML-DSA signing keys available in Key Management Service (2025).Partial
Microsoft WindowsOperating systemML-KEM and ML-DSA added to SymCrypt and Windows cryptography APIs, rolled out through 2025.Partial

“Shipping” means enabled by default in a generally available release. “Partial” means available for some services or behind configuration. Always confirm against the vendor’s own documentation for your version. Spotted something out of date? Tell us.

Find out what a quantum computer would break first.

Start with a free scan of your source code, or book a full posture assessment with our cryptographers.