Overview

Know what hardware you need before you ask for it.

Quantum hardware time is scarce and expensive. Scheduling a circuit that exceeds the available qubit count, or that requires more gate layers than the device's coherence time allows, wastes that time — and may produce results too corrupted to use. The physical resource estimator runs these feasibility checks before any hardware commitment.

Given a circuit and its error correction allocation, the estimator calculates how many physical qubits are needed to support the required logical qubits at the target fidelity, how many gate layers the compiled circuit will require, how many ancilla and magic-state qubits the error correction overhead demands, and whether those totals fit within a specified hardware capacity. The estimator is aware of the φCoherent error-correction code structure and uses it to produce accurate overhead forecasts rather than worst-case bounds.

/ Capabilities

What it provides.

Physical qubit count estimation, gate depth projection, magic state factory sizing, and a hardware feasibility check give a complete pre-flight picture before any hardware time is reserved.

  • / 01

    Physical qubit count estimation

    Calculates how many physical qubits are needed to encode the required logical qubits at the target error rate, accounting for the specific QEC code in use. The result reflects actual φCoherent code overhead, not a generic worst-case assumption.

  • / 02

    Gate layer depth projection

    Forecasts the total circuit depth after transpilation and error correction overhead, checking against hardware coherence time limits. Depth projections account for parallelization opportunities identified during transpilation.

  • / 03

    Magic state factory sizing

    Estimates the ancilla qubits and factory overhead required to supply the T-state gates needed by the circuit. Magic state distillation is often the dominant qubit cost in fault-tolerant circuits; the estimator surfaces this early.

  • / 04

    Hardware feasibility check

    Compares all estimated requirements against a provided hardware capacity specification and returns a pass or fail with actionable detail on which constraints are binding — qubit count, depth limit, or connectivity — so the team knows exactly what to address.

In the stack

Pre-flight planning layer — run before scheduling hardware time. The error budget allocator's output feeds directly into the estimator. Both feed into the unified budget pipeline, which combines them in a single end-to-end pass. Use the estimator whenever a circuit's hardware requirements are unknown or a new hardware platform is being evaluated.

Related packages
Licensing

Open under AGPLv3.

Published under the GNU AGPLv3 with whitepaper and reference implementation. Commercial licensing is available for closed-source deployments.

← Quantum Stack Commercial License