Components and complete events
Publish incidents and maintenance against customer-facing components, with one terminal event per history row.
Operate public or private status pages without mixing the event archive into the daily workspace. Manage components, incidents, maintenance, subscribers, domains, access, and publication automation from seven focused areas.
The component model, event lifecycle, delivery record, and access policy stay explicit.
Publish incidents and maintenance against customer-facing components, with one terminal event per history row.
Confirm email subscriptions, deliver to email or webhooks, and retain attempts and errors for a configured period.
Use email or domain allowlists, magic-link sessions, DNS verification, and managed or edge-terminated TLS.
Match alert incidents or Synthetic monitors, delay transient failures, map component impact, and require approval when needed.
workflow
The overview remains short while active operations and historical records each get the right surface.
Create ordered components, visibility, language, branding, history, and delivery retention.
Draft the message, map affected components, then make the event public when it is ready.
Add immutable customer updates through investigating, monitoring, resolved, scheduled, or completed states.
Simulate ordered rules, correlate later transitions, and either approve the result or publish automatically.
proof / shipped
The current product includes a seven-tab administration workspace, public archive, subscriber delivery, private access, domain verification, TLS state, and automation candidates.
Operate public or private status pages without mixing the event archive into the daily workspace. Manage components, incidents, maintenance, subscribers, domains, access, and publication automation from seven focused areas.