The page turns red when the assertion fails
Point a component at the monitors that prove it works. When an assertion fails, Assert changes the page, emails the subscribers and logs the incident.
Nobody edits the page during an incident
Assert already knows which assertion failed and in how many regions. It updates the components in the same second it pages the on-call engineer, so your users and your team are reading the same evidence.
- Every component follows its monitors without a switch to flip.
- Group components by service, so the page reads like your architecture.
- Assert emails subscribers when the incident opens and when it resolves.
- Users read 90 days of uptime, one square per day.
Every plan includes one status page
White-label branding and a custom domain come with any paid plan. The incumbents charge $208 a month for the same thing.
Custom domain
Publish at status.yourcompany.com. Assert issues and renews the certificate.
The checks update it
A component follows the monitors behind it. When the assertion fails, the page says so.
Subscribers
Users subscribe by email and get the same open and resolve messages your team does.
90-day history
A per-day uptime bar for every component, computed from the checks that ran.
White-label
Your logo, your colours, your CSS. Every paid plan includes it.
Incident log
Past incidents stay published, with what failed and how long it lasted.
Three audiences, one page
During an incident
The page answers "is it down?" so support can answer the questions only a human can.
In a sales review
A public 90-day history is easier to trust than a number in a slide.
For internal services
Keep a page private to your organisation and give every team the same view of the platform.
