Qpher and other PQC options
How Qpher relates to cloud KMS post-quantum keys and local PQC libraries — and when Qpher is not the right tool.
Qpher and a cloud KMS
Google Cloud KMS and AWS KMS ship post-quantum key operations. They give you primitives — key encapsulation and signing. Qpher gives you the hand-off: encrypt on your device, sign in your name, deliver to someone outside your organization, and prove it later.
Data that stays in your own cloud
If your data is encrypted at rest with AES-256 in your own cloud, that layer is already quantum-safe. You need Qpher when the data has to leave — to a client, a counsel, a family member.
Validation status
We implement NIST FIPS 203, 204 and 205. ML-KEM key versions created on or after 2026-10-23 run inside the AWS-LC 3 Cryptographic Module (version AWS-LC FIPS 3.1.0), which NIST's CMVP has validated (certificate #5298), for keys the module generated; earlier ML-KEM key versions, the ML-DSA and SLH-DSA signatures and the hybrid modes are not covered by any CMVP validation.
What Qpher can see
Qpher is not zero-knowledge. Private keys are generated and used only inside an isolated key service and are never exported; on client-side paths (Vault, Organization send, .qpher) Qpher never sees the plaintext; the API's server-side mode receives plaintext over TLS, processes it in memory and does not store it.
When Qpher is not the right tool
- Offline or embedded cryptography — Every Qpher operation is a call over the network; for cryptography inside a device or without a connection, use a local PQC library.
- Sub-millisecond latency — Each operation includes a network round-trip to Qpher.
- Data stored outside the US — Data is stored in the United States on Google Cloud and in Cloudflare's eastern North America region; there is no EU or other regional data-residency option today.
- Keys in your own cloud account — Your private keys are generated and used only inside Qpher's isolated key service; they cannot be exported to your cloud KMS or HSM.
Migration
- From liboqs — Migrate from liboqs: step-by-step, with before-and-after code.
- From RSA or ECDSA — Migration Guide: moving from classical cryptography.