skip to content
Ivan's wiki
Site Tools
Search
Tools
Show pagesource
Backlinks
Recent Changes
Media Manager
Sitemap
>
Recent Changes
Media Manager
Sitemap
qiskit-backends
This page is read only. You can view the source, but not change it.
# Backends **Backends** are the execution targets for [quantum circuits](/qiskit-quantum-circuits). A backend can be a classical [simulator](/qiskit-simulators) or a real quantum processor. Qiskit abstracts the details: you design once, then run on different backends without changing code. Each backend has constraints: a gate set (which gates it natively supports), qubit connectivity (which pairs can interact), and error rates. [Transpilation](/qiskit-transpilation) adapts your circuit to meet these constraints. ## Backend selection Qiskit provides several built-in backends: - **AerSimulator**: fast classical simulator, supports arbitrary gate sets, perfect fidelity - **QasmSimulator**: OpenQASM 2.0 simulator - **StatevectorSimulator**: tracks the full quantum state (for small circuits) - **IBM backends**: real quantum processors via IBM Quantum Platform ```python from qiskit_aer import AerSimulator, QasmSimulator from qiskit_ibm_runtime import QiskitRuntimeService # Local simulators sim = AerSimulator() result = sim.run(qc, shots=1000).result() # IBM quantum hardware (requires account and token) service = QiskitRuntimeService() backend = service.backend('ibmq_qx5') job = backend.run(qc, shots=1000) result = job.result() ``` ## Backend properties Query a backend's properties: qubit count, gate times, error rates, connectivity: ```python backend = AerSimulator() print(backend.num_qubits) print(backend.configuration().basis_gates) ``` Different backends have different performance characteristics. Simulators are perfect but slow for large circuits; real hardware is noisy but available now.
Page Tools
Show pagesource
Backlinks
Back to top