The next era of computing will be shaped by bringing different computing resources together, and quantum has earned a place in that conversation. At SC26 in Chicago, Quantinuum is showing how we’re bringing that hybrid integration to life today.
Consider a researcher studying a molecule. Classical computers prepare the problem, a quantum computer contributes a calculation, and classical computers analyze the results. Those steps may run on different machines, in different locations. Connecting them into a coordinated workflow is essential to making the application useful.
Quantinuum Nexus is our developer platform that helps manage those connections. It brings quantum programming, testing and execution into one environment and provides the foundation to coordinate quantum calculations with the surrounding classical work. Researchers can focus on the scientific problem without writing custom software to manage every handoff between systems.
Making these connections easier helps more people build quantum applications, including those whose expertise lies in the scientific and industrial problems they want to solve.
Connecting quantum programs to the wider computing environment
A researcher studying a molecule or material needs more than access to a quantum processor. A hybrid application can involve classical preparation, HPC simulation, quantum execution and post-processing. Each stage needs particular resources and may depend on results from an earlier calculation.
As the application grows, coordinating those steps becomes a development challenge. Developers need to specify which tasks can run independently, which must wait for results, and where each task should execute. The resources also operate on different timescales. A quantum job may be waiting in a queue or running remotely. During that time, valuable HPC resources should remain available for other work.
Nexus’ Hybrid Workflow Runtime helps address this challenge. Developers express how the quantum and classical tasks depend on one another, and the runtime coordinates their execution across the relevant resources. Its asynchronous approach allows work to progress without requiring every resource to remain active or blocked while another task completes. This connects quantum job submission to the surrounding classical application, reducing the need for developers to write bespoke logic.
Hybrid workflows in practice: Chemistry with RIKEN
Our work with RIKEN illustrates the scientific workflows this coordination can support.
Calculating how electrons behave in a molecule is central to understanding its properties. These electronic-structure calculations help researchers investigate questions relevant to chemistry and materials science, but they can become increasingly demanding as the problem grows.
RIKEN’s quantum residual exploration method combines quantum and classical contributions to that calculation. Quantum measurements suggest additional electronic configurations—possible arrangements of electrons—which classical routines assess and select for the final calculation.
In a demonstration involving a stretched 12-atom hydrogen chain, the quantum-generated proposals lowered the calculated energy compared with classical-only selection using the same final number of configurations. This improved the energy estimate within that specific comparison.
Our developer tools and platform connected the stages of the application. Guppy expressed the quantum logic, Hybrid Workflow Runtime (Tierkreis) coordinated the quantum and classical tasks, and Nexus provided the submission interface for quantum execution. Researchers could develop the application without manually coordinating every handoff.
Working with the infrastructure computing centers already use
As hybrid applications develop, their workflows need to adapt to different resources, tools and operating practices.
That makes interoperability a design requirement for Nexus. Developers should be able to choose resources suited to their application. Computing centers need flexibility to build on existing investments and evolve their infrastructure over time.
HPC scheduling is one example. Quantinuum supports connections to workload managers including Slurm, PBS, and PJSub, enabling developers to build around the scheduling infrastructure at their computing center.
With Slurm, Hybrid Workflow Runtime can submit classical tasks to a Slurm-managed environment while quantum jobs are submitted through Nexus. The runtime coordinates the task dependencies, while Slurm allocates the compute resources those tasks need, across both HPC and now QPUs as well given the recent expansion to Slurm announced by NVIDIA to include quantum resources.
Interoperability extends beyond scheduling. A computing center may combine workflow tools, resource-management software and quantum hardware from several providers. Defined interfaces help those components work together as the environment changes.
One example is the Open Quantum-HPC Software Ecosystem, or OpenQSE, a community effort led by Oak Ridge National Laboratory. Its reference architecture defines boundaries across the hybrid computing stack to help different implementations work together. Within that architecture, Nexus' Hybrid Workflow Runtime sits at the application workflow layer, above scheduling and resource-access software. Interfaces such as QRMI and QDMI provide connections toward quantum systems.
Our SC26 demonstration in Chicago illustrates this division of responsibilities. Hybrid Workflow Runtime orchestrates the application, assigning classical chemistry tasks to a shared Slurm executor with an explicit resource profile. The runtime coordinates task dependencies, while Slurm handles placement and hybrid compute resource allocation. The workflow can then interact with QFw to reach quantum execution targets.
Explore the SC26 demonstration here.
Building toward fault-tolerant hybrid applications
The applications researchers develop today also help build the expertise needed for increasingly capable quantum computers.
The Nexus fault-tolerance roadmap is intended to support that transition. Supported error-correction encoding, emulation and execution on Helios already provide a starting point. Future releases aim to simplify more of the work involved in developing and deploying quantum applications as the hardware advances.
Through Nexus, we are connecting quantum programming with hybrid deployment. Our goal is for the applications, workflows and expertise users develop today to provide a foundation they can carry forward into the fault-tolerant era.
That preparation involves learning how to formulate a useful problem, test an approach, evaluate results and coordinate the computing resources needed to run the application. Making those steps easier helps more people contribute, including researchers whose expertise lies in the scientific and industrial problems they want to solve.
Join us at SC26
At SC26, we’re bringing these pieces together: quantum hardware, developer tools, and the connections that make hybrid applications possible within existing HPC environments.
You can visit Quantinuum at Booth 4838 in the Quantum Junction, November 17–19 at McCormick Place, Chicago. See our hybrid workflow demonstration and join more than 15 booth theater sessions with Quantinuum experts and partners including NVIDIA and Oracle.
Bring your questions about connecting quantum to your HPC environment, developing hybrid applications, and preparing for what comes next.
Book time with our experts, explore the Nexus roadmap, or get started with Nexus.





