Status pages
Branded, on your own domain, with component health and scheduled maintenance. You choose exactly what goes public — every status update is broadcast-eligible, but nothing reaches the page unless a responder explicitly turns it on for that update.
Public pages
Point a CNAME at your Waroom status page and verify it, or ship today on your Waroom address. Overall status, the active incident, upcoming maintenance, and every linked component in one page that refreshes on its own.
Component health
Link services from your catalog and organize them into named groups instead of one flat list. Each component carries a live status pill derived from alarms and incidents, an optional metrics toggle, and a public name independent of its internal one.
Maintenance windows
Schedule a window with a title, description, start and end time, and which components it affects. It saves as a draft until you publish it, then shows a scheduled badge on the public page with the advance notice subscribers asked for.
Subscribers
Visitors sign up from the public page itself, by email (confirmed via a link before it counts) or a signed webhook URL for their own systems, plus a public RSS/Atom feed for anyone who'd rather pull updates than get pushed them. Every subscriber shows up admin-side with its state — pending, confirmed, bounced, unsubscribed — with a one-click revoke and a CSV export.
Broadcast control
Every status update carries a "Publish this update to the status page" checkbox — unchecked by default, and separate from marking an incident customer-facing. Post several internal-only updates, then check the box on the one your customers should actually see.
