Quickstart

In five minutes you can create an account, run the max-cut workflow's example graph on the CPU simulator, and read the comparison with the classical baseline. The run costs a small fraction of one credit, and every new account starts with 100.

1. Create an account

On the sign-in page choose Create your account. Sign up with an email and a password (at least 8 characters), continue with GitHub, or use Email me a sign-in link to skip the password.

Qsolve sends a confirmation email, and your 100 free credits arrive when you confirm it. Each person gets one grant: variants of one Gmail address (dots, +tags) count as the same address. Your balance shows at the top of the page and on Usage.

2. Pick a workflow

Open Run an experiment. Each workflow has a row of small coloured squares, one per benchmark case: green means the case matched the best classical answer, amber means it came out below it, red means it failed.

Search for "graph" or choose the max-cut card. It splits a weighted graph into two groups so the total weight of edges between them is as large as possible.

3. Set up the run

The form is pre-filled with the first example, a 6-node graph. The chips under Start from load other examples and Blank clears the form. To edit raw JSON, switch Edit as to JSON:

{
  "nodes": ["a", "b", "c", "d", "e", "f"],
  "edges": [["a","b"], ["b","c"], ["c","d"], ["d","e"], ["e","f"], ["f","a"], ["a","d", 2]]
}

Under Where to run, leave CPU simulator selected. It is exact, noiseless and the cheapest. See Machines and targets for the others.

In the Run summary box, the Spend limit is the most you are willing to pay. Leave the suggested value. You see the exact quote before anything is charged.

4. Run it

Press Run. The run page moves through Sizing, Queued and Running to Done, usually within seconds, with no refresh needed.

5. Read the result

From the top, the run page shows:

• Answer: a one-sentence summary, then the answer itself (here, which nodes go in which group and the cut weight).
• Quantum vs classical: a verdict such as "Matched the classical answer", "x% better than classical" or "x% from the classical answer", with both values side by side and the name of the classical method.
• Circuits: every distinct circuit the run sent, with qubits, depth and gate counts.
• How the solver got there: the solver's own settings and numbers.
• Cost, in the side column: credits charged and how the hold was released.

Reading your results goes through each part, and Choosing a workflow explains the track record on the workflow page. The Receipt card shows the workflow version, the code commit, and hashes of the input and the result.

Next

Accuracy, fidelity and noise explains the numbers. Credits and pricing shows what runs cost on other machines. The FAQ covers common messages.