Loading docs
Run & Route
Provider Routing
Select quantum providers, inspect hardware fit, and keep credentials private while routing workflows.
Updated May 26, 2026QFlow StudioNormal userTeacher
Provider routing connects workflow intent to available execution infrastructure. It should show fit, readiness, and provider context without exposing credentials.
The route decision belongs to the workflow record because it affects how results should be interpreted later.
Purpose
Select quantum providers, inspect hardware fit, and keep credentials private while routing workflows.
Where it fits
This page belongs to the Run & Route section and should be read with the related pages listed at the end.
Review boundary
Use screenshots and notes to explain product behavior without exposing private credentials, admin state, or customer data.
Select provider context from the Studio
Open provider selection from the workflow surface when possible. That keeps the route decision close to the circuit and generated code.
If the provider is not ready, fix setup in the private provider area. Do not paste tokens into docs, comments, run notes, or screenshots.
Provider chosen
Backend context visible
Token hidden
Route fit checked
The public ecosystem story maps to private provider setup
Marketing pages show recognizable providers and SDKs so teams understand the operating layer. The actual credentials and provider status remain in authenticated surfaces.
Keep this boundary clear in team documentation: public proof can name a provider route, but credentials stay sealed.
Next pages
Run workflows
Understand run feedback, simulator and hardware execution paths, queue context, and safe retry behavior.
Security model
Understand provider credential boundaries, reviewer-safe shares, role isolation, and safe documentation capture.
Observatory
Use observability surfaces to monitor provider health, workflow readiness, hardware setup, and operational signals.