Compare monthly run capacity, hardware allowance, and collaboration headroom before you create a workspace. The values at right come from the public billing catalog.
Plans
The first three plans are self-serve. Researcher and Team add more execution headroom for sustained work, review, and collaboration.
Learning and small experiments
Starter access for learning and small experiments.
Monthly billing · prices in USD
Open samplesIncludes
Start with bounded circuits and reviewer-safe sample outputs.
Students and cohorts
Discounted learning tier for students and course cohorts.
Monthly billing · prices in USD
Explore academyIncludes
Enough room for classroom runs, AI help, and reusable lab templates.
Individual researchers
Higher limits plus hardware job access for individual researchers.
Monthly billing · prices in USD
Start accountIncludes
Higher simulator and hardware headroom for repeatable experiments.
Hardware-backed research
High-limit individual research tier for hardware-backed experiments.
Monthly billing · prices in USD
Plan research pilotIncludes
High-limit individual tier for sustained hardware-backed work.
Shared teams
Large project limits and shared operational headroom.
Monthly billing · prices in USD
Plan team pilotIncludes
Shared operating room for provider access, exports, and reviewer boundaries.
Choose by stage
Use the plan cards for quota, then use this path to see where each tier fits in a real quantum workflow.
Start with sample workflows, guided labs, and bounded execution before you need more capacity.
Move from exploration to higher simulator and hardware limits with clearer evidence review.
Keep provider access, exports, admin seats, and review boundaries legible as the project grows.
Limit matrix
These are QFlow usage limits. They do not guarantee third-party hardware provider quota or pricing.
Free
Free
Student
$9 / month
Pro
$29 / month
Researcher
$49 / month
Team
$99 / month
| Limit | Free | Student | Pro | Researcher | Team |
|---|---|---|---|---|---|
| WorkspaceWhat the account can keep active. | |||||
| Workflows | 5 | 25 | 100 | 250 | 1,000 |
| API keys | 2 | 3 | 10 | 20 | 50 |
| Block templates | 5 | 25 | 100 | 250 | 1,000 |
| ExecutionMonthly run and shot budget. | |||||
| Runs per month | 50 | 500 | 2,000 | 5,000 | 20,000 |
| Hardware runs per month | 2 | 5 | 50 | 150 | 500 |
| Simulation shots per month | 100,000 | 1,000,000 | 5,000,000 | 25,000,000 | 100,000,000 |
| Hardware shots per month | 8,192 | 25,000 | 200,000 | 750,000 | 2,000,000 |
| Shots per run | 4,096 | 10,000 | 20,000 | 50,000 | 100,000 |
| AI and evidenceAssistant usage, export, and team controls. | |||||
| AI messages per month | 30 | 500 | 2,000 | 5,000 | 20,000 |
| AI tokens per month | 25,000 | 500,000 | 2,000,000 | 8,000,000 | 20,000,000 |
| Data export | Included | Included | Included | Included | Included |
| Admin seats | Individual | Individual | Individual | Individual | 5 |
Workflows, API keys, and block templates are current-account limits.
Runs, hardware runs, simulator shots, hardware shots, AI messages, and AI tokens reset each billing period.
Hardware access means QFlow can store credentials, preflight routes, and enforce QFlow run limits. Provider availability, vendor quota, and provider charges are separate.
Exports and reviewer links exclude provider tokens, private billing state, admin notes, and raw credentials.
Pilot packages
A plan controls monthly usage. A pilot defines the workflow family, provider route, security review, academy cohort, or enterprise decision packet your team wants to validate.
Individual learners and early evaluators
Public samples, simulator-first workflows, generated source, and evidence previews.
Research and quantum ops teams
One workflow family, one provider route, one review packet, and a go-forward decision memo.
Universities, bootcamps, and internal enablement
Lessons, labs, progress tracking, certificates, and sample evidence for student attempts.
Security, platform, procurement, and regulated teams
RBAC review, provider key boundary, audit posture, procurement checklist, and private/public evidence split.
Enterprise review
Keep credentials, provider billing, and admin controls private while sharing the evidence packet a reviewer needs to approve the next workflow.