About
We work on two questions. Which cryptographic algorithms will your systems still trust in ten years, and which of your operational problems belong on quantum or hybrid hardware now.
Post-quantum migration turns out to be mostly an inventory and integration job.
That surprises people who expect it to be a cryptography problem. The algorithms are published, standardised and available. What nobody has is a reliable map of where their cryptography actually lives: which services negotiate which cipher suites, which certificates chain to what, which embedded device has a key baked into firmware nobody can rebuild.
Our background covers quantum optimization and machine learning research, applied cryptography, network engineering and security assurance. That mix matters more than cryptography alone, because the hard part of this work is the estate, not the maths.
The same combination applies on the optimization side. A quantum algorithm is worthless without an honest classical baseline, a correct problem encoding and the surrounding engineering to run it. Most quantum projects fail somewhere in that chain rather than at the physics.
We work with clients wherever they are: remotely by default, on site when a system needs hands on it. Our focus is energy, logistics and financial infrastructure, where the optimization problems are real and the cryptography is often decades old.
Position
You do not need to believe a fault-tolerant quantum computer arrives on any particular date. Harvest-now-decrypt-later already works, and standards bodies have already set deadlines. The migration is a decade of work regardless.
Position
Quantum hardware will not beat your solver across the board. It might beat it on a particular structure of problem, on a particular instance size. That is worth testing carefully and not worth assuming.
Position
In a variational algorithm the quantum device runs for under a second per iteration. Everything else, the optimiser, the transpilation, the data movement, is ordinary engineering that decides whether the thing works.
01
Six to eight weeks. We map your cryptographic estate or the target optimisation problem and deliver ranked, costed findings. The output is yours whether you continue or not.
02
A migration architecture or solution design, with a classical baseline and success criteria agreed before work starts. We also tell you what we expect to fail.
03
Production increments measured against the stage-two criteria. Your engineers work alongside ours so your team can run the result without us.
04
Monitoring, reassessment as standards change, and handover. Done properly, your next migration is a config change.
We keep a small delivery bench rather than a large one. These are the teams we build alongside when a project needs more hands than we carry ourselves.