Skip to main content

​
Overview

IQM’s superconducting quantum computers are available in the Haiqu SDK through IQM’s Resonance platform. This integration lets you run circuits directly on IQM QPUs such as Garnet, Emerald, and Sirius — using IQM’s native gate set (R, CZ, Measure) — without leaving the Haiqu SDK.

​
Key Features of the Integration

Direct Resonance access: Execute quantum programs on IQM’s superconducting QPUs straight from the Haiqu SDK — no AWS Braket account required.Dynamic device discovery: IQM devices are enumerated live from Resonance, so haiqu.list_devices() always reflects what your account can reach.Mock simulators: Every device has an ideal :mock variant that runs a server-side noiseless simulation with the device’s real topology — perfect for validating a circuit before spending QPU time.

​
How to Access QPUs via IQM Resonance

1

Obtain an IQM Resonance API token

Create an API token in the IQM Resonance dashboard. This token authorizes access to the quantum computers available to your Resonance account, and hardware usage is billed to that account.
2

Configure Haiqu SDK

Pass your token into the run options as iqm_token:
Alternatively, save it once and the SDK will inject it automatically on subsequent runs:
The Resonance server URL defaults to https://resonance.iqm.tech and does not need to be set. To target a different endpoint, pass iqm_server_url in options (or use haiqu.save_iqm_credentials(token, server_url)).
3

Submit Quantum Jobs

IQM devices follow the id convention iqm_<name> (e.g. iqm_garnet, iqm_emerald, iqm_sirius).
Check which IQM devices are available in your environment by calling haiqu.list_devices() first — the list is discovered dynamically from Resonance.
The same credentials and device ids work for hybrid programs submitted with haiqu.flow(...).
4

Monitor and Retrieve Results

Track a job’s status and retrieve results within the SDK:

​
Using the IQM mock simulators

Each Resonance device exposes an ideal, noiseless mock variant under the id <device>:mock — for example iqm_garnet:mock. A mock device runs a server-side simulator that uses the real device’s topology and native gate set, so it’s the fastest way to validate an end-to-end run before submitting to hardware. Mock devices consume no QPU time.
Mock devices are authenticated with your iqm_token just like the physical QPUs — the token is required for any iqm_* device.

​
Conclusion

The IQM Resonance integration brings IQM’s superconducting quantum hardware into the Haiqu SDK with a single credential and the familiar haiqu.run / haiqu.flow workflow. Whether you are validating a circuit on a mock device or running on Garnet, Emerald, or Sirius, the SDK handles transpilation to IQM’s native gate set, submission, and result retrieval for you — so you can focus on your quantum application.