Skip to content

QFlow Studio

Build a circuit, run it, and share the result.

Design circuits visually, keep Qiskit and OpenQASM in sync, run simulators or provider routes, and share results as evidence — without exposing credentials.

Workflow

Bell State Demo

4,096 shots

Bell State workflow

canvas
q0q1q2t1t2t3t4t5INITq0..q1Initialize: q0..q1Hq0Hadamard: q0CXq0 -> q1Entangle: q0 -> q1IDq1No-op slot: q1Mq0,q1Measure: q0,q1CHECKcountsAttempt check: countsRESULTevidenceResult: evidence

Works with the quantum stack

Built on the SDKs and runtimes your team already uses — not a walled garden.

runtimes & access
  • IBM QuantumIBM Quantumruntime
  • AWS BraketAWS Braketaccess
  • Azure QuantumAzure Quantumcloud
  • IonQIonQtrapped ion
  • RigettiRigettisuperconducting
  • QuantinuumQuantinuumpytket
SDKs & formats
  • QiskitQiskitSDK
  • CUDA-QCUDA-QNVIDIA hybrid
  • CirqCirqGoogle circuits
  • OpenQASMOpenQASMexport

Names and marks belong to their owners. Listed as supported integrations, not endorsements.

Run record

Keep each circuit run in one place.

Store the brief, canvas, source, route, run status, trace, result, and share link together.

run record

QF-2048 supply-chain optimization

single source
01

Brief

objective + owner

02

Circuit

8 qubits / 24 ops

03

Source

Qiskit + QASM3

04

Runner

Aer / Cirq / qsim

05

Run

4,096 shots

06

Result

counts + trace

One live run record.

Version, owner, source, run state, and result move as one record.

versionv14
ownerQuantum Ops
runnerQiskit Aer
resultready

Security boundary

Share results, not secrets.

Publish read-only result pages, certificate pages, and share-safe links while credentials and drafts remain private.

Simulator result page

Bell-style counts

4,096 shots · probabilities · CSV/JSON export

complete

00

934

01

128

10

177

11

2857

Result page

counts, probabilities, JSON, CSV

Certificate page

issuer + completion status

Shared result

read-only public link

Private boundary

tokens stay sealed

Technical depth

What actually runs today.

A circuit can move from canvas to source, runner, counts, exports, and share-safe evidence without leaving the workflow record.

01 Visual blocks

Circuit JSON

02 Source

Qiskit / OpenQASM

03 Runner

FastAPI runner

04 Evidence

Counts / LaTeX / CSV

31q

default cap

<=8q

statevector

raw Python

off by default

current

Can I run circuits here?

Yes

current

Runner architecture

FastAPI + 4 simulators

current

Qubit limit

31q default

current

State output

<=8q statevector

runtime boundaries

Noise, CUDA-Q, and raw source stay clearly scoped.

6 noise modes

Noise models

Starters + workbench

VQE / QAOA

IonQ / IBM Eagle / Heron

Transpile targets

Off by default

Raw Python

AI Builder

AI drafts the workflow. Humans approve the run.

AI can draft circuits, route notes, source changes, and evidence summaries while the team keeps approval over provider submits and shared results.

saved
QAOA supply chain optimization

Design canvas

IBM Brisbane4,096 shotsWorkflow AI
CanvasAI draft applied
8 qubits

Provider status

Check providers before you submit.

QFlow shows credentialed device context, route fit, SDK output, OpenQASM export, and result artifacts for the same circuit. Live provider status appears after credentialed sign-in.

provider fabric

credentialed access layer

11

provider adapters

4

simulators

1

workflow record

Access

keys + devices

Route

fit + fallback

Run

QASM + counts

IBM Quantum

credentialed

Public stats

signed-in status

Local runner

live

provider access

hardware, cloud, runtime

6 connected

IBM Quantum

runtime

AWS Braket

access

Azure Quantum

cloud

IonQ

trapped ion

Rigetti

superconducting

Quantinuum

pytket

inputs

keys, account device state

QFlow

routing layer

outputs

code, QASM, counts

artifact layer

SDKs, code, results

4 connected

Qiskit

SDK

CUDA-Q

NVIDIA hybrid

Cirq

Google circuits

OpenQASM

export

Who it is for

Use QFlow for research, provider pilots, and classes.

Research operations, provider rollout, and academy cohorts start from circuits, source, and simulator output instead of a blank notebook.

Cryogenic quantum testbed used for research operations and pilot planning
NIST testbed

Research ops

Build Bell, GHZ, QAOA, VQE, and custom circuit drafts, then run simulator checks before hardware time.

IBM Quantum System One hardware used as a provider rollout reference
Runtime hardware

Provider rollout

Compare credentials, device capabilities, queue context, and routing constraints before submitting quantum jobs.

Quantum information research cohort used to represent academy learning workflows
Cohort lab

Academy cohorts

Give students runnable labs with source, counts, progress, comments, and certificates instead of passive notes.

Research briefings

Long reads tied to real quantum surfaces.

Source-backed briefings that connect current research to QFlow circuits, providers, algorithms, and learning flows.

View blog
Engineers assembling the cryogenic measurement path for qubits
01
36 min
FMNLab / Wikimedia Commons

hardware

Quantum RF sensing for defense 2026: field-ready evidence

A public-source guide to Rydberg RF sensing, robust quantum sensors, atomic receivers, defense caveats, lawful spectrum use, and validation evidence.

24sections6sources36min
Read long analysis
QFlow Studio runs history screen
02
36 min
QFlow Studio product capture

operations

Quantum telecom networks 2026: QKD, PQC, and 6G evidence

A practical telecom guide to EuroQCI, satellite and free-space QKD, optical ground stations, PQC for non-terrestrial networks, and 6G security.

24sections6sources36min
Read long analysis
QFlow Studio teacher academy overview screen
03
36 min
QFlow Studio product capture

education

Quantum healthcare and drug discovery 2026: evidence map

A current map of Q4Bio, protein-ligand simulations, quantum chemistry, oncology workflows, clinical caveats, and healthcare evidence packets.

24sections6sources36min
Read long analysis