Statuslab

Status pages

One Statuspage for System State

Publish component health, active incidents, and maintenance windows. Visitors and subscribers stay aligned without chasing threads or spreadsheets.
Get startedView demo
acme.status.example.com

Current status

All systems operational

Operational
APIOperational
DashboardOperational

Public hostname · no sign-in · live updates

Problem

Status scattered across channels confuses everyone

Teams answer the same questions in chat, email, and tickets. Customers lack a single place to verify what is affected and what is safe to use.

Duplicate answers

Stale screenshots

No shared timeline

A public status page gives you one structured surface for truth. Statuslab connects it to monitors, components, and incidents you already manage.

Surface

Everything on the page ties back to your project

Components reflect service health. Incidents and maintenance appear when you publish them. The public page is the read model your customers trust.

  • Component-level status
  • Incident and maintenance sections
  • Stable public hostname
Product Model

Visitor experience

Built for scanning, not noise

Visitors see operational components, current incidents, and scheduled work in a predictable layout. No login required for the public view.

Overall system statusPer-component healthIncident and maintenance summariesSubscriber-ready structure
status.yourdomain.com

Components · 90-day uptime

APIOperational
99.98%90 days
DashboardOperational
99.95%90 days

Incident · scheduled maintenance Sat 02:00 UTC

Composition

You control what appears and when

Components can be shown or hidden. Incidents respect visibility rules. Maintenance windows publish on your schedule.

Components

Map services to rows visitors recognize. Health rolls up from monitors and incident state.

Public hostname

Each page maps to a stable URL on your Statuslab domain so links stay shareable.

Subscribers

Structure updates so notifications and the page stay consistent.

Real-time

The Page updates without a refresh

When state changes in your project, connected visitors receive updates over the same realtime layer as your dashboard.

  • WebSocket delivery to public sessions
  • Operators and visitors stay aligned
  • No manual publish step for every change

Realtime layer

WebSocket /status

Connected

  • Project dashboard

    room project:8f3a…c1

  • Gateway

    fan-out to rooms

  • Public status page

    room page:acme

Payload
monitorcomponentincident

Incidents

Incidents you manage become updates customers read

Structured timelines and visibility rules carry through to the public page when you choose to publish.

Incident management

Maintenance

Planned work appears alongside live status

Schedule maintenance windows so visitors see upcoming work before it starts and resolution when it completes.

Maintenance

Summary

One page, connected to how you operate

Statuslab ties monitors, components, incidents, and maintenance to a public status page that updates in real time.

  • •Single hostname for customer-facing status
  • •Structured content instead of ad-hoc posts
  • •Dashboard and public surface stay in sync

Publish your status page

Create an account, define components, and publish a public page when your project is ready.
Get startedOpen status pages