Status pages

A status page is a public, unauthenticated URL showing the health of the workflows you choose. Create one under Status pages.

Each page is scoped to exactly one of an instance or a client workspace — not both, and not neither.

What a visitor sees

• An overall level: operational, degraded, or major disruption
• Per-workflow status
• Active incidents, described generically

What a visitor never sees

Incident descriptions on a status page are derived from the incident type, not from the incident itself. There is no raw error text, no workflow ids, no organisation name and no payloads.

Two of them are deliberately vaguer than the rest:

• A cost spike renders as "A run consumed unusually high resources", because your spend is your business and not a status-page visitor's.
• A business threshold renders as "A business metric moved outside its expected range", for the same reason — the metric name and its value are yours.

Status pages are served with noindex, so they do not turn up in search results for your customers' names.

Branding

Client-scoped pages can carry a logo and a brand colour, which is the white-label feature, on the Agency plan. Instance-scoped pages are unbranded.