What state this is in, and what happens to what you type
KetQat Intelligence is in beta. That word on its own tells you nothing you had not guessed, so this page says the two things it usually stands in for: which parts you can rely on, and what happens to the circuits and figures you enter.
Read this before you rely on a number
Estimates here are modelled, from published expressions with their sources stated. They are not measurements of any device, and no figure on this site is a forecast. Where the evidence does not support an answer, the product refuses to give one — that refusal is the finding, not a gap.
Supported
These work now, and a change that broke one would be treated as breaking rather than shipped quietly.
- Resource estimation from a workload description
- Logical qubits, code distance, physical footprint, distillation cost and runtime, from the expressions set out in the methodology with their sources.
- Scenario comparison
- Several assumption sets side by side, each with its own threshold conditions.
- Decision reports as numbered revisions
- A report is generated from the inputs as they stand and saved. Later edits do not alter it.
- Review by somebody who did not request it
- Including the refusal path, and an attestation that stops applying when the inputs change.
- Reference assessments, including a refusal
- Worked examples with their arithmetic shown, one of which the tool declines to assess.
Not supported, and not planned
Absent by decision rather than by backlog. If your question is one of these, this product will not answer it later either — which is worth knowing before you invest an afternoon.
- Any date
- No projection of when hardware will run a workload. Vendor targets are compared on stated figures only, and no curve is fitted through announced milestones.
- Any price, or cost per run
- No vendor pricing is aggregated. A cost figure with an unknown input is not a cost figure.
- Vendor rankings
- Devices are not scored against each other. Incompatible workloads are never ranked together.
- Execution on real quantum hardware
- Simulation only, in a separate sandboxed plane. Every result carries its execution class; a simulated result is never presented as hardware.
- An estimate the platform vouches for by itself
- A reproducibility hash shows the bytes are unchanged. It is not verification, and no badge is awarded automatically — attestation needs a named person.
The full list, with where each refusal is enforced in code, is on what it will not tell you.
May change
- Scenario presets and their default assumptions, as sources are added or corrected.
- The shape of the REST API and the typed client. The SDK is at 0.3.0 and does not yet promise a stable API.
- Page structure and URLs outside the evidence pages, which are kept stable because reports cite them.
A saved report is not on this list. Reports are numbered revisions and are never rewritten, so a version you circulated stays readable exactly as circulated even after the assumptions behind it move.
What happens to what you type
Assessments and drafts are private by default, visible to you and to members of a project you put them in. A draft is never estimated until you submit it.
Nothing you enter is sent to a third party. There is no analytics tag, no session recorder and no advertising pixel on this site.
Usage measurement records stage counts only — that somebody reached the estimate step, not who, and not what they were estimating. No circuit, baseline, name, email or content of any kind is included. The recorder takes a single stage name as its only argument, so there is nowhere for anything else to be attached without changing that function.
Provider credentials are never stored. They are supplied per job and held only in the isolated execution plane, which is a separate sandbox — nothing you upload runs in the web application.
The authoritative statement, including retention and how to have data removed, is on privacy.
Telling us something is wrong
Two routes, and they are different on purpose. Neither asks for your name, your email or your employer.
Public — a GitHub issue
A wrong figure, a broken page, a source that does not say what we claim it says. Public, so the correction is auditable by whoever read the wrong version.
Earlier assisted-study concept
Assisted studies are not offered. Do not put confidential work in public issues. The retained page explains the current scope and free local alternative.