Backends & Targets¶
Open Quantum exposes its QPUs to qBraid as devices. This page covers how to discover and target them.
Backend IDs¶
qBraid device ids are hierarchical, colon-separated strings of the form provider:vendor:type:device. Open Quantum devices use the openquantum provider. For example, to target IQM Garnet:
The following Open Quantum backends are available through qBraid:
| QPU | Technology | Qubits | qBraid device id |
|---|---|---|---|
| IonQ Forte 1 | Trapped ion | 36 | openquantum:ionq:qpu:forte-1 |
| IonQ Forte Enterprise 1 | Trapped ion | 36 | openquantum:ionq:qpu:forte-enterprise |
| Rigetti Cepheus-1-108Q | Superconducting | 108 | openquantum:rigetti:qpu:cepheus-1-108q |
| IQM Emerald | Superconducting | 54 | openquantum:iqm:qpu:emerald |
| IQM Garnet | Superconducting | 20 | openquantum:iqm:qpu:garnet |
| AQT IBEX Q1 | Trapped ion | 12 | openquantum:aqt:qpu:ibex-q1 |
Listing Devices¶
From the qBraid SDK¶
Use QbraidProvider to enumerate the devices available to your linked account:
from qbraid.runtime import QbraidProvider
provider = QbraidProvider(api_key="YOUR_QBRAID_API_KEY")
# All devices visible to your account
for device in provider.get_devices():
print(device.id)
# Fetch a specific Open Quantum backend
device = provider.get_device("openquantum:iqm:qpu:garnet")
From the qBraid Website¶
Open Quantum backends appear under Devices in the qBraid dashboard once your accounts are linked. You can also browse status and metadata.
Supported Operations¶
You can write circuits in any framework qBraid supports (Qiskit, Cirq, Braket, OpenQASM, and more). qBraid transpiles your program and Open Quantum applies backend-specific transformations before execution, so standard gate sets work without manual decomposition.
Native gate sets, qubit connectivity, and features such as mid-circuit measurement vary by QPU. Transpilation maps your circuit onto the target, but operations a device cannot support will be rejected.
Note
Every run requires a finite shots value. Analytic/statevector mode is not available on hardware.
Next Steps¶
- Examples -- complete, runnable examples.