Hardware
Run on a real quantum computer
This leaves the simulator behind. Your circuit is transpiled into a device's native gate set and executed on physical qubits — superconducting transmon circuits or trapped ions — with a shared queue in front of it and real noise inside it. The results will not be as clean as Aer's, and that is the entire point.
1 · Circuit
OPENQASM 3.0; include "stdgates.inc"; qubit[2] q; bit[2] c; h q[0]; cx q[0], q[1]; c = measure q;
2 · Device
3 · Shots and cost
Pick a device to price 1,024 shots.
4 · What to measure
By default the device returns a histogram of bitstrings — the sampler. Add an observable instead and it measures ⟨ψ|H|ψ⟩ for each one, which is what VQE, QAOA and most of quantum chemistry actually need.
Observables
samplerAdding an observable switches this submission from the sampler, which returns a bitstring histogram, to the Estimator, which returns <psi|H|psi> for each one. Leave the list empty to sample instead. Each Pauli string needs one letter per qubit, and qubit 0 is the rightmost character — Qiskit's ordering, so IZ is Z on qubit 0.
Start from
A preset replaces the whole list. Hover or focus one for what it measures.
No observables. This job will sample and return a histogram.
These checks are a local copy of the server's, not the server's. A clean editor means nothing failed the rules we know about here; the API re-runs all of them against the parsed circuit and has the final say.
5 · Submit
Your hardware runs
Loading your runs…
Compare two runs
Loading your runs…
One last thing before you spend anything: a local simulation is instant, free and exact. If you want to know what a Bell state's distribution looks like, Aer will tell you in milliseconds. Come here when the question is specifically about the machine — how much decoherence eats your fidelity, what a native gate set does to your depth, how long a real queue actually is. Reproducing textbook results on a QPU costs money and teaches you nothing the simulator would not have.