Using Qsolve

Choose a workflow, run it, read the results and understand what it costs.

1. 1Choosing a workflowHow to find the right Qsolve workflow for your problem and judge it before you spend credits: search, track record, problem limits and the classical baseline.
2. 2Running an experimentHow to set up and launch a Qsolve run: enter your input, pick a machine, adjust solver settings, set a spend limit, then approve the quote, stop or rerun it.
3. 3Reading your resultsA guide to the Qsolve run page: the answer, the verdict against the classical baseline, fidelity and shots kept, circuits, cost, receipt and failed runs.
4. 4Accuracy, fidelity and noiseWhat Qsolve's accuracy, fidelity and shots-kept numbers mean, why correct hardware answers can have noisy distributions, and what is measured versus reported.
5. 5Machines and targetsThe three Qsolve targets (CPU simulator, GPU simulator, quantum computer), when to use each, what they cost, and how to read availability on the Compute page.
6. 6Credits and pricingHow Qsolve prices a run: the quote and hold formulas, how charges and returns are settled, spend limits and monthly budgets, with worked examples in credits.
7. 7Run recordsWhat Qsolve stores for every run, how to browse your run history, and how to read the evidence on a run page: receipt, circuits, events and credit movements.
8. 8ReproducibilityHow to reproduce a Qsolve run: the seed, workflow version and settings that fix a simulator result, what the receipt lets you compare, why hardware differs.
9. 9Data and privacyWhat data you give Qsolve when you run a workflow, what is stored and for how long, who can see it, and what a workflow's code can do with your input.
10. 10Qsolve for enterprisesHow an enterprise team can evaluate a Qsolve workflow, control spend with limits and budgets, audit runs, and what its results can and cannot be relied on for.