Publish a status page from your own instance.
A public status page with per-service uptime bars and incident history, served from your own Checkmate instance with your branding. One URL answers 'is it down?' for the whole company.
Turn monitors into status.
The page reflects what your monitors see. Pick which monitors appear. Their status and uptime bars stay current without anyone editing a page mid-outage.
Incident history stays on the record, which reads as honesty: a service with a visible past is more credible than one that claims a spotless year.
- Per-service uptime bars
- You choose which monitors appear
- Incident history on the record
Make it look like your brand.
Upload your logo, pick one of 5 built-in themes and the page reads as yours. Customers checking status during an incident see your brand handling it, not a monitoring vendor's.
Because your instance serves the page, it lives on whatever domain you point at it. No CNAME upsell, no hosted-page subdomain.
- 5 built-in themes with light and dark modes
- Your logo and branding
- Any domain you control
Cut the tickets while you fix things.
An outage creates two jobs: fixing it and answering everyone asking about it. A status page does the second job for you, so the person who can fix it stays heads-down.
Selectable time ranges let visitors see the recent picture or the longer record, while monitor tags keep a busy page organised by team or product.
- Selectable time ranges on the page
- Monitor tags in the selector
- One link for support to share
For teams tired of answering 'is it down?'
SaaS teams
Customers check status before they file tickets, if you give them somewhere to check. Uptime bars and incident history do the explaining.
Agencies and MSPs
A status page per client shows the sites you manage are watched around the clock. It is proof of service you don't have to compile.
Internal platform teams
Self-hosted means the page can stay on the company network. An internal status page for internal services, without exposing anything.
See what it covers and what it doesn't.
Covered
- Public status pages with per-service uptime bars
- Incident history kept on the record
- Your logo, branding and choice of 5 themes
- Selectable time ranges for visitors
- Monitor tags in the status page selector
- Served from your own instance, on your domain
Out of scope
- Hosting: the page runs on your instance, there is no page-hosting service to depend on
- Third-party audit data: the page reports what your monitors observe
- Paging your team: that is what notification channels are for
For the technically curious.
Your instance serves it
The status page is part of your Checkmate deployment. Put it on a public domain for customers or keep it inside the network for internal services. Access follows your infrastructure.
Many pages from one instance
Pages are assembled from monitors you select, so one instance can serve different pages for different audiences: a public one for customers and a wider one for the team.
5 themes plus your CSS
Refined, Modern, Bold, Editorial and Minimal ship built in, each with light, dark and auto modes. Custom CSS on top overrides anything, with a live preview before you publish.
No separate uptime math
The uptime bars come from the same check history as your dashboard. What you see internally and what visitors see are the same numbers.
Frequently asked questions
Yes, by construction. Your Checkmate instance serves the page, so it lives on whatever domain you point at the instance. There is no hosted subdomain and no custom-domain upsell.
Yes. It is driven by your monitors, so service status and uptime bars reflect the latest checks without anyone editing the page during an incident.
Yes. Upload your logo and pick one of 5 built-in themes (Refined, Modern, Bold, Editorial and Minimal), each with light, dark and auto modes. Custom CSS covers anything beyond that.
Yes. You select which monitors a page shows, so you can run a customer-facing page with public services and a separate, wider one for the team.
Yes. Since your instance serves the page, keeping it on an internal network is an ordinary networking decision. Internal services get a status page without being exposed.
Yes. Status pages ship with Checkmate, open source under AGPL-3.0, with no subscriber fees or page limits.
