Skip to main content

Why Qpher?

You need Qpher when the data has to leave — to a client, a counsel, a family member.

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.

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.


What you get​

1. Key lifecycle management​

Every PQC key in Qpher has an explicit version number and a defined lifecycle:

active → retired → archived
  • Active keys can encrypt, decrypt, sign, and verify
  • Retired keys can only decrypt and verify (no new operations)
  • Archived keys cannot perform any operations; archiving is irreversible and is done in Qpher Console only

Key rotation is a single API call. The new key becomes active immediately, and the previous key transitions to retired status. There is no downtime, and every transition is recorded in the audit log.

2. Security by default​

  • Non-exportable keys — Private keys are generated and used only inside Qpher's isolated key service. No API can export them.
  • Fail-closed policy engine — API requests pass a policy engine that fails closed.
  • Timing-safe comparisons — All hash and token comparisons use constant-time algorithms to prevent timing side-channel attacks.
  • Tenant isolation — Each customer gets a separate tenant, isolated at four layers: repository filtering, database constraints, request context and gateway enforcement.

3. Auditability​

Qpher records every cryptographic operation in a tamper-evident audit log:

  • Every log entry is linked to the previous entry via a SHA-256 hash chain, so altering or removing any entry invalidates every entry recorded after it
  • You can re-derive the chain yourself through the verification endpoint. This detects modification of individual entries
  • A daily job signs a checkpoint of each chain with a platform-held Dilithium3 key (checkpoints exist from August 2026 onward). A verified checkpoint detects rewriting of the chain by an actor with database write access but not the KMS signing identity; it does not survive compromise of that signing identity itself
  • Audit logs are retained for the life of your account and for 24 months after the account is deleted; accounts with an armed Legacy policy are exempt from deletion while the policy is armed.
  • Admins export the organization's hash-chained audit log from Qpher Console and verify it. Which plans include it: qpher.ai/plans.

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.
  • Transport security — Qpher encrypts documents and keys, not the connections your systems make; for data in transit, use a TLS stack with post-quantum key exchange.

Getting Started​

Ready to try it? The Quickstart Guide walks you through your first quantum-safe API call in under 5 minutes.

Want to understand the security architecture first? Read the Threat Model to see exactly what Qpher protects and where the trust boundaries lie.