Practical guides
Start with the failure mode your customers actually feel.
Each guide maps a workload to the monitors, public components and rollout decisions that make a status page useful under pressure.
Ecommerce status page
Cart, checkout, payment, fulfilment, returns — the moving parts that determine whether a customer converts or leaves.
SaaS status page
Multi-tenant uptime, multi-region failover, and the page your customers open when they call their account manager.
Kubernetes status page
Container, pod, node, control plane, ingress, DNS, certificate, registry — each of these is a thing that can be up while everything else is on fire.
Self-hosted Uptime Monitoring status page
When you do not want a third party to know which services you run, when your monitoring tool needs to be on a different failure domain than the things it watches, or when 'managed' costs more than a half-day of ops time per month.
API status page
A clear service-health surface for the API endpoints, authentication flows and webhooks your customers build against.
SSL certificate monitoring status page
Catch an expiring certificate, an invalid chain or a hostname mismatch before browsers turn it into a customer-facing outage.
Agency client services status page
Give each client a clean, independent status page instead of turning every outage into an urgent support thread.