Quick Start
Five steps to your first run.
- 1
Open a starter template
From the Workflows page choose a template like Bell State or Grover Search. The studio loads the circuit on the canvas and a workflow is created in your active workspace.
- 2
Edit Design or Code
Place compact gates on legal qubit lanes or edit supported Qiskit, Cirq, or OpenQASM in Code. Both panes update the same circuit; use the splitter to give the active representation more room.
- 3
Run a simulation
Press Cmd/Ctrl+R or use the shared Run action in the Build header. The run setup chooses simulation, dry-run, or entitled hardware, then saves the execution record as it enters the queue.
- 4
Inspect the saved result
Use the Results rail in Build for the latest output or open Run results for persistent counts, trace, JSON, CSV, sharing, statistics, and side-by-side comparison.
- 5
Target real hardware
Add a provider API key in Settings → API Keys, switch the run mode to Hardware, and select a supported device. Submit-capable adapters validate the workflow, queue the job, and track it until it finishes.
Library
Curated starting points across entanglement, search, transforms, and variational algorithms.
Templates open in the signed-in library. Browse public examples on sample workflows without an account.
Algorithms
Common building blocks used across the studio.
Bell State
Created by a Hadamard on qubit 0 followed by a CNOT(0 → 1). Produces (|00⟩ + |11⟩)/√2, the simplest example of quantum entanglement. Underlies teleportation, superdense coding, and QKD protocols.
Grover's Search
Unstructured search in O(√N) queries versus O(N) classically. Alternates oracle reflection (marks the solution with a phase flip) and the diffusion operator (reflection about the uniform superposition) for roughly π/4·√N iterations.
Shor's Algorithm
Factors an N-bit integer in polynomial time by reducing factoring to order-finding, then solving order-finding with quantum phase estimation on the modular exponentiation operator. Famous for breaking RSA at sufficient qubit counts.
VQE
Variational Quantum Eigensolver: a hybrid quantum-classical loop that prepares a parameterized ansatz, measures the energy expectation value of a Hamiltonian, and updates the parameters classically to minimize energy. Used for molecular ground-state estimation.
QAOA
Quantum Approximate Optimization Algorithm: p alternating layers of a problem unitary e^(-iγH_C) and a mixer e^(-iβH_M) acting on a uniform superposition. A near-term heuristic for combinatorial problems like Max-Cut and MIS.
Providers
Simulation mode uses the configured runner path; in Docker, that is the Python quantum-runner by default. To use submit-capable hardware adapters or vendor-backed devices, add a provider API key.
The provider catalog covers IBM Quantum, Google Quantum AI, IonQ, Rigetti, Microsoft Azure Quantum, Amazon Braket, and additional device catalogs. Some integrations are credential/device-test only; unsupported direct submissions return validation or unsupported-provider errors. Keys are encrypted at rest and only used server-side.
Provider keys can be tested from Settings. Hardware health and device lists are fetched through the provider/device API routes, while the sidecar poller reconciles already-submitted hardware jobs.
Shortcuts
Grouped by context. On Windows and Linux, use Ctrl in place of Cmd.
Workflow
Common workflow actions. Browser/editable fields may reserve shortcuts while focused.
- Save workflowCmd+S
- Save workflow (Windows / Linux)Ctrl+S
Documentation
Reference for designing circuits, running them, and using the REST API.
Overview
QFlow Studio builds, simulates, and executes quantum circuits through local simulators and supported provider adapters. Author visually on the canvas or write supported Qiskit, Cirq, or OpenQASM; saved code changes can be parsed back into the workflow model.
Workflows are saved per workspace and versioned on publish. The shared Run action creates a saved record for the active circuit; simulation and submit-capable hardware adapters report counts, statevectors, trace, and timing into the Build results rail and persistent Run results where available.
The platform has three primitives: workflows (the circuit definition), runs (one execution on a backend), and providers (the cloud endpoints).
Building circuits
Place gates from the Design library onto legal qubit wires; targets snap to circuit time slots. Gate controls expose parameters, repeat, decomposition, and workflow actions. The synchronized Code editor parses supported Qiskit, Cirq, and OpenQASM back into the same circuit model.
from qiskit import QuantumCircuit
qc = QuantumCircuit(2, 2)
qc.h(0)
qc.cx(0, 1)
qc.measure([0, 1], [0, 1])Running simulations
Press Cmd/Ctrl+R or use the shared Run action. Runs are saved per workflow and can target simulation, dry-run validation, or entitled hardware. Shots and noise model are captured so result detail and comparison can replay the exact request.
API reference
Core workflow, run, provider, learning, and admin actions are exposed through REST routes. Browser sessions use the app session cookie; cron endpoints useCRON_SECRET bearer headers.
Support
Stuck, found a bug, or have feedback? We usually respond within one business day.