## Does RIKEN's QURI SDK Adoption Signal a Maturing Quantum-HPC Software Stack in Japan?

Japan's most powerful supercomputer now has a unified software layer connecting it to two of the world's leading quantum systems. RIKEN has officially adopted QunaSys's **QURI SDK Enterprise** for the JHPC-quantum platform — a NEDO-commissioned project under Japan's Ministry of Economy, Trade and Industry — giving researchers access to [IBM Quantum](https://quantumintel.tech/companies/ibm) System Two ("ibm_kobe" at RIKEN's Kobe campus) and the trapped-ion system "Reimei" (a [Quantinuum](https://quantumintel.tech/companies/quantinuum) System Model H2, located at RIKEN's Wako campus in Saitama) directly from Fugaku's compute and pre/post nodes.

The practical implication is direct: researchers running workflows on Fugaku can now invoke quantum circuits on two architecturally distinct quantum backends — superconducting and trapped-ion — without leaving the supercomputer environment. QURI SDK Enterprise bundles the QSCI (Quantum Selected Configuration Interaction) and ADAPT-QSCI algorithm libraries, targeting quantum chemistry, materials science, and computer-aided engineering. On the HPC simulation side, the SDK supports MPI-based distributed parallelism via mpiQulacs on Fugaku's compute nodes and a cuQuantum-based backend on ROQUO, the JHPC-quantum GPU cluster built on NVIDIA GB200 NVL4 hardware.

---

## What Is the JHPC-quantum Project and Why Does It Matter?

JHPC-quantum is a platform development effort commissioned by NEDO, the New Energy and Industrial Technology Development Organization, with METI jurisdiction. Its explicit goal is building production-grade [hybrid quantum-classical](https://quantumintel.tech/glossary/hybrid-quantum-classical) workflows that bridge Japan's flagship HPC infrastructure with operational quantum hardware.

The hardware topology is worth mapping carefully, because it reflects deliberate architectural choices:

- **Fugaku** (RIKEN Center for Computational Science, Kobe): classical compute and pre/post nodes
- **ibm_kobe**: IBM Quantum System Two, co-located at R-CCS Kobe
- **Reimei**: Quantinuum System Model H2 trapped-ion system, at RIKEN Wako, Saitama
- **ROQUO**: JHPC-quantum's dedicated GPU supercomputer, NVIDIA GB200 NVL4-based

Pairing a superconducting system with a trapped-ion system is not coincidental. The two modalities offer very different trade-off profiles: IBM's superconducting transmon architecture offers faster gate speeds and scale, while Quantinuum's H2 trapped-ion system is known for high two-qubit [gate fidelity](https://quantumintel.tech/glossary/gate-fidelity) and all-to-all connectivity. Giving researchers a unified SDK that can schedule work across both, while offloading classical pre/post-processing to either Fugaku or ROQUO, is precisely the kind of software infrastructure the field has needed.

The fact that RIKEN's Test User Program already showed strong demand for QURI SDK Enterprise — cited directly by RIKEN R-CCS Division Director Mitsuhisa Sato as a driver of the adoption decision — suggests this isn't speculative demand. Users who encountered the SDK in an evaluation context wanted it permanently.

---

## QSCI: From Research Algorithm to National Infrastructure Tool

QunaSys CEO Tennin Yan described QSCI as "one of the most widely used approaches to quantum-HPC hybrid computing worldwide." That claim warrants scrutiny, but the algorithm's deployment context here lends it credibility. QSCI — Quantum Selected Configuration Interaction — is a hybrid approach that uses quantum hardware to identify the most relevant electronic configurations in a quantum chemistry problem, then hands that selected space back to classical HPC for high-precision post-processing. ADAPT-QSCI extends this with adaptive circuit construction.

The architectural fit with Fugaku is deliberate: QunaSys has prior work specifically optimizing QSCI for Fugaku, according to Yan's statement. RIKEN's adoption therefore isn't a cold deployment — it builds on existing algorithm co-development. For enterprise buyers evaluating quantum software vendors, this kind of deep HPC co-optimization is increasingly the differentiator. Generic circuit transpilers that sit on top of any backend are table stakes; algorithm libraries tuned to specific supercomputer memory and network topologies are harder to replicate.

---

## Skeptical Read: What This Doesn't Prove

Adoption by a national research institution is a strong validation signal, but several caveats apply.

**Scope is still research-grade.** The JHPC-quantum project and its user base are academic and government researchers. The source material notes applications "with a view to future practical applications" — language that acknowledges the gap between current capability and industry deployment. Quantum chemistry on NISQ-era or early fault-tolerant hardware still faces steep circuit depth and error accumulation constraints. QSCI's hybrid structure helps, but it doesn't eliminate those constraints.

**Hardware access is Japan-specific.** The ibm_kobe system is physically co-located at R-CCS Kobe; Reimei is at Wako. This architecture is not trivially reproducible by enterprise customers outside Japan. International researchers or companies hoping to replicate this setup face both logistical and access policy barriers.

**No performance benchmarks cited.** The announcement contains no gate fidelity numbers, circuit depth thresholds, or [coherence time](https://quantumintel.tech/glossary/coherence-time) data showing that the current hardware is performing adequately for the target chemistry applications. For buyers, this is a software-layer story, not a proof-of-quantum-advantage story.

---

## Industry Trajectory: Japan's Quantum Software Stack Is Consolidating

What this adoption signals at a national level is more significant than any single SDK deployment. Japan now has a coherent quantum-HPC integration path: METI policy funding through NEDO → RIKEN hardware deployment → QunaSys software layer → researcher access through Fugaku. That vertical integration of policy, hardware, and software within a single national framework is what countries like the US and UK are still assembling.

For quantum software companies globally, the RIKEN-QunaSys model illustrates a viable commercial motion: build algorithm libraries that are genuinely differentiated (QSCI with Fugaku-specific optimization), win a national lab deployment, use that as the anchor reference for industrial users who want the same workflow environment. QunaSys has stated intent to expand to additional devices and HPC environments and to pursue collaboration with research institutions and industry both domestically and internationally.

The NVIDIA GB200 NVL4-based ROQUO cluster is also worth noting for the GPU-quantum simulation angle. Using cuQuantum as the simulation backend on a modern NVL4 cluster means researchers can benchmark classical simulation limits before deciding which workloads genuinely benefit from quantum hardware — a disciplined approach that the broader industry should be replicating more systematically.

---

## Key Takeaways

- RIKEN has officially adopted QunaSys QURI SDK Enterprise for the JHPC-quantum platform, enabling Fugaku users to access IBM Quantum System Two and Quantinuum System Model H2 from a single software environment.
- The SDK includes QSCI and ADAPT-QSCI algorithm libraries targeting quantum chemistry, materials science, and CAE applications.
- On the simulation side, QURI SDK Enterprise supports MPI-distributed parallelism via mpiQulacs on Fugaku and a cuQuantum-based backend on ROQUO, the NVIDIA GB200 NVL4-based GPU cluster.
- The adoption was accelerated by demonstrated demand from JHPC-quantum's Test User Program, per RIKEN R-CCS Division Director Mitsuhisa Sato.
- JHPC-quantum is a NEDO-commissioned project under METI, giving it national strategic backing — not just academic curiosity.
- The announcement contains no hardware performance benchmarks; this is a software infrastructure story, not a quantum advantage claim.
- Japan is consolidating a coherent policy-hardware-software stack that other national quantum programs should benchmark against.

---

## Frequently Asked Questions

**What is QURI SDK Enterprise and what does it do?**
QURI SDK Enterprise is QunaSys's commercial quantum software development kit. It provides algorithm libraries — including QSCI and ADAPT-QSCI — for quantum-HPC hybrid workflows, along with backend support for IBM Quantum System Two, Quantinuum System Model H2, Fugaku, and the ROQUO GPU cluster. It is now the official SDK for RIKEN's JHPC-quantum platform.

**What is the JHPC-quantum project?**
JHPC-quantum is a quantum-HPC hybrid platform development project commissioned by NEDO (New Energy and Industrial Technology Development Organization) under Japan's Ministry of Economy, Trade and Industry. It links Fugaku, the ibm_kobe IBM Quantum System Two, and the Reimei trapped-ion system (Quantinuum H2) into a unified research platform.

**Why does RIKEN use both IBM Quantum and Quantinuum hardware?**
The two systems represent architecturally distinct quantum modalities — superconducting transmon (IBM) and trapped-ion (Quantinuum). They offer different trade-offs in gate speed, connectivity, and fidelity. Supporting both gives researchers the flexibility to route workloads to the most suitable hardware for a given application.

**What is QSCI and why is it relevant for quantum chemistry?**
QSCI (Quantum Selected Configuration Interaction) is a hybrid algorithm developed by QunaSys that uses quantum hardware to identify the most chemically relevant electronic configurations, then passes that selected space to classical HPC for precision computation. It is designed to extract practical value from current hardware without requiring deep fault-tolerant circuits.

**Does this mean quantum computers are ready for industrial chemistry applications?**
Not yet at scale. The JHPC-quantum deployment is aimed at research users, and the source material explicitly describes applications as forward-looking toward "future practical applications." QSCI's hybrid architecture helps manage current hardware limitations, but industrial deployment at the scale and reliability enterprises require remains a work in progress.