Quantum hardware drifts.We catch it before it burns your shots.
Every quantum backend drifts between calibration windows. It's physics, not failure. We observe it in real time across IBM, AWS Braket, Rigetti and Quantinuum — then score each run and return a signed record.
In plain English: quantum hardware is billed by the minute and calibration windows are hours, not days. We flag runs that fall outside the window before the result reaches your paper.
Dublin, Ireland · Stelor Evolution Ltd · IBM Quantum Ecosystem partner
qb-compiler
Apache 2.0 · PyPI
Our calibration-aware compiler is in the IBM Quantum Ecosystem under Error Mitigation + Circuit Optimization.
pip install qb-compiler · routes around bad qubits at submit time, not after the run.
THE PROBLEM
The pain is not “device down.” The pain is the device up, the shots running, and the number at the end quietly wrong.
Quantum hardware is billed by the minute and calibration windows are hours, not days. A run submitted outside the window produces shots whose energy can be off by 30 mHa — you find out when you write up the paper six weeks later. Every vendor publishes calibration data. Nobody cross-references it with your job queue in real time. That is the gap we fill.
Wasted shots
DriftRadar scores the backend before you submit.
Blind trust
Every result comes back with a signed passport.
No budget control
LiveGate aborts round-2 when the decoder goes bad.
WHY NOW
Three events in the last six months turned quantum from research into billed infrastructure.
NOV 2025
IBM Nighthawk ships, $96/min billing.
120 qubits on Utility tier. Quantum compute is now a line item on an enterprise invoice. Nobody is checking the answers.
FEB 2026
Software stack consolidates.
Classiq closes $110M Series C, Riverlane $75M. The compiler and decoder layers are claimed. The vendor-neutral trust layer across them is still open.
APR 2026
qb-compiler in IBM Quantum Ecosystem.
Our calibration-aware compiler is listed alongside the other algorithm vendors. Apache 2.0 telemetry surface, paid SDK on top. We are in the stack, not adjacent to it.
QUANTUM FLIGHT CONTROL
Nine products. One signed Result Passport at the end. Every number in the claims below is hardware, not Stim.
QPU HEALTH
If you run the platform
PROVENANCE & ENTROPY
If a regulator signs off your results
COMPUTE EFFICIENCY
If you write the circuits
SEE THE PASSPORT FOR YOURSELF
One JSON document per QPU run. Trust score, drift state, which gates fired, what the policy decided.
QUANTUM FLIGHT CONTROLEVERY RESULTHAS A PASSPORT.
The Quantum Result Passport, a signed, machine-readable record of provenance, confidence, policy, and trust for every quantum execution.
“Does this result have a passport?”
HOW IT WORKS
SUBMIT
Wrap your Qiskit job in our SDK. Pick the gates that matter for the workload.
GOVERN
Gates run in-line with the circuit. Doomed shots get aborted, bad decodes get dropped.
CERTIFY
Result comes back with a signed passport. Accept it, investigate it, or re-run on a cleaner backend.
Four SLA tiers (Bronze, Silver, Gold, Platinum) match the trust level your workload demands. See pricing →
FOR DEVELOPERS
RESULT PASSPORT API
from qubitboost_sdk import (
ResultPassport, WorkloadType, SLATier, PolicyConfig,
)
passport_engine = ResultPassport(
workload_type=WorkloadType.VQE,
policy_config=PolicyConfig(sla_tier=SLATier.GOLD),
)
passport = passport_engine.evaluate(
gate_results={
'driftradar': 0.91,
'livegate': 0.88,
'safetygate': 0.85,
},
job_id='vqe-h2o-fez-001',
)
print(passport.trust_score) # 0.874
print(passport.decision) # 'ACCEPT'CLI
$ pip install qb-compiler $ qbc preflight circuit.qasm -b ibm_fez $ qbc analyze circuit.qasm -b ibm_fez $ qbc compile circuit.qasm -b ibm_fez --receipt
WHERE WE SIT
We are not a decoder, not an SDK, not a control stack. We are the vendor-neutral trust layer across them.
| RIVERLANE | Q-CTRL | CLASSIQ | QUBITBOOST | |
|---|---|---|---|---|
| What they sell | Hardware decoder | Control + suppression | Software + compiler | Governance + trust |
| Model | FPGA integration | Vendor SDK | IDE | Vendor-neutral SaaS |
| Funding | $75M Series C | $113M total | $110M Series C | Bootstrapped |
201K SHOTS. FOUR VENDORS. EIGHT BACKENDS.
Every number on this page is a measurement on real silicon, drift-stratified, with the methodology file on record.
Five earlier claims were inflated. We retracted them publicly in Q1 2026. The discipline that made us retract is the discipline we sell.
IBM Fez
156-qubit Heron
Rigetti Ankaa-3
QEC at distance d=7
4 vendors, 8 backends
Cross-platform validation
IonQ Aria, Quantinuum H2
Trapped-ion, signed Result Passport
IBM Quantum
LIVERigetti
LIVEIonQ
LIVEIQM
LIVEACADEMIC ACCESS
Free for universities and research labs.
$500/month of real hardware time. All backends. Publish your results, cite us if the numbers helped, argue with us if they did not. See pricing.
REQUEST PILOT ACCESS
Two weeks on your workloads, your backends. Tell us which QPU and we will point the pilot at it. No commitment, no credit card, no deck.