AQT
Run on Alpine Quantum Technologies' IBEX Q1 trapped-ion QPU through qBraid, with only a qBraid API key.
Using your own AQT arnica account? See AQT (self-managed).
Devices on qBraid
Alpine Quantum Technologies (AQT)’ IBEX Q1 is a 12-qubit trapped-ion QPU with all-to-all connectivity. It is on qBraid through two submission paths. Each path has its own device ID and billing.
| Device ID | Path |
|---|---|
openquantum:aqt:qpu:ibex-q1 | Open Quantum |
aws:aqt:qpu:ibex-q1 | Amazon Braket |
Check each device’s status and price in the device catalog before you submit. Not every path is online at once.
Quick start
from qbraid.runtime import QbraidProvider
provider = QbraidProvider()
device = provider.get_device("aws:aqt:qpu:ibex-q1")
bell = """
OPENQASM 3.0;
include "stdgates.inc";
qubit[2] q;
bit[2] c;
h q[0];
cx q[0], q[1];
c = measure q;
"""
job = device.run(bell, shots=100)
print(job.result().data.get_counts())Programs can be written in any framework qBraid supports.
Through Amazon Braket
aws:aqt: devices go through Amazon Braket, billed in qBraid credits. Any two qubits can interact, so there is no coupling map to route around: Calibrations returns an empty edge list for IBEX Q1. These devices take Braket runtime options, and Amazon Braket covers what every Braket device has in common, including how counts are ordered.
Through Open Quantum
openquantum:aqt: devices go through Open Quantum and spend credits from an Open Quantum account linked to qBraid, not qBraid credits. Link the account first, then submit as usual:
device = provider.get_device("openquantum:aqt:qpu:ibex-q1")
job = device.run(bell, shots=100)See Open Quantum for linking an account and what these devices accept.
Related links
- Run on qBraid: installing the SDK and saving your qBraid API key
- Batch & group jobs: running several circuits as separate, batch, or group jobs
- Amazon Braket: how
aws:*devices compile and order bits - AQT (self-managed):
AQTProviderwith your own arnica account - AQT
Thanks for your feedback.

