PQC Solutions Compared
Choosing a post-quantum cryptography solution depends on your use case, infrastructure, and operational requirements. This page provides an objective comparison of Qpher against other PQC options.
Comparison Table
| Feature | Qpher | liboqs | AWS KMS PQC | Google Cloud KMS PQC |
|---|---|---|---|---|
| Type | Managed API | Library | Cloud KMS | Cloud KMS |
| Setup time | 5 min (API key) | Hours (compile C) | Minutes (IAM config) | Minutes (IAM config) |
| Key management | Built-in (versioned, rotatable) | DIY | Built-in | Built-in |
| Private key custody | Qpher enclave | Your infrastructure | AWS | |
| PQC algorithms | ML-KEM-768, ML-DSA-65, X-Wing, Composite-ML-DSA | 50+ algorithms | ML-KEM (limited) | ML-KEM (limited) |
| Hybrid PQC+Classical | Yes (X-Wing, Composite-ML-DSA) | Manual | No | No |
| Digital signatures | ML-DSA-65 | Multiple | No PQC sigs | No PQC sigs |
| Key wrapping | Yes (KEM-DEM) | DIY | Yes | Yes |
| Multi-tenant | Built-in | DIY | Per-account | Per-project |
| SDKs | Python, Node.js, Go | C, Python | AWS SDKs | Google SDKs |
| Pricing | Free tier, from $99/mo | Free (OSS) | Pay-per-use | Pay-per-use |
| Vendor lock-in | Low (REST API) | None | High (AWS) | High (GCP) |
| FIPS 140-3 validation | Pre-certification | Not validated | In progress | In progress |
When to Choose Qpher
- You want PQC as a service without managing cryptographic infrastructure, key storage, or algorithm updates
- You need both KEM encryption AND digital signatures — AWS and Google Cloud KMS PQC currently offer only KEM
- You want hybrid PQC + classical algorithms — X-Wing KEM (X25519 + ML-KEM-768) and Composite ML-DSA (ECDSA P-256 + ML-DSA-65)
- You need multi-tenant key isolation — each tenant gets isolated key pairs with version management
- You are building a B2B SaaS that needs to offer quantum-safe cryptography to your own customers
When NOT to Choose Qpher
- You need offline or embedded crypto — use liboqs for local, in-process cryptography with no network dependency
- You are already deep in AWS/GCP and only need KEM — use your cloud provider's native KMS PQC offering
- You need algorithms beyond ML-KEM-768 / ML-DSA-65 — liboqs supports 50+ algorithm variants
- You require FIPS 140-3 validated modules today — Qpher is pre-certification; check back for updates
- You need sub-millisecond latency — network round-trips add latency; use liboqs locally for raw speed
- You want zero vendor dependency — liboqs is open-source with no service dependency
Detailed Comparison
vs liboqs
liboqs is the reference open-source PQC library. It provides the raw cryptographic primitives that Qpher builds upon.
| Aspect | Qpher | liboqs |
|---|---|---|
| Key storage | Managed, encrypted at rest | You handle storage |
| Key rotation | Built-in API | You implement |
| Audit logging | Built-in | You implement |
| Deployment | API call | Compile C, link, deploy |
| Algorithm breadth | 4 algorithms | 50+ algorithms |
| Latency | ~150ms (network) | <1ms (local) |
Bottom line: Use liboqs when you need local speed and algorithm variety. Use Qpher when you want managed key lifecycle and operational simplicity.
vs AWS KMS PQC
AWS KMS added post-quantum TLS key agreement in 2024. It supports ML-KEM for key encapsulation but does not yet offer PQC digital signatures.
| Aspect | Qpher | AWS KMS PQC |
|---|---|---|
| KEM encryption | Yes (ML-KEM-768) | Yes (ML-KEM) |
| Digital signatures | Yes (ML-DSA-65) | No PQC sigs |
| Hybrid modes | X-Wing, Composite-ML-DSA | TLS hybrid only |
| Multi-tenant | Built-in | Per-account IAM |
| Lock-in | Low (REST) | High (AWS SDK) |
Bottom line: If you only need KEM and are already on AWS, use AWS KMS. If you need PQC signatures or hybrid modes, choose Qpher.
vs Google Cloud KMS PQC
Google Cloud KMS supports ML-KEM for key encapsulation. Like AWS, it does not yet offer PQC digital signatures.
| Aspect | Qpher | Google Cloud KMS PQC |
|---|---|---|
| KEM encryption | Yes (ML-KEM-768) | Yes (ML-KEM) |
| Digital signatures | Yes (ML-DSA-65) | No PQC sigs |
| Hybrid modes | X-Wing, Composite-ML-DSA | No |
| Multi-tenant | Built-in | Per-project IAM |
| Lock-in | Low (REST) | High (GCP SDK) |
Bottom line: Same trade-off as AWS. If you are already on GCP and only need KEM, use Cloud KMS. If you need signatures or hybrid crypto, choose Qpher.
Migration Path
- From liboqs: See Migrate from liboqs for a step-by-step guide with before/after code examples
- From AWS/GCP KMS: Straightforward REST API swap — replace SDK calls with Qpher API calls; key generation creates new PQC keys on Qpher
- From RSA/ECDSA: See the Migration Guide for transitioning from classical cryptography