Practical education and research programmes
QFlow Academy connects lessons and lab workflows to generated code, attempts, instructor feedback, result records, and certificate verification for universities and research cohorts.
Available programme00Quantum workflow product
QFlow Studio makes the quantum workflow visible.
Build a circuit, inspect synchronized source, choose a simulator or provider route, and preserve a reviewer-safe experiment record.
- Visual
- Circuit and workflow canvas
- Synced
- Qiskit · Cirq · OpenQASM
- Human
- Provider submit and sharing
01Product flow
One record from brief to evidence.
QFlow adds continuity around official SDKs and provider tools; it does not replace their technical source of truth.
- 01
Make the circuit and its purpose visible
Start from a brief, build with circuit blocks, inspect parameters, and keep the reason for the experiment attached to the canvas instead of buried in a notebook thread.
Brief → canvas · Visual canvas · Circuit blocks · Workflow brief
- 02
Keep generated source synchronized
Move between the visual model and generated Qiskit, Cirq, or OpenQASM views so learners and developers can inspect implementation details without losing the workflow context.
Canvas → source · Qiskit · Cirq · OpenQASM
- 03
Validate locally, then choose a route deliberately
Use local simulator routes for fast checks, inspect provider and device context, and keep credentialed submissions behind explicit preflight and human approval.
Source → route · Local simulators · Provider preflight · Human submit
- 04
Turn a completed run into a reusable record
Keep run status, trace, counts, exports, source, route notes, and a share-safe evidence link connected so another person can review what happened without receiving credentials.
Run → evidence · Run history · Counts & exports · Share-safe evidence
Canvas to source
The implementation stays visible beside the workflow.
Generated Qiskit, Cirq, and OpenQASM views remain connected to the visual model so the record can be inspected without reconstructing context later.
03
Validate locally, then choose a route deliberately
Source → route · Local simulators · Provider preflight · Human submit
04
Turn a completed run into a reusable record
Run → evidence · Run history · Counts & exports · Share-safe evidence
02Use and roadmap
One evidence model, three ways in.
Education, research, and enterprise pilots share the same discipline while keeping their goals and acceptance decisions distinct.
Product prioritiesAvailable, pilot, beta, and core tracks.05 records +Close −
Accessible environments for builders
Visual workflows, synced source, starter circuits, and AI-assisted drafting help students and developers move faster while preserving a human decision before provider submission or sharing.
Available productFast, bounded enterprise pilots
Stage-gated pilots for quantum-safe migration and optimisation, defined by a measurable question, classical baseline, resource budget, evidence criteria, and an explicit stop or scale decision.
Pilot trackClearer workload access models
Make provider, device, credential, account, queue, and workload context understandable. Eligibility, pricing, credits, regions, and service terms remain controlled by each independent provider.
Beta access trackRepeatable research evidence
Keep the question, canvas, source, route, run trace, output, review note, and share boundary connected across iterations rather than scattering them across notebooks and screenshots.
Core track03Status and evidence
Route status stays explicit.
Provider eligibility, credentials, plans, queue state, pricing, region, and terms remain controlled by each independent provider.
Available now
- Visual circuit canvas and reusable workflow records
- Generated Qiskit, Cirq, and OpenQASM views
- Local simulator runner, counts, exports, and share links
- Academy labs, run history, and evidence packets
Credentialed / beta routes
- IBM Quantum, AWS Braket, IonQ, Rigetti, Quantinuum, and OQC submit-capable beta paths
- Azure Quantum validation/resource estimation and Google Quantum AI access preflight; direct submit disabled
- D-Wave credential and device test; no gate-circuit submit path
- Live provider state appears only after sign-in and remains subject to provider terms
Specialized / planned
- QuEra and Pasqal specialized analog paths
- Broader managed hybrid-job orchestration
- Expanded enterprise programme and governance packs
- qOS runtime and portable artifact foundations
Reusable experiment record
- 01Brief & acceptance
- The question, expected behavior, classical comparator, constraints, and stop condition.
- 02Canvas & source
- Circuit structure, parameters, generated source, format, and the version that was actually run.
- 03Route & preflight
- Simulator or provider route, device context, validation outcome, shots, seed, and non-secret configuration.
- 04Run trace
- Run identity, timestamps, state changes, failure or retry notes, and external job reference where one exists.
- 05Result & exports
- Counts or other outputs, post-processing notes, JSON or CSV exports, and comparison with the expected result.
- 06Review & sharing
- Reviewer note, decision, limitations, next action, and an explicit boundary that excludes credentials and private workspace data.
Security boundary: account references may be recorded; API keys, tokens, and provider secrets never enter the experiment manifest.
Official reference setExternal documentation remains the source of truth.05 sources +
04Guides and boundaries
Learn one operating question at a time.
Core workflow, runtime operations, and research practice remain available on demand instead of becoming a second product page.
01 · Core workflowProduct orientation, lifecycle, reproducibility, hands-on learning, inspectable source, and human-approved AI assistance.
QFlow Studio explained: from a visual Bell circuit to reviewable evidence.14 min readWhat is a quantum workflow? From a research brief to reusable evidence.15 min readReproducible quantum experiments need more than a histogram.16 min readHow to learn quantum computing: a practical beginner roadmap from first circuit to evidence.28 min readVisual Qiskit and OpenQASM workflows without losing code-level review.16 min readAI-assisted quantum programming needs a draft, verify, approve loop.16 min read
02 · Runtime operationsExecution modes, primitive contracts, simulator-to-QPU routing, and workload observability.
03 · Learning and research practiceBackend choice, mitigation, resource estimation, university lab design, and evidence-based assessment.
Quantum backend selection: choose for the circuit, not a universal leaderboard.17 min readQuantum error mitigation needs a controlled comparison, not an accuracy promise.18 min readFault-tolerant quantum resource estimation is an assumption ledger, not a hardware forecast.18 min readA university quantum computing lab program needs an operating model, not only exercises.18 min readA quantum computing lab rubric should reward prediction, reasoning, revision, and evidence.17 min read
Q01What is QFlow Studio?
QFlow Studio is Neura Parse’s visual quantum workflow platform. It connects a workflow brief, circuit canvas, generated Qiskit, Cirq or OpenQASM source, simulator or provider route, run history, results, and reviewer-safe evidence in one record.
Q02Is QFlow the same as QFlow Studio?
QFlow Studio is the full product name. People may shorten it to QFlow when the quantum context is clear, but unrelated companies, algorithms, and research projects also use QFlow. This page refers only to the Neura Parse QFlow Studio product at qflow.studio.
Q03Can QFlow Studio run a quantum workflow today?
Yes. Its public product surface supports visual circuit building, generated source, local simulator routes, run status, result counts, exports, and share-safe evidence. Credentialed provider routes carry explicit beta or validation status and require separate provider access.
Q04How do Qiskit and OpenQASM fit into QFlow?
QFlow keeps the visual circuit and generated implementation views connected. Qiskit can carry Python-based circuit and runtime work, while OpenQASM provides a portable circuit representation where supported. Provider SDKs and specifications remain the technical source of truth.
Q05Which quantum providers does QFlow Studio support?
The public status matrix currently labels IBM Quantum, AWS Braket, IonQ, Rigetti, Quantinuum, and OQC as submit-capable beta routes. Azure Quantum provides validation and resource-estimator context, Google Quantum AI provides access preflight, and D-Wave exposes credential and device testing without direct gate-circuit submission. QuEra and Pasqal are specialized planned paths. Verify the live matrix before planning access.
Q06Can I learn quantum computing with QFlow Studio?
QFlow Academy is designed for hands-on quantum computing learning through lessons, runnable lab workflows, generated code, attempts, instructor feedback, and certificate verification. Here, quantum learning means learning quantum computing; it is not a claim about the separate field of quantum machine learning.
Q07How does Neura Parse's IBM Partner Plus membership relate to QFlow Studio?
Neura Parse is an IBM Partner Plus member. That company-level ecosystem status does not make QFlow Studio an IBM product, imply IBM endorsement or IBM Quantum Network membership, certify a QFlow integration, or include IBM Quantum accounts, credits, plans, or hardware access.
Q08Does AI submit quantum jobs automatically?
No. The AI Builder can draft circuits, source, route notes, and evidence context, but a person remains responsible for verification, provider submission, and sharing. Simulator checks and visible approval boundaries are part of the operating model.
Q09What does a QFlow evidence packet share?
A reviewer-safe packet can connect the brief, circuit, generated source, selected route, run trace, result counts or exports, and review notes. Provider tokens, private credentials, and unrelated workspace data stay outside the shared record.
Start with a question worth answering.
End with evidence another person can inspect, reproduce, and use to make a stop, iterate, or scale decision.