Quantum Cost Calculators

Quantum computing billing is complex. Each platform uses a different pricing model — from simple per-shot pricing to exotic unit systems like AQT and HQC. These calculators help you estimate costs before submitting jobs.

Universal Circuit Cost Calculator

Most popular

Enter your circuit parameters — qubit count, circuit depth, 1Q and 2Q gate counts, measurements, and shot count — and instantly estimate the cost across every compatible QPU and cloud platform. Supports per-shot, per-second, AQT, and HQC pricing models.

What's included
  • Covers all 10 cloud platforms
  • All pricing models (per-shot, AQT, HQC, per-second)
  • Error mitigation cost breakdown
  • Side-by-side platform comparison
  • Cost-per-useful-circuit estimate

IonQ AQT Calculator

IonQ

Calculate the exact cost for jobs on IonQ QPUs using the Algorithmic Qubit Token (AQT) pricing model. Input your circuit's two-qubit and one-qubit gate counts with shot count to see costs across IonQ Cloud, Amazon Braket, Azure Quantum, and qBraid.

What's included
  • AQT formula: shots × (n_2q + 0.1 × n_1q)
  • All IonQ QPUs: Aria 1, Forte 1, Forte Enterprise
  • Cross-platform price comparison
  • Minimum cost per job calculation
  • Cost optimization tips

Quantinuum HQC Calculator

Quantinuum

Compute costs for Quantinuum H1-1 and H2-1 jobs using the Hardware Quantum Credit (HQC) model. The HQC formula accounts for circuit complexity: single-qubit gates, two-qubit gates, measurements, and shot count. Compare Azure Quantum vs Strangeworks pricing.

What's included
  • HQC formula: (n_1q + 10×n_2q + 5×n_meas) × shots
  • H1-1 ($120/HQC) and H2-1 ($275/HQC) pricing
  • Azure Quantum vs Strangeworks comparison
  • Emulator vs QPU cost breakdown
  • Batch optimization recommendations

Amazon Braket Cost Calculator

AWS

Estimate costs for quantum jobs on Amazon Braket across all supported QPUs: IonQ Forte, IonQ Aria, Rigetti Ankaa-3, IQM Garnet, AQT PINE, QuEra Aquila, and D-Wave Advantage. Covers per-shot and per-task pricing with the $0.30 task fee.

What's included
  • All Braket QPUs in one calculator
  • Per-shot pricing + task fee breakdown
  • AWS region availability
  • Free simulator vs paid QPU comparison
  • Monthly cost projection

Quantum Pricing Model Primer

Understanding how quantum cloud providers charge is essential for cost control. Here are the four main billing approaches:

Per Shot

total = price_per_shot × shots + task_fee

Example: Rigetti Ankaa-3 on Braket: $0.00090/shot × 1,000 + $0.30 = $1.20

Amazon BraketRigetti QCSAzure Quantum

Per Second

total = price_per_second × execution_time_seconds

Example: IBM Heron r2: $1.60/sec × 10 sec = $16.00

IBM Quantum

AQT (IonQ)

AQT = shots × (n_2q + 0.1 × n_1q)
total = $0.00097 × AQT

Example: 1,000 shots, 20 two-qubit gates → AQT = 20,000 → cost = $19.40

IonQ CloudAzure QuantumqBraid

HQC (Quantinuum)

HQC = (n_1q + 10 × n_2q + 5 × n_meas) × shots
total = price_per_hqc × HQC

Example: H2-1: 10 2Q gates, 5 1Q gates, 5 meas, 100 shots → HQC = 1,600 → $440

Azure QuantumStrangeworksqBraid

Cost Optimization Tips

1
Maximize shots per job

For per-shot pricing, the task fee ($0.30) is fixed. Running 10,000 shots spreads this fee over more executions, reducing cost per shot.

2
Minimize two-qubit gates

For AQT/HQC pricing, 2Q gates are 10× more expensive than 1Q gates. Use transpiler optimization to reduce CNOT/CZ gate count before submission.

3
Use emulators first

Quantinuum H2-1 emulator costs $5.50/HQC vs $275/HQC for the real QPU — 50× cheaper. Validate circuit logic before running on hardware.

4
Compare platforms

The same QPU can cost differently on different platforms. Rigetti Ankaa-3 is cheapest on Rigetti QCS ($0.00075/shot) vs Amazon Braket ($0.00090/shot).

5
Leverage free tiers

IBM Quantum offers free access to Eagle QPUs. Azure Quantum gives $500 credits for new accounts. qBraid gives 300 credits on signup. Start free.

6
Match QPU to task

Optimization problems with 1,000+ variables are cheaper on D-Wave annealing ($2,000/min but problems solve in microseconds). Don't use gate QPUs for pure optimization.