HPC Quantum

HPC – Quantum Synergies

GPU-accelerated simulation, hybrid quantum-classical workflows, and multi-backend portability.

Synergy A1

GPU-Accelerated Quantum Simulation as the "Quantum Dev Loop"

In practice, most quantum R&D cycles rely heavily on simulation (state-vector, tensor-network, noise models), especially for:

With modern GPUs, this becomes a native HPC workload. GPU-accelerated quantum simulators (state-vector, tensor-network) run on the Kubernetes platform and leverage the GPU stack (e.g., CUDA-Q / cuQuantum), with targets like ≥32-qubit simulations per GPU.

Why it matters: This makes quantum capability scalable today, without waiting for large fault-tolerant machines.
Synergy A2

Hybrid Quantum-Classical Workflows (HPC as Orchestrator)

Even when you run on real quantum hardware, you almost always do hybrid loops:

1 Classical optimizer (HPC) → proposes parameters 2 Quantum circuit execution (simulator or QPU) → returns measurements 3 Classical post-processing (HPC) → updates optimizer 4 Repeat

This is exactly where HPC shines:

The platform direction already anticipates this style of operation by packaging quantum tooling into the same managed environment where Kubernetes workflows, CI/CD, and GPU workloads live.

Synergy A3

Multi-Backend Portability (Avoid Vendor Lock-in)

A major accelerator for research and commercialization is being able to move between:

Simulator → QPU A → QPU B

Or between modalities like ion traps vs superconducting devices

The planned CUDA-Q approach explicitly includes integrations to multiple hardware providers (ion-trap and superconducting options). This enables: