Selected work.

Three projects across compilers, simulation and post-quantum security. Client names are not shown.

A neutral-atom quantum startup

Performance and portability for a new system.

The challenge
The startup needed better performance from its system and a way to run on other hardware.
What we built
A custom compiler pass for noise-aware routing, dynamical decoupling to mitigate errors, and a flexible IR with a backend that could target other neutral-atom devices.
The result
A 3.1x reduction in circuit depth, giving higher-fidelity results, and portability to a second hardware vendor in 6 weeks.
Next steps
Tune the compiler for specific algorithms and explore more advanced error mitigation.

A pharmaceutical research lab

A hybrid pipeline for drug discovery.

The challenge
The lab wanted to speed up molecular simulation and be able to move to its own quantum backend later.
What we built
An ADAPT-VQE pipeline with the algorithm running on a GPU-accelerated simulator and classical optimization loops managed by a control server, transferable to the lab's in-house backend.
The result
A 30% reduction in compute cost and a significant speed-up in simulation times.
Next steps
Connect the pipeline to a larger quantum device and try more complex molecules.

A Web3 custodian

A wallet that resists classical and quantum attacks.

The challenge
The custodian needed to secure its digital-asset wallet against threats from both classical and quantum computers.
What we built
A post-quantum wallet using multi-party computation to protect private keys, with hybrid certificates so the move stayed backward compatible, and a zero-downtime migration.
The result
A quantum-resistant wallet that meets strict security and compliance requirements, migrated with no downtime.
Next steps
Ongoing security audits, and looking at other quantum security technology such as QKD.

What these projects have in common.

Different sectors, the same way of working.

  • Measured against a baseline

    Each project started with a number to beat and ended with a comparison.

  • Built to move

    The compiler targets a second vendor, the pipeline transfers to an in-house backend and the wallet migration stays backward compatible.

  • Handed over

    The client's team can run and extend what was built.

Could your project look like one of these?

Each is a different engagement type. You do not need to know which yours is before you call.

Describe your problem in a few lines. Book a technical scoping call.

  1. Compiler sprint

    The neutral-atom project is an example. One backend first, then a second vendor reached in 6 weeks.

  2. Simulation pipeline

    The pharmaceutical project is an example. A pipeline built on a simulator that can transfer to the lab's own backend.

  3. Security migration

    The custodian project is an example. A staged, zero-downtime move to post-quantum protection.

Common questions.

Are these results typical?
No. Each result belongs to one device, workload and baseline. A scoping call is where we say what is realistic for yours.
Why are client names not shown?
Selected work describes the projects without naming the clients.
Can you do the same for us?
Possibly, on the same engagement types. We would start by agreeing a baseline and one measurable result.

Have a similar problem?

Tell us about your hardware and your workload in a technical scoping call.

Book a technical scoping call