Answer “is it you or me?” before the ticket
Per-component health, incident timelines, and operator notices — on your own domain. Every minute your status page stays silent during an outage is a support ticket you chose to receive.
The problem
Outages cost twice
Once when the system is down, and again in the hour your team spends replying individually to customers asking whether it is down. The second cost is entirely avoidable and usually larger.
A status page is the cheapest support automation there is: one update, written once, answers everyone who was about to write to you.
What you get
Everything in status pages
Components customers recognise
`API`, `Dashboard`, `Email delivery` — named for what a customer uses, not for your service topology.
Incident timeline
Investigating, Identified, Monitoring, Resolved. Each update is timestamped and kept, so the incident reads as a record afterwards.
Subscribers
Customers subscribe by email and are notified when an incident opens, updates, and resolves.
Operator notices
A banner without an incident — planned maintenance, a deprecation date, a migration window — without marking anything as broken.
SVG badge
A live badge for your README, docs, or wiki. It is an image, so it works anywhere an image works.
Your domain
Serve it from `status.yourcompany.com`. Customers should not have to trust an unfamiliar domain during the one hour they are least inclined to.
Step by step
How to set up a status page
Define components, connect a custom domain, and run your first incident.
- 1
Define components
List the parts a customer would name: API, dashboard, email delivery. Avoid internal service names.
- 2
Point your domain
Add a CNAME from status.yourcompany.com to the host shown in workspace settings, then enter the domain in SignlOS and wait for the certificate.
- 3
Invite subscribers
Link the status page from your product's footer and your support signature so customers subscribe before they need it.
- 4
Run the incident
Open the incident as soon as you have a symptom, set the affected components, and post an update every 30 minutes even when the update is 'still working on it'.
- 5
Resolve and write it up
Resolving notifies subscribers. A short cause afterwards turns an outage into evidence you are competent.
Questions
Frequently asked
Keep reading
Works with
Release notes
A changelog with an editor, categories, and a public feed. Publishing notifies everyone who voted for the linked posts — the loop from request to announcement closes itself.
Learn more →Knowledge base
Searchable help articles that deflect the questions your team keeps retyping. On the same portal as your boards, so customers never have to find a second site.
Learn more →Feedback boards
Customers post ideas and bugs, vote on the ones they care about, and get told when their request moves. You get a ranked list instead of a shared inbox.
Learn more →Full documentation lives at docs.signlos.com.
Your customers already told you what to build
It is in a support inbox, three Slack threads, and a spreadsheet nobody has opened since March. Put it somewhere it can be counted.
No credit card required to start. $0 forever.