current
Can I run circuits here?
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 studio
Public sample
Workflow
Bell State Demo
Bell State workflow
Qiskit Aer / 4,096 shots
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
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
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
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.
AI builder studio
AI builder preview
AI quantum builder
AI-generated, then checked by your team.
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
credentialedPublic stats
signed-in statusLocal runner
liveprovider access
hardware, cloud, runtime
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
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.
NIST testbed
Research ops
Build Bell, GHZ, QAOA, VQE, and custom circuit drafts, then run simulator checks before hardware time.
Runtime hardware
Provider rollout
Compare credentials, device capabilities, queue context, and routing constraints before submitting quantum jobs.
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.
01
36 min
UCL Quantum Labs / 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 analysis02
36 min
Daderot / Wikimedia Commons, CC0
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 analysis03
36 min
U.S. Department of Energy / Wikimedia Commons, public domain
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 analysisPilot path
Pilot plan, not a sales deck.
Start with a bounded circuit workflow, run it on the simulator or your providers, and leave with results your technical and security teams can inspect.
success criteria before setup
private credentials stay sealed
result and certificate pages are share-ready
step 01
Map the pilot
Agree on one circuit family, success criteria, owner, and simulator or provider path.
deliverable
Pilot brief
step 02
Connect safely
Configure roles, provider access, private tokens, and the approval path.
deliverable
Secure workspace
step 03
Run and validate
Execute simulator or hardware jobs, then inspect counts, probabilities, and traces.
deliverable
Result set
step 04
Approve rollout
Share approved results, certificate pages, and the rollout decision memo.
deliverable
Go-forward plan