Status pages

A status page is a public site (no sign-in) showing your services' health to your users, fed by the same checks and uptime data the console runs on.

Creating a page

In Status pages, Add page: pick a name and a slug. The page is served at <slug>.status.wakora.io over TLS immediately. Components are what visitors see as rows: map each component to a monitored site or host service, and its state follows the real checks (operational, degraded, down) with uptime bars over the last days.

Branding lets you set the page's name, logo and accent so it reads as yours.

A page can also live on your own domain: point a CNAME at your page's status hostname and save the domain; the record is verified on the spot (an honest "not visible yet" if DNS has not propagated), and the certificate is issued and renewed automatically. Nothing else to host.

Publishing updates

Incidents you choose to communicate are posted, never auto-published: an update has a state (investigating, identified, monitoring, resolved) and your text. The fastest path is from the incident itself: post to status page on the incident row prefills the state and title, you write the human sentence, publish. Updates thread on the page under the affected components.

Subscribers

Visitors can subscribe to updates by email (double opt-in: nothing is sent until the address confirms; confirmation and unsubscribe links live on your page's domain). Operators can additionally register webhook subscribers: a URL that receives every published update as JSON, signed with a per-subscriber secret shown next to the row, so the receiving side can verify it is really you.