private credentials
Provider connections
Saved keys and provider schemas live behind authenticated account settings.
Skip to content
Full matrix 
Flowintent / proof
Integrations
Provider routing for the 2026 quantum stack.
QFlow makes integrations operational: encrypted provider credentials, device discovery, preflight context, simulator routes, submit-capable beta paths, hardware polling, run history, and reviewer-safe evidence stay around one workflow record.
adapter audit 2026-06-03
Submit where implemented. Plan where specialized.
Provider logos are context. The useful part is status, route mode, limits, and evidence ownership.
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
Credential boundary
Provider tokens stay encrypted and private.
Device discovery
Targets and backend context become route inputs.
Preflight decision
Unsupported routes fail before a costly submit.
Run and poll
Simulator or beta adapter state stays with the workflow.
Evidence packet
Counts, source, trace, CSV, and reviewer notes are shareable.
Ecosystem context
The logo layer stays quiet. The route layer stays explicit.
QFlow references provider and SDK ecosystems independently. It does not imply affiliation, certification, endorsement, or guaranteed account access.
Qiskit
IBM Quantum
AWS Braket
Azure Quantum
IonQ
Rigetti
Google Quantum AI
Quantinuum
OpenQASM
NVIDIA CUDA-Q
workflow context
Route selection
The canvas keeps provider and device choice attached to generated source and run state.
evidence trail
Run history
Completed, failed, and hardware-bound runs are reviewable without exposing private tokens.
Live simulator
Qiskit Aer, Cirq, and OpenQASM paths run public samples without provider credentials.
Submit-capable beta
Implemented adapters can submit, poll, and map results where the provider account has access.
Validation-only
Some adapters check credentials, targets, workspace context, or estimator fit before direct submit exists.
Specialized roadmap
Analog and annealing workflows stay planned until they have their own model instead of a forced gate path.
Provider status preview
Public matrix before private credentials.
The public matrix is a product-status explanation, not a live provider account check. It shows the adapter layer while private token tests stay inside authenticated provider surfaces.
IBM Quantum
Submit-capable betaHardware and simulator
Authenticated 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 betaOpenQASM task path
Device 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 contextIonQ
Submit-capable betaHardware and simulator
Credential 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 contextQuantinuum
Submit-capable betaHardware and emulator
Nexus credential flow, device discovery, submit, polling, and result mapping.
Backend access, project permissions, and provider-side payload constraints apply.
Source contextAzure Quantum
Validation and estimator contextTarget list, workspace preflight
Credential 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 contextD-Wave
Credential/device testAnnealing and hybrid solvers
Credential validation and solver/device catalog context.
QFlow does not submit gate-circuit jobs to D-Wave; annealing workflows need a separate Ocean-style model.
Source contextCloud provider context
AWS, Azure, IBM, IonQ, Rigetti, Quantinuum, and OQC paths stay visible with their own access limits.
Analog and annealing boundary
D-Wave, QuEra, and Pasqal are represented as specialized paths instead of mislabeled gate-circuit submit.
Evidence survives handoff
Counts, source, trace, route notes, and CSV exports stay with the run history.
Private data stays private
Provider tokens, billing state, admin notes, and raw credentials stay out of public proof.
No 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.