Who it is for
Organizations with an inventory, readiness decisions, and a specific system or protocol that is suitable for controlled post-quantum engineering work.
PQC migration service
Test and migrate a defined post-quantum path
Move a selected system or protocol from roadmap to controlled engineering work with documented architecture, interoperability, performance, and operational limits.
Laboratory prototype or scoped implementation — evidence level stated per engagement
What we need to begin
- A selected use case with an identified owner and decision objective
- Relevant inventory and readiness findings, including unresolved risks
- A safe test environment, representative integrations, and rollback boundaries
- Confirmed platform, protocol, provider, and compliance constraints
What we engineer and test
- Algorithm and protocol fit for the selected use case and supported implementation
- Interoperability across clients, services, libraries, providers, and fallback paths
- Performance, resource, certificate, message-size, and operational effects
- Key, identity, deployment, monitoring, rollback, and incident-response implications
- Residual risks, unsupported dependencies, and production decision gates
What you receive
- A documented architecture decision and evidence level
- A controlled laboratory prototype or narrowly scoped implementation
- Reproducible compatibility and performance test results
- A deployment, rollback, monitoring, and follow-up backlog for the defined scope
How the engagement works
- 01
Select
Confirm the use case, success measures, supported standards, environment, and stop conditions.
- 02
Design
Document the architecture, dependencies, trust boundaries, operational path, and alternatives.
- 03
Prototype
Implement and test in the agreed environment with reproducible compatibility and performance evidence.
- 04
Decide
Record limitations, residual risk, rollback needs, and whether production work is justified.
Standards and evidence basis
Implementation choices are limited to established platform and provider capabilities. Evolext does not create custom cryptographic primitives.
Standards and guidance last reviewed: 5 August 2026.
Final standards
NIST FIPS 203, 204, and 205
Define standardized ML-KEM, ML-DSA, and SLH-DSA algorithms used only where the selected platform and protocol support them.
Final guidanceNIST CSWP 39upd1 — Crypto Agility
Informs replaceability, transition controls, dependencies, and continued operation during change.
Initial public draftNIST IR 8547 — PQC Transition
Provides draft transition context and is not presented as a final implementation mandate.
Important limitations
- A laboratory prototype is not evidence that the same design is production-ready or universally quantum-safe.
- Production deployment depends on the selected protocol, platform, provider support, operational controls, and client approval.
- The service does not replace independent security review, compliance assessment, or ongoing cryptographic lifecycle management.
Prepare the migration
Crypto Inventory / PQC Readiness Scanner
A tool-assisted engagement that maps observable cryptographic use, ownership, dependencies, and evidence gaps.
Quantum-Safe Readiness Assessment
A business and technical assessment covering data longevity, vendor readiness, migration constraints, and priorities.