Hall 6 · Exhibit 1 1 min
Who's Already Using PQC
Chrome, Signal, Apple, Meta, and more
Chrome + CloudflareHybrid TLS live for most users
MessagingApple PQ3 · Signal PQXDH (ML-KEM)
LibrariesOpenSSL · BoringSSL · liboqs
TakeawayPQC is in production today
is not a future technology — it is deployed in production today across some of the world's largest platforms.
| Platform | Implementation | Notes |
|---|---|---|
| Chrome + Cloudflare | Hybrid TLS (X25519 + ML-KEM-768) | Live — most Chrome users doing PQC |
| Apple iMessage | PQ3 protocol (ML-KEM) | Deployed across iOS/macOS |
| Signal | PQXDH protocol (ML-KEM) | PQC key exchange in production |
| Meta | Hybrid PQC internally | ML-KEM + ML-DSA across infrastructure |
| BoringSSL / OpenSSL | ML-KEM + ML-DSA integrated | Backend for Chrome, Android, most servers |
| LibOQS (PQCA) | Open-source PQC library | Linux Foundation; Meta contributes |
| Certificate Authorities | Testing ML-DSA for TLS certs | Let's Encrypt, GlobalSign |
Key Takeaways
- Most Chrome users are already performing PQC handshakes via X25519 + ML-KEM-768
- Signal, Apple iMessage, and Meta have deployed PQC in production messaging
- OpenSSL and BoringSSL have integrated ML-KEM and ML-DSA