Integrations · implementation status

See what submits, what validates, and what stays planned.

The public matrix comes from the QFlow adapter implementation audit. It separates the local simulator, submit-capable beta paths, validation or preflight surfaces, and planned work without implying provider affiliation or account access.

Open the full matrix Integration overview

Adapter snapshot

Current route modes

Code audited

12 providers

ProviderStatusMode

QFlow local runnerLive simulatorQiskit Aer, Cirq, OpenQASM

IBM QuantumSubmit-capable betaHardware and simulator

AWS BraketSubmit-capable betaOpenQASM task path

Azure QuantumValidation and estimator contextTarget list, workspace preflight

IonQSubmit-capable betaHardware and simulator

RigettiSubmit-capable betaQPU route

Submit-capable means an adapter path exists. Account access, queue, quota, pricing, region, and provider-side features remain external constraints.

Implementation audit: June 3, 2026 · private credential tests require authentication

Provider status and requirements

Compare each route with its supported features and account requirements. These are implementation checks; live availability appears after connecting your account.

QFlow local runner

FastAPI runner

Live simulator

Mode: Qiskit Aer, Cirq, OpenQASM
Works now: Circuit JSON and OpenQASM runs, counts, probabilities, and <=8-qubit Qiskit statevectors.
Limits and requirements: Default 31-qubit runner cap; raw Python source execution is off unless explicitly sandboxed.

Code audit: 2026-06-03

Source context

IBM Quantum

Qiskit Runtime REST

Submit-capable beta

Mode: Hardware and simulator
Works now: Authenticated job submit, job polling, backend listing, and result retrieval through the IBM adapter.
Limits and requirements: Requires IBM IAM access, service CRN, backend access, and provider-side job limits.

Adapter audit: 2026-06-03

Source context

AWS Braket

AWS Braket API

Submit-capable beta

Mode: OpenQASM task path
Works now: Device listing and OpenQASM task submission path with S3 result location when credentials are configured.
Limits and requirements: Hybrid Jobs are not the public QFlow submit path yet; direct tasks need AWS region, role, device ARN, and S3 bucket.

Adapter audit: 2026-06-03

Source context

Azure Quantum

Azure Quantum REST/QDK context

Validation and estimator context

Mode: Target list, workspace preflight
Works now: Credential validation, workspace target discovery, and resource-estimator positioning.
Limits and requirements: Direct hardware job submission is intentionally disabled in the adapter until upload/SAS handling is implemented.

Adapter audit: 2026-06-03

Source context

IonQ

IonQ API

Submit-capable beta

Mode: Hardware and simulator
Works now: Credential validation, backend listing, constrained circuit submission, polling, and result mapping.
Limits and requirements: Unsupported operations must be decomposed before submit; provider quotas and backend access still apply.

Adapter audit: 2026-08-14

Source context

Rigetti

QCS / Quil

Submit-capable beta

Mode: QPU route
Works now: Credential validation, device discovery, Quil-oriented submission, polling, and result mapping.
Limits and requirements: Only supported gate shapes can submit; unsupported workflow operations return explicit validation errors.

Adapter audit: 2026-06-03

Source context

Google Quantum AI

Cirq / Quantum Engine context

Access and device preflight

Mode: Approved-group hardware access
Works now: Credential/project checks and access-oriented provider context.
Limits and requirements: Direct Cirq protobuf hardware submission is not implemented in QFlow; Google hardware access is restricted to approved groups.

Adapter audit: 2026-06-03

Source context

Quantinuum

Quantinuum Nexus

Submit-capable beta

Mode: Hardware and emulator
Works now: Nexus credential flow, device discovery, submit, polling, and result mapping.
Limits and requirements: Backend access, project permissions, and provider-side payload constraints apply.

Adapter audit: 2026-08-14

Source context

OQC

OQC Cloud API

Submit-capable beta

Mode: Cloud QPU task
Works now: Access setup, QPU discovery, cloud task submission, polling, and result mapping.
Limits and requirements: Requires OQC workspace access and supported circuit payloads.

Adapter audit: 2026-08-14

Source context

D-Wave

Leap / Ocean context

Credential/device test

Mode: Annealing and hybrid solvers
Works now: Credential validation and solver/device catalog context.
Limits and requirements: QFlow does not submit gate-circuit jobs to D-Wave; annealing workflows need a separate Ocean-style model.

Adapter audit: 2026-08-14

Source context

QuEra

Aquila / Braket route context

Planned direct path

Mode: Analog neutral-atom context
Works now: Public provider context and device positioning for planning.
Limits and requirements: Direct QFlow gate-circuit submission is not supported; typical access is through approved paths such as AWS Braket.

Adapter audit: 2026-06-03

Source context

Pasqal

Pasqal Cloud / Pulser context

Planned analog path

Mode: Analog/Pulser context
Works now: Credential and cloud-positioning context for analog planning.
Limits and requirements: Direct QFlow gate-circuit submission is not supported by this adapter.

Adapter audit: 2026-06-03

Source context

Need a provider pilot?

Start with one workflow, one route, one evidence packet, and one success criterion.

See pilot packages