Product
A System for
System Status
System model
Built on a clear system model
Four primitives connect end to end. Each layer has a job. Together they explain how state moves from probes to subscribers.
Monitors
Continuous checks and probe signals.
Components
Structure that maps to your architecture.
Incidents
Events with timelines and visibility rules.
Status pages
External communication from one source.
Statuslab is not a collection of features. It is a system.
- Monitors detect changes.
- Components represent system structure.
- Incidents organize events.
- Status pages communicate everything externally.
Detection layer
Detection Layer: Monitors
Define checks that continuously evaluate your system. Trigger checks on demand or run them on a schedule.
Check surface
| Region | Outcome | RTT |
|---|---|---|
| eu-central | OK | 238ms |
| us-east | OK | 191ms |
| ap-southeast | OK | 312ms |
System model
Model Your System with Components
Represent services, APIs, and infrastructure as components. Map monitors to components to reflect real system state.
Architecture
Components mirror how you think about services—not arbitrary group names.
Status sources
Roll up from monitors or set state when automation is not enough.
Visibility
Choose what appears on the public page versus internal views.
Ordering
Group and order components to match customer-facing priorities.
Incident timeline
Elevated API latency
Investigating
Initial triage and scope
Monitoring
Fix deployed; watching metrics
Resolved
Closed with timeline record
Event layer
Structure every incident
Track incidents from detection to resolution with a clear, structured timeline.
- Incident lifecycle management
- Real-time updates
- Public and internal updates
- Active and historical incidents
Communication layer
Publish system status
Provide a single source of truth for users with public status pages.
Components · 90-day uptime
Incident · scheduled maintenance Sat 02:00 UTC
Real-time
Real-time by design
All updates propagate instantly across dashboards and public pages.
Realtime layer
WebSocket /status
Events flow through one gateway to project dashboards and public status pages.
Project dashboard
room project:…
Gateway
Fan-out to rooms
Public status page
room page:…
Infrastructure
Distributed Monitoring
Run checks across multiple regions using distributed probes.
- Regions and probes
- Health-based probe coordination
- Scalable execution
- Worker-based architecture
Region registry
Probe workers register per region. The control plane tracks heartbeats and routes checks without duplicating configuration.
| Region | Label | Probes | Median RTT |
|---|---|---|---|
| eu-central | 12 | 38ms | Healthy |
| us-east | 14 | 22ms | Healthy |
| ap-southeast | 10 | 51ms | Healthy |
Architecture
Built for teams and projects
Manage multiple projects with isolated configurations and status pages.
Project isolation
Configuration, keys, and pages stay inside project boundaries.
Multi-tenant core
One platform deployment; many teams with separate namespaces.
Subdomain routing
Each status page maps to a stable public hostname.
Summary
A complete system for system status
Statuslab brings monitoring, incident management, and status communication into a single structured platform.
- •Detection through monitors and regions
- •Structure through components and incidents
- •Communication through pages and APIs