Live simulator
Local Qiskit Aer, Cirq, and OpenQASM paths support public sample workflows without provider credentials.
Integrations
Route quantum work with adapter status your team can trust.
QFlow already combines encrypted provider credentials, device discovery, preflight context, simulator routes, submit-capable beta adapters, hardware polling, run history, and evidence around the same workflow record.
status is explicit
Submit where implemented. Plan where specialized.
Provider logos are not enough; each row names the working adapter path, account limits, and roadmap scope.
1
Live simulator
6
Submit-capable beta
1
Validation and estimator context
1
Access and device preflight
1
Credential/device test
1
Planned direct path
1
Planned analog path
Submit-capable beta
Implemented submit, poll, and result paths exist for supported adapters; provider access, backend limits, and quotas still apply.
Validation-only
Some providers expose credential checks, target catalogs, or estimator context without direct hardware submission.
Specialized roadmap paths
Analog, annealing, or restricted hardware paths are represented honestly and planned with their own models instead of being forced into gate-circuit submit.
Provider status preview
Public matrix before private credentials.
The public matrix is a product-status explanation, not a live provider account check. It should show the strength of the adapter layer while keeping private token tests inside authenticated provider surfaces.
QFlow local runner
Live simulatorCircuit JSON and OpenQASM runs, counts, probabilities, and <=8-qubit Qiskit statevectors.
Default 24-qubit runner cap; raw Python source execution is off unless explicitly sandboxed.
Source contextIBM Quantum
Submit-capable betaAuthenticated job submit, job polling, backend listing, and result retrieval through the IBM adapter.
Requires IBM IAM access, service CRN, backend access, and provider-side job limits.
Source contextAWS Braket
Submit-capable betaDevice listing and OpenQASM task submission path with S3 result location when credentials are configured.
Hybrid Jobs are not the public QFlow submit path yet; direct tasks need AWS region, role, device ARN, and S3 bucket.
Source contextAzure Quantum
Validation and estimator contextCredential validation, workspace target discovery, and resource-estimator positioning.
Direct hardware job submission is intentionally disabled in the adapter until upload/SAS handling is implemented.
Source contextIonQ
Submit-capable betaCredential validation, backend listing, constrained circuit submission, polling, and result mapping.
Unsupported operations must be decomposed before submit; provider quotas and backend access still apply.
Source contextRigetti
Submit-capable betaCredential validation, device discovery, Quil-oriented submission, polling, and result mapping.
Only supported gate shapes can submit; unsupported workflow operations return explicit validation errors.
Source contextNo affiliation claim
Provider names are used for independent workflow context.
Use IBM, AWS, Azure, IonQ, Rigetti, Quantinuum, OQC, D-Wave, QuEra, Pasqal, Qiskit, CUDA-Q, and OpenQASM for their own deep execution layers.
Use QFlow when your team needs encrypted provider operations, route decisions, generated source, run state, polling, history, and evidence to survive review and handoff.