QP Cloud documentation
An introduction to the concepts behind QP Cloud, a workspace for observing distributed infrastructure.
These pages describe the platform direction and terminology. Public API access and general onboarding are not available yet.
Core concepts
QP Cloud organizes monitoring into workspaces, services, regions, and signals. These concepts provide a consistent language for describing what is running and how it is behaving.
Observability
The platform is designed to bring operational signals into a focused view. In the planned model, observations are grouped by service, region, and time range to reduce context switching during routine checks.
{
"service": "example-api",
"region": "eu-central",
"type": "health-check",
"state": "healthy",
"timestamp": "2026-01-01T12:00:00Z"
}Example only. Not a published API contract.
Edge agents
Edge agents are lightweight components associated with an infrastructure location. They can expose narrow operational information to local monitoring systems. An agent response should reflect the actual state of its HTTP component.
{
"service": "qp-cloud-web",
"status": "ok"
}The bundled /health route checks that this Laravel web application is responding; it does not monitor other infrastructure.
Access & availability
QP Cloud is in private beta. Workspace access is limited, and self-service registration is not currently available. Public documentation will be expanded as features become generally available.