Quantum Computer Rental Performance Comparison

Summarize this article with:
Has anyone compared the different current rentable quantum computers performance? Sorry for the poorly written question. The QC industry is still in its early stages where defining "performance" is actually quite difficult. The various machines available for public use work in different ways that perform very differently on different workloads. It's like evaluating the difference between a Ferrari and a minivan. Do you want to measure on acceleration or cargo capacity? As the industry matures, it's likely that analysts will identify important workloads and use them as benchmarks, but given that we still only have a fuzzy understanding of what QC workloads are practical or valuable, it will take time to reach that level of maturity. What are the publicly available rental options? I thought most usable machines were in captive labs All of the major cloud providers (AWS Braket, Azure Quantum, and to a lesser extent GCP) provide a software interface to run workloads on the machines in captive labs. It's not always cheap and it's not always fast, because they're basically queuing workloads onto these very throughput-limited machines like the old days of mainframes. But it's pretty easy. IBM also provides access but I think only to specially selected partners. They give the public access to simulators, though. IBM has real 100Q+ systems that anybody can use for free, 10 min a month IBM is the most heavily used provider by the public today (by far) for access to the real hardware. While these cloud providers do provide interface for access, it is not to their own machines. They just play broker for others (ionQ, riggetti, pascal etc.) Amazon Braket • Pricing model • $0.30 per task • Per-shot pricing varies by QPU • ~$0.0009 (Rigetti) → ~$0.08 (IonQ Forte) • Optional dedicated reservations: ~$2.5k–$7k per hour • What this means • Most transparent pricing in the market • Easy to cap spend and reason about cost • Good for benchmarking, experiments, controlled pilots • Gotcha: Shot-heavy workloads scale cost fast Microsoft Azure Quantum (IonQ backends) • Pricing model • Per gate-shot (1Q + 2Q gates) • Minimum cost per execution • ~$12–$170 per run depending on device and error mitigation • What this means • Minimum charges dominate cost • Many small jobs are expensive unless batched • Gotcha • Easy to blow budget accidentally without strict batching discipline Microsoft Azure Quantum (Quantinuum backends) • Pricing model • Monthly subscription using credits (HQCs / eHQCs) • ~$125k–$175k per month list price • What this means • Predictable budgeting • Enterprise / institutional research focus • Gotcha • Not startup-friendly pricing • Overkill unless you have steady throughput Microsoft Azure Quantum (Rigetti backends) • Pricing model • ~$0.02 per 10 ms of execution time • What this means • Time-based billing favors shallow circuits • Cost depends on circuit depth and queue behavior • Gotcha • Less intuitive than per-shot pricing IBM Quantum • Pricing model • Pay-per-minute of QPU time • ~$96/min PAYG • ~$48–$72/min prepaid tiers • What this means • You pay for wall-clock quantum time, not shots • Encourages tight runtime limits and short circuits • Gotcha • Long jobs or retries get expensive fast D-Wave Leap • Pricing model • Hybrid solver usage (not cleanly itemized publicly) • Typical pilots reported at ~$5k–$30k • What this means • Cheapest in practice for optimization-style workloads • Most compute is classical, quantum used sparingly • Gotcha • Only fits QUBO / Ising / CQM-style problems IonQ (direct access) • Pricing model • Resource-estimator based, quote-driven • What this means • Similar economics to AWS/Azure IonQ paths • Less transparent unless you’re a large customer • Gotcha • No simple public price sheet Google Quantum Computing Service • Pricing model • No public commercial pricing • What this means • Restricted-access, research-focused • Gotcha • Not a general-purpose QCaaS option today TL;DR • Per-shot pricing = easiest to reason about • Per-execution minimums = silent budget killer • Per-minute pricing = optimize for shallow circuits • Enterprise subscriptions start at six figures • None of these are cheaper than classical for real workloads today Create your account and connect with a world of communities.
