Loading docs
Operate
Observatory and Readiness
Use observability surfaces to monitor provider health, workflow readiness, hardware setup, and operational signals.
Updated May 26, 2026QFlow StudioNormal userTeacher
The observatory is the product’s operating view. Use it before live work to confirm that providers, workflows, and run paths are healthy enough for the next step.
For production teams, the observatory is also a communication surface: it helps explain what is ready, what is blocked, and what needs attention.
Purpose
Use observability surfaces to monitor provider health, workflow readiness, hardware setup, and operational signals.
Where it fits
This page belongs to the Operate 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.
Readiness signals
Readiness is more useful than raw activity. Look for provider health, workflow readiness, run state, learning progress, and hardware observation signals.
A healthy dashboard should reduce surprises before execution, not become another wall of unrelated metrics.
Provider health
Run status
Workflow readiness
Learning activity
Next pages
Providers
Select quantum providers, inspect hardware fit, and keep credentials private while routing workflows.
Run workflows
Understand run feedback, simulator and hardware execution paths, queue context, and safe retry behavior.
Deployment
Operate the Docker stack, verify health checks, understand service boundaries, and prepare production deployment.