Frequently asked questions
Direct answers to common questions about Qsolve: cost, failed runs, quantum hardware, accuracy against classical methods, privacy, reproducibility and limits.
Updated 12 November 2026 View as markdown
Getting started
Do I need to know quantum computing?
No. You describe your problem in the workflow's input form and read the result in domain terms, such as which assets to hold or which solvent binds lithium most strongly. You do need to read a comparison with a classical baseline, which the run page explains in words. See Reading your results.
Can I buy more credits?
Not in the web app. See Credits and pricing.
Results
Is the quantum answer better than the classical one?
Not by default. On some cases it matches the classical answer and on others it falls below it, and the track record shows which. A quantum result can at best equal an exact baseline. The value of Qsolve is that you see this and can decide whether the quantum method is worth using.
Why does my result say "x% from the classical answer"?
The quantum method found a worse answer than the baseline. On a simulator that reflects the algorithm and its settings. On a quantum computer it also reflects hardware noise, which is why the workflow page shows hardware results separately. See Accuracy, fidelity and noise.
Why is the fidelity low when the answer is correct?
Fidelity measures how close the whole output distribution is to the ideal one, and noise spreads probability across wrong outcomes. A sampling workflow only needs the best outcome it saw, and that can still be the right one. See Accuracy, fidelity and noise.
What is the difference between "measured" and "reported"?
Measured numbers are computed by Qsolve from what actually went to the machine: circuits, shots, depth, raw fidelity and the accuracy against the baseline. Reported numbers are the workflow's own claims, such as its mitigated fidelity, and are labelled as such.
Is the track record based on my data?
No. It comes from fixed benchmark inputs, so it shows how the workflow behaves on problems like those, not on yours. Run a representative input of your own on a simulator before relying on it.
Why did two runs of the same input differ?
On a simulator, the same workflow version, input and settings give the same result hash. The web form runs the latest published version with the default seed, so a difference usually means the workflow was updated or a setting differs. On a quantum computer, results vary because the hardware is noisy and drifts. See Reproducibility.
Cost and credits
How much does a run cost?
The workflow page shows a typical cost and each run shows an exact quote before anything is charged. A small run on the CPU simulator costs a few hundredths of a credit. A quantum computer run is priced by quantum seconds and costs far more. See Credits and pricing.
Am I charged for a failed run?
Only for work that ran. A run that fails before it starts costs nothing. A run that fails after using machine time is billed for what it used, never more than the hold.
Machines
Can I run on a real quantum computer?
If the workflow supports it and the machine is open, yes. Where to run offers an IBM quantum computer with a choice of device, priced by quantum seconds. It may not be open to every account yet. The Compute page shows availability. See Machines and targets.
How long will my run take?
Once the run is sized, the run page shows "Runs like this take about N min", based on the workflow's own prediction. Waiting for a free machine, or in a quantum computer's queue, comes on top. A run predicted to exceed the workflow's time limit is rejected before it starts.
Privacy and records
Who can see my runs and inputs?
The members of your account, and nobody else. The exception is the platform's own benchmark runs, which every signed-in user can read. The workflow's author does not receive your input, and the workflow's code cannot send it out. See Data and privacy.
How long are my runs kept?
Progress events for 30 days. A run's input, settings and result are cleared 90 days after it finishes, while its status, cost and receipt remain. Download a run with Report if you need it longer.
Publishing
Can I run an older version of a workflow?
No. The web form always runs the latest published version. See Reproducibility.
How do I publish my own workflow?
Write it in Qiskit with the Qsolve SDK, test it locally, and submit its repository for validation. See Build overview and Validation and publishing.