SaaS with Statusboard
The page is set up for a typical SaaS: the web app, the API and email delivery. Customers get one link to check when something seems wrong, and you post updates there instead of answering each ticket.
- Rename the components to match what customers see and set real URLs.
- Save and add the status link to your app footer, help centre and status emails.
- During an outage, post an incident first, then update it as you learn more.
- Resolve the incident when it is over; it stays visible under past incidents for 14 days.
What to know
B2B buyers increasingly ask for a status page during evaluation, and support teams use it to deflect "is it down?" tickets during an incident. A page that updates on its own from health checks is credible in a way that a manually maintained one is not.
Write incident updates for customers, not engineers: what is affected, what they should do, and when you will update next. The four stages, investigating, identified, monitoring and resolved, give customers a sense of progress even when the fix takes time.
Three components cover most early-stage products. As the product grows, Pro adds up to 25 components per page, five pages for separate products or regions, 90 days of history and email alerts to you when a check fails.
Updated · Cosmovex
Questions
Where does the page live?
At tools.cosmovexapps.com/status/your-name. Choose the name when you create it.
How long do past incidents stay visible?
Resolved incidents show under Past incidents for 14 days.
Can I schedule maintenance?
Post an incident with the maintenance impact. The banner shows scheduled maintenance while it is open.
Is Statusboard free?
Yes: one page with 3 components, checks every 5 minutes, incidents and 30 days of uptime bars, with a small "Powered by Statusboard" footer. Pro is $9 a month for 5 pages, 25 components, 90 days of history, no footer and email alerts.
The free plan covers everything on this page. Statusboard Pro ($9/mo, billed monthly) is described on the Statusboard page.
