Provider Routing

Select quantum providers, inspect hardware fit, and keep credentials private while routing workflows.

Updated August 14, 2026Public QFlow Studio docsNo credentials or customer data

On this page

Select provider context from the Studio The public ecosystem story maps to private provider setup

Provider routing connects the workflow objective 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.

QFlow Studio provider connections page without private token exposure — Provider setup and readiness stay private while route decisions remain explainable.

Section 01

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 selector opened from the Studio workflow canvas — The selector documents provider choice without exposing credential material.

Provider chosen
Backend context visible
Token hidden
Route fit checked

Section 02

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 evidence can name a provider route, but credentials stay sealed.

QFlow Studio public ecosystem section with providers, SDKs, and routing layer — The public ecosystem view explains coverage; private setup handles access.

Continue with

Run workflowsUnderstand run feedback, simulator and hardware execution paths, queue context, and safe retry behavior.Security modelUnderstand provider credential boundaries, reviewer-safe shares, role isolation, and safe documentation capture.ObservatoryUse observability surfaces to monitor provider readiness, workflow readiness, hardware setup, and operational signals.

Loading documentation