Loading docs
API & Evidence
Provider Adapters
Understand submit-capable, validation-only, simulator, and planned quantum provider adapter boundaries in QFlow Studio.
Updated June 3, 2026QFlow StudioNormal userTeacher
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.
Purpose
Understand submit-capable, validation-only, simulator, and planned quantum provider adapter boundaries in QFlow Studio.
Where it fits
This page belongs to the API & Evidence section and should be read with the related pages listed at the end.
Review boundary
Use screenshots and notes to explain product behavior without exposing private credentials, admin state, or customer data.
Status labels
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.
live simulator
submit-capable beta
validation-only
planned
unsupported direct submit
No overclaiming
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.
source-backed
no affiliation claim
limits explicit
private credentials sealed
Next pages
Providers
Select quantum providers, inspect hardware fit, and keep credentials private while routing workflows.
Runs API
Understand the public product contract for creating, tracking, exporting, and reviewing quantum workflow runs.
Security model
Understand provider credential boundaries, reviewer-safe shares, role isolation, and safe documentation capture.