One platform, your choice of engine
Run on any engine from any of your favorite frameworks. Pick whichever engine best matches your workflow.
Quantum Rings Simulator
by Quantum RingsQuantum Rings' simulator for large circuits, up to 128 qubits, with adjustable precision and speed-versus-accuracy settings.
Qiskit
by IBMIBM's high-performance simulator for the Qiskit ecosystem, with fast, exact state-vector simulation plus density matrix, stabilizer, and MPS methods.
PennyLane
by XanaduXanadu's high-performance C++ state-vector simulator for the PennyLane ecosystem, plus PennyLane's mixed-state and Clifford devices.
Cirq
by GoogleGoogle's qsim state-vector simulator for the Cirq ecosystem, plus a quimb-based matrix product state engine for larger circuits.
Which simulator should I use?
State-vector simulation tracks every amplitude, so the simulated state is exact. The trade-off is memory, which doubles with every qubit, so state-vector runs here stay under 30 qubits. PennyLane Lightning, Google's qsim, and Qiskit Aer all work this way.
Matrix product state (MPS) engines compress the quantum state instead of storing every amplitude, so they reach far larger circuits when entanglement stays modest. Quantum Rings and Cirq's MPS engine take this approach.
Qiskit Aer, PennyLane Lightning, Google's qsim, and the Quantum Rings simulator are the standard simulators from their respective ecosystems.
Prototype here, prove it on real QPUs
Execute circuits on leading quantum simulators. Circuits you run here can then go to real QPUs from IonQ, Rigetti, IQM, and AQT through the same API, with $50 of free quantum compute to start.
Missing an engine you rely on? Request a simulator and we will look into it.