Your encryption won't survive the quantum era.

Qypher finds every key, certificate and algorithm a quantum computer will break, maps the exposure to RBI, MAS and CBUAE, and generates the post-quantum migration artifacts your team deploys.

Frequently asked questions

What does Qypher actually do?

Qypher's agents discover every cryptographic asset across your infrastructure - external endpoints, internal services, cloud, code, and vendor integrations - score each one for quantum exposure, generate a regulator-ready Cryptographic Bill of Materials (CBOM), produce a prioritised migration plan, and generate the actual migration artifacts - PQC keys, certificates, CSRs, and hybrid-TLS configurations - staged in your environment for your team to deploy. Orchestrated execution, where Qypher makes the change with your approval and rolls back on failure, is what we are building next.

Does Qypher migrate my cryptography, or just tell me what to fix?

Today, more than a plan but not yet hands-off execution. Qypher discovers and scores, then generates the real migration artifacts: post-quantum keys (ML-KEM, ML-DSA), certificates, CSRs, and hybrid-TLS configurations, staged in your environment so your team deploys them through your own change control. Orchestrated execution (you approve each change, with impact simulation and rollback) is in active development, followed by automation within guardrails you set. We label what ships and what is building, and we will not tell you otherwise.

What is a CBOM and why will my auditor ask for one?

A Cryptographic Bill of Materials is a structured inventory of every cryptographic asset your organization uses - certificates, keys, algorithms, protocols, and their configurations. Regulators including CERT-In, and frameworks like SEBI CSCRF and the EU coordinated roadmap, increasingly expect organizations to maintain cryptographic inventories as the foundation of quantum-readiness. Qypher generates yours as a signed CycloneDX 1.6 file, re-run on demand or on a schedule you set.

When are the post-quantum deadlines?

It depends on where you are regulated. Singapore CII owners, including major banks, must file a quantum-safe migration plan by 31 March 2027 and finish by end-2031. India's DST roadmap targets CII foundations by December 2027 and full adoption by 2029 (advisory). The EU wants member states to begin the transition by the end of 2026 and migrate high-risk systems by 2030. In the US, EO 14412 binds federal agencies to 2030 for key establishment and 2031 for signatures, and NIST's draft IR 8547 proposes deprecating RSA and ECC after 2030 and disallowing them after 2035. Because migration takes years, discovery needs to start now.

What is "Harvest Now, Decrypt Later" and does it affect me?

Harvest Now, Decrypt Later (HNDL) is an attack where adversaries intercept and store encrypted data today, planning to decrypt it once quantum computers arrive. Any data with long-term sensitivity - financial records, health data, KYC, intellectual property - encrypted with RSA or ECC is already at risk if it is being captured now. Moving key exchange on those data flows to post-quantum (in practice, hybrid X25519 + ML-KEM) is the defence, and it has to happen before the data is captured.

Which regulations and regions does Qypher cover?

Findings are mapped today to our core markets: RBI, SEBI CSCRF and CERT-In in India; MAS and the CSA Quantum-Safe Handbook in Singapore; the UAE National Encryption Policy and CBUAE; and NIST standards in the US. We also track the EU roadmap, DORA, UK NCSC, the G7 finance roadmap and other national guidance on our roadmap page, so you can see every deadline that touches you.

How is Qypher different from a scan-and-report tool?

Most cryptographic-discovery tools deliberately stop at a plan and hand it to your team - they never touch production. Qypher goes one step further: it generates the working migration artifacts - keys, certificates, CSRs, configs - mapped to the regulation your auditors answer to, so your team deploys a fix instead of starting from a to-do list. Orchestrated execution with your approval is the next step we are building. Keys never leave your environment.

How long does an assessment take?

The free external scan needs nothing from you but a domain: about 60 seconds, no login, and you can download the full report. The internal assessment is automated rather than a weeks-long manual audit; how long it takes depends on the size of your estate and the access you grant. After that, re-scans run on a schedule you set, with alerts when your score drops or a certificate nears expiry.

Who is Qypher built for?

Regulated enterprises - especially in banking, financial services, and other sectors handling long-lived sensitive data under active regulators. Qypher is designed for CISOs, compliance teams, DevOps, and application owners to work on quantum readiness in one workspace, with viewer, member and admin roles, sign-in history, and an audit log you can export.

Latest research