Paste a circuit. See the cost. Simulate first. Run when ready.
QRoute is a workflow layer that makes quantum computing easier to use. It helps users check whether a circuit can run, estimate cost before execution, compare provider options, and receive a clear result report.
Quantum access exists, but running jobs is still confusing.
Too many choices
Users must compare providers, hardware types, SDKs, plan limits, and pricing models before they can run anything.
Unclear pricing
Quantum jobs can include task fees, shot fees, runtime fees, reservations, and credits. Users need the price before submitting.
Wasted runs
Without simulation and circuit checks, beginners can spend money on jobs that are incompatible, too noisy, or hard to interpret.
Hard results
Many users can run an experiment but still struggle to understand what the output means or what to try next.
One guided workflow from circuit to report.
Paste
Paste or build a circuit using OpenQASM, templates, or supported SDK formats.
Check
QRoute checks qubits, gates, depth, shots, compatibility, and noise risk.
Price
Estimate cost before execution using provider fees, shots, runtime, and credits.
Simulate
Run a simulator first so users can catch mistakes before paying for hardware.
Submit a starter circuit through a simulator or quantum provider.
Use a simulator first, then switch the backend when you are ready. The circuit field accepts a Python list of IonQ QIS gate dictionaries, so you can edit experiments without changing the site code.
Tap any gate to add it to the circuit box.
Tap a template to replace the whole circuit box with a known example.
IonQ key configured https://api.ionq.co/v0.4
Submit a simulator job to see the IonQ job response here.
Rigetti simulator
Best for quick local testing with consistent ideal results. It does not need an API key and does not contact Rigetti cloud.
Local ideal simulatorIonQ simulator
Best for testing the same IonQ API path you will later use for IonQ hardware.
IonQ cloud pathIonQ quantum computer
Best for real hardware experiments after IonQ enables the QPU target for your project. It can use credits and may take longer.
Real hardwareEstimate the job before the user spends money.
QRoute should be honest about pricing. When exact provider data is not available, it should show a clear estimate range instead of pretending the number is guaranteed.
Give companies one clean integration layer.
QRoute can expose provider metadata, compatibility, and cost estimates through a simple JSON API. The current prototype includes Strangeworks, IBM, AWS Braket, IonQ, Azure Quantum, and a simulator option.
/api/providers
List supported providers, access models, hardware families, pricing fields, and supported formats.
/api/providers/{id}
Return one provider profile for routing, vendor comparison, or partner-specific setup screens.
/api/estimate
Submit provider, shots, runtime, markup, and credits to receive a transparent cost breakdown.
{
"provider": "ionq",
"shots": 1000,
"runtimeMinutes": 1.5,
"markup": 0.1,
"credits": 0
}Start where the need is already clear.
Classrooms and labs
Guided demos, repeatable assignments, budget controls, and clear reports.
Individual researchers
Compare providers, track costs, export experiments, and avoid wasted runs.
Quantum startups
Test small circuits and use API access without building every integration.
Developer teams
Run starter circuits faster without several cloud accounts or hidden fees.
Sell software value first, compute access second.
Free
Templates, simulator access, limited analysis, and limited saved reports.
Pro
More saved experiments, cost estimates, exports, and advanced checks.
Team
Shared workspace, budgets, team history, classroom or lab reports, and controls.
Enterprise
Governance, API access, integrations, procurement, support, and permissions.
QRoute complements providers instead of competing with them.
AWS Braket, IBM Quantum, Azure Quantum, Strangeworks, IonQ, Rigetti, and other suppliers prove that quantum access exists. QRoute sits above that ecosystem as the simple runner, pricing, and reporting layer.
Provider-neutral comparisons
Upfront pricing and cost history
Simulator-first workflow
Beginner-friendly explanations
Team budget controls
Saved experiment reports
Be honest about quantum limits and build the workflow first.
Low demand
Start with classrooms, labs, hackathons, and research groups where the need is clearer.
Wrong recommendations
Show transparent reasoning and confidence levels instead of claiming perfect decisions.
Difficult APIs
Start with simulator and reports, then add real providers one at a time.
Hard monetization
Charge for workflow, reports, saved history, and budget controls before compute markup.