Data stolen todaycan be read tomorrow.
Attackers can store your encrypted traffic now and decrypt it once quantum computers are strong enough. We find where your systems still use encryption that will be retired after 2030, and give you a plan to move before your data runs out of time.
4 of 6 hosts run out of time by 2030.
- api.northwind.exampleX25519MLKEM768past 2035
- shop.northwind.exampleX25519until 2030
- pay.northwind.exampleECDHE P-256until 2030
- vpn.northwind.exampleTLS 1.0 · RSAalready out
- legacy.northwind.exampleTLS 1.1 · RSAalready out
- files.northwind.exampleno answer on 443unknown
Harvest now, decrypt later
- TodaySomeone records your encrypted traffic. It can't be read yet.
- For yearsThe recording is stored and waits. Storage is cheap.
- LaterOnce quantum computers are strong enough, today's RSA and elliptic-curve keys can be broken and the data read.
So the question is not when quantum computers arrive. It is how long your data must stay secret.
The clock is already set
Standards bodies have fixed the dates. Systems that still rely on RSA or elliptic-curve cryptography will need to change, and data captured before the switch stays exposed.
- End of 2026EU: national transition plans and cryptographic inventories start
- 2030NIST: RSA and ECC deprecated. EU: high-risk systems migrated
- 2035NIST: RSA and ECC disallowed. EU: remaining systems migrated
Sources: NIST IR 8547 (Oct 2026), EU Coordinated Implementation Roadmap for PQC (June 2025).
How long must your data stay secret?
Pick a type of data. We compare how long it must stay confidential with the retirement dates of today's encryption.
Already late for data in transit today. Use hybrid post-quantum encryption first on this system.
What we check
- Public endpointsTLS versions, post-quantum hybrid key exchange (X25519MLKEM768) and fallback behaviour on every domain and subdomain in scope.
- CertificatesSignature algorithms, key types and sizes, expiry and the chain behind each certificate.
- Your source codeWhere RSA, ECDSA, ECDH and weak algorithms are used, and which crypto libraries and versions you depend on. Delivered as a cryptographic inventory (CBOM).
- Your dataA short workshop with your team to set how long each type of data must stay secret.
What your connections actually negotiate, not only what your servers offer. From Cloudflare, the share of real requests that already use post-quantum key exchange, per hostname. From the Signal sensor inside your network, the same for internal services, VPN and remote access, and the connections your systems open to suppliers and cloud services. We read only the handshake, never the content.
- Cloudflarepublic hostnames
- Signal sensorinternal services, VPN, suppliers
How it runs
- Scope
You give us your domains, repositories and the systems that hold sensitive data.
- Scan
We check endpoints, certificates and code, and live traffic from Cloudflare or the Signal sensor where available.
- Prioritise
We match every finding with how long the data behind it must stay secret.
- Plan & retest
You get a migration plan in order of urgency. Every assessment includes a retest.
What you get back
- An inventory of where quantum-vulnerable cryptography is used
- A status for every asset: PQC hybrid, classical only, outdated TLS or unknown
- A migration plan ordered by how long your data must stay secret
- A retest after you migrate
Quantum Readiness tells you where you stand and what to fix first. It does not certify that your data is safe for a given number of years.
4Tify's own platform already runs on post-quantum encryption.
- Priority 1pay.northwind.examplePayment records, 10 yearsEnable hybrid key exchange on the load balancer
- Priority 2vpn.northwind.exampleRemote accessReplace TLS 1.2-only VPN appliance
- Priority 3shop.northwind.exampleCustomer accounts, 5 yearsUpgrade TLS library to a version with ML-KEM
Join the closed beta
Quantum Readiness is open to a small group of companies while we finish it together. Beta users get a full assessment, the migration plan and a retest. Pricing is set per company.
- 1You request access.
- 2We agree the scope with your team.
- 3We run the checks and the data workshop.
- 4You get the report and the migration plan.
Not sure where to start? Talk to us first.
Talk to an expert