Quantinuum, Rolls-Royce, Riverlane, and EPCC (the UK's national supercomputing centre, based at the University of Edinburgh) announced an agreement on July 14, 2026, to explore what quantum computing would need to look like to fit into real industrial design workflows, with gas turbine design named as the specific target. This is not a first contact between the parties. It builds on prior work between Rolls-Royce, Riverlane, and EPCC that already laid groundwork on the algorithmic, error-correction, and data requirements for tackling fluid dynamics problems with quantum hardware, which is the detail that separates this from a cold-start pilot.
Who is contributing what
The agreement splits responsibility along each party's own expertise rather than bundling everyone into a vague joint statement. Quantinuum provides access to its quantum systems and software stack. Rolls-Royce contributes the industrial design use cases and the domain knowledge needed to know whether a result is useful to an engineer, not only computationally interesting. Riverlane brings quantum error correction and algorithmic expertise, an area it specializes in independent of any single hardware vendor. EPCC contributes supercomputing expertise and the hybrid-workflow integration work needed to connect a quantum processor to a classical simulation pipeline rather than treating it as a standalone tool.
Why gas turbine design is a real test case, not a marketing one
Gas turbine design depends heavily on computational fluid dynamics, a class of problem that is genuinely expensive to simulate classically and has long been cited, correctly, as a plausible quantum use case. That plausibility has not translated into much published, concrete progress industry-wide, which is exactly why the prior Rolls-Royce and Riverlane fluid-dynamics groundwork matters here. The plan under this agreement is to test key computational building blocks, not full turbine simulations, on Quantinuum's Helios system now, and assess how those building blocks would scale on Quantinuum's planned Sol and Apollo systems.
What "computational building blocks" signals
Naming building blocks rather than a finished application is a narrower and more honest scope than most industrial-quantum announcements set for themselves. It suggests the collaborators are testing whether specific subroutines, the kind of thing that needs to work correctly and efficiently before a full fluid-dynamics algorithm runs on quantum hardware at all, behave the way theory predicts on Helios today. That is a slower, more verifiable path than announcing a turbine simulation result before the underlying pieces are proven out.
How this compares to Quantinuum's other industrial partnerships
Quantinuum's multi-year partnership with BMW runs on a similar structure: named hardware generations (Helios, Sol, Apollo), a specific scientific problem rather than a generic industry reference, and a track record of prior collaboration behind the new announcement. The Rolls-Royce agreement follows the same pattern, industrial design and fluid dynamics in place of electrochemistry, which suggests Quantinuum is running a repeatable playbook for these deals rather than a one-off press moment.
What to watch next
The next real signal is whether Riverlane or EPCC publishes a technical result on which specific building blocks ran successfully on Helios, and how the projected scaling to Sol and Apollo compares against the actual hardware once those systems ship. Our use cases overview tracks which quantum applications, across industries, have moved past the building-blocks stage into results run on real hardware.