TLS key exchange on the gateway
- Before
- X25519
- After
- X25519MLKEM768
- Classical-only client
- still connects
patch sha256:9f2c…e41a, approved by [NAME], [DATE]
Post-quantum, proven.
CritiQo inventories your cryptography, migrates it to hybrid and then to pure post-quantum, and proves every step. Your code never leaves your infrastructure.
Cryptography nobody has listed.
The problem
Today’s tools tell you what to change. Then the plan becomes a runbook that someone executes by hand, for years, and nobody can show an auditor that each change was right.
Why it matters now
Traffic captured today can be decrypted once a cryptographically relevant quantum computer exists, and anything signed today can be forged. Migrating an organisation takes years, so the deadlines below are closer than they look.
End of 2026
- EU: first steps and cryptographic inventories
Dec 2027
- EU Cyber Resilience Act: crypto-agility in products with digital elements
End of 2030
- EU: high-risk systems migrated
- US: key establishment for high-value federal systems
- NIST IR 8547 (draft): 112-bit RSA and ECC deprecated
End of 2031
- US: signatures for high-value federal systems
End of 2035
- EU: medium-risk systems migrated
- NIST IR 8547 (draft): RSA and ECC disallowed
Sources: EU NIS Cooperation Group, Coordinated Implementation Roadmap v1.1 (June 2025); EU Cyber Resilience Act; US Executive Order 14412 (June 2026); NIST IR 8547, initial public draft.
Four steps, each with its evidence.
- 01
Discover
CritiQo observes your cryptography instead of asking about it: the code, what your servers actually negotiate, your images and certificates. Every finding says how it is known.
Observed, inferred or suspected. Only what is observed gets migrated.
- 02
Prioritise
Each finding is ranked by risk horizon, Mosca’s inequality and regulatory deadlines with sources, into four waves: migrate now, prepare, plan, watch.
Every decision is explained in one sentence you can forward.
- 03
Migrate
Before touching anything, a dry run shows what would change and what would break. The change runs on a copy of the repository, in a sandbox with no network, and arrives as a pull request.
The agent cannot merge. The server prevents it, not just the code.
- 04
Prove
Each change is verified before and after, against a real deployment and against an independent cryptographic implementation. Only a later scan can mark it resolved.
And it always says what it did not check.
We catch it before anything breaks.
An ML-DSA-65 signature is 3,309 bytes. Your column holds 128. CritiQo follows a signature to where it is stored, which constants assume its size and which tests depend on it, before it changes a single line.
ECDSA P-25672 B
ML-DSA-6572 B
signature VARCHAR(128)
ProposedWiden the column first. The algorithm change waits until it is done.
Verified
First hybrid. Then pure post-quantum.
Executing each phase is not the hard part. Knowing when you can take the next step without breaking anything is.
ClassicalPost-quantum
- Phase 1
Compatible
Add post-quantum without removing anything. Old clients keep connecting.
- TLS
- X25519MLKEM768 ahead of the classical groups
- Signatures
- Dual signature: ECDSA + ML-DSA
- Phase 2
Strict
Require the new algorithm once every consumer understands it. CritiQo tells you when you can.
- TLS
- Classical-only groups removed
- Signatures
- Verifiers require ML-DSA
- Phase 3
Pure post-quantum
Retire the classical algorithm, if your policy allows it.
- TLS
- ML-KEM only
- Signatures
- ML-DSA only
Guarantees
The AI proposes. Deterministic code decides. A person approves.
Sovereign
The language model runs on your infrastructure. Neither your code nor your findings leave it. The full demo runs on a laptop with no internet.
A person in command
No change is applied without your approval, and the approval is bound to the exact patch you saw. The agent cannot merge.
Verified
The model only steps in where the question is about language. Scoring and verification are deterministic, and each result lists what it did not check.
Where CritiQo fits
Posture platforms tell you what to change. CritiQo changes it, checks it breaks nothing and proves it. It consumes their findings instead of competing with them.
| Capability | Posture platforms | Generic code agents | CritiQo |
|---|---|---|---|
| Inventories the whole organisation | Yes | No | Partly |
| Suggests the fix and its root cause | Yes | Partly | Yes |
| Makes the change | No | Yes | Yes |
| Checks what the change would break | No | No | Yes |
| Verifies against an independent implementation | No | No | Yes |
| Keeps your code on your infrastructure | Yes | No | Yes |
Try it on one of your repositories.
A pilot on your infrastructure, with your code and your team. Nothing leaves your network, and nothing changes without your approval.
Or write to contact@critiqolabs.com