Loading docs
Understand submit-capable, validation-only, simulator, and planned quantum provider adapter boundaries in QFlow Studio.
Provider adapters should be described by what they can do today: submit, validate credentials, list devices, estimate resources, or provide only ecosystem context.
Use the public integration status page before assuming that every provider logo means direct hardware submission.
Section 01
Live simulator means the local runner path is product-ready. Submit-capable beta means an adapter can submit and poll when private credentials and provider access are valid. Validation-only means QFlow can check credentials, targets, or workspace context but does not submit jobs directly. Planned means the direct path is intentionally not implemented yet.
These labels are public product status, not a live account health check.
Section 02
Provider names are used for independent ecosystem and routing context. Do not imply affiliation, certification, endorsement, or replacement unless a page states it explicitly.
If a provider path is analog, annealing, restricted, or requires a different SDK model, say that directly in status copy.