Monitoring Dashboards

One live view of every check, shared with anyone you choose

Checkly dashboards show the status, availability, and P95/P99 of your checks on a page you can hand to your team, your stakeholders, or the public. Filter by tag, serve it from your own domain, style it with CSS, and define the whole thing in code.

Start for freeView docs

Trusted by teams that put their uptime on display

Vercel
Carhartt
CrowdStrike
Airbus
Fanatics
Mistral
ServiceNow
GoFundMe
Hopper
1Password
Fastly
Total Wine

The status of your stack, without a login to Checkly

Your checks already know whether checkout works and how fast the API answers. A dashboard puts that on a page anyone can open: the on-call engineer on a wall monitor, a product manager in a browser tab, or a customer on status.acme.dev. No Checkly account required, unless you want one.

tags: ["production", "api"]

Tags decide what shows up

A dashboard is a tag filter, not a hand-picked list. Tag a new check "production" and it appears on the production dashboard on its next run. Combine tags with OR, or require all of them with the AND operator.

isPrivate: true

Public by URL, or private by password

Every dashboard is public by default at its own URL. Flip it to private and viewers need the dashboard password. Enterprise accounts can also gate it behind a Checkly login.

customDomain: "status.acme.dev"

Your domain, your logo, your CSS

Serve it from a checkly-dashboards.com subdomain or CNAME your own domain to it. Set the logo, logo link, and favicon, then restyle every element with the built-in CSS editor.

Dashboards are the live, check-level view for people who want detail. For customer-facing incident communication around named services, pair them with Checkly status pages.

The dashboard is a construct, not a settings page

Dashboard is a first-class construct in the Checkly CLI. Header, tag filter, custom domain, logo, refresh rate, incidents, privacy, and the CSS file all live in your repo next to the checks they display. Review it in a pull request, deploy it from CI, and every environment gets the same one.

  • Tag filter with OR by default, AND with useTagsAndOperator
  • Refresh every 60, 300, or 600 seconds; paginate long check lists
  • Toggle P95, P99, tags, and the header per dashboard
  • Custom CSS from a file in your repo, deployed with npx checkly deploy

Prefer clicking? Every option has parity in the app. Construct reference in the Dashboard docs.

dashboard.check.ts
1// dashboard.check.ts
2import { Dashboard } from 'checkly/constructs'
3import * as path from 'path'
4
5new Dashboard('production-status', {
6 header: 'ACME Production Status',
7 description: 'Live status of the checkout, API, and platform services',
8
9 // Every check tagged "production" shows up here automatically
10 tags: ['production'],
11
12 // status.acme.dev, with a CNAME pointing at checkly-dashboards.com
13 customDomain: 'status.acme.dev',
14 logo: 'https://acme.dev/logo.svg',
15 favicon: 'https://acme.dev/favicon.ico',
16 link: 'https://acme.dev',
17
18 // Refresh every 60s; show availability, P95, and P99
19 refreshRate: 60,
20 showP95: true,
21 showP99: true,
22 hideTags: false,
23
24 // Publish incidents and maintenance notices on this dashboard
25 enableIncidents: true,
26
27 // Password protected (Team and Enterprise plans)
28 isPrivate: true,
29
30 customCSS: {
31 entrypoint: path.join(__dirname, 'dashboard.css'),
32 },
33})

Looks like yours, because it is yours

Every dashboard starts on a subdomain of checkly-dashboards.com. Point a CNAME at it and it answers on status.acme.dev instead, TLS included. Then set the logo, the logo link, and the favicon, and restyle the rest in the CSS editor. Every element has a documented class, from the header to the incident cards to the login box.

  • Custom subdomain on checkly-dashboards.com, or a CNAME to your own domain
  • Logo, logo link, and favicon set in Look & Feel
  • Built-in CSS editor with boilerplate generation and a class-name hints tab
  • Custom CSS on Team and Enterprise plans

Class reference and styled examples in the custom CSS docs.

Say what is happening, right where people are looking

Green tiles are not the whole story during an outage. Publish an incident on the dashboard from the Checkly app in seconds, mark it major or minor, and post updates as you move from investigating to resolved. Planned work gets a maintenance notice instead of a surprise.

  • Three incident types: major impact, minor impact, maintenance
  • Updates through Investigating, Identified, Monitoring, Resolved
  • Incidents are scoped per dashboard, so each audience sees its own
  • Past incidents stay listed chronologically for later reference

Incidents are a paid-plan feature. Details in the incidents docs.

Internal numbers stay internal

Not every dashboard belongs on the open web. Turn on password protection and Checkly generates a password for your viewers. It works on the checkly-dashboards.com URL and on your custom domain alike. Enterprise accounts can require a Checkly login instead, so access follows your team roster.

Public
Anyone with the URL. The default.
Password
One generated password per dashboard. Team and Enterprise.
Checkly login
Sign in with an existing Checkly account. Enterprise.
Scope
Access is set per dashboard, so public and private can coexist.

Setup steps in the dashboard configuration docs.

Frequently asked questions

Everything you need to know about sharing check status with Checkly dashboards.

A Checkly dashboard is a hosted page that shows the live status of your checks and monitors: passing, degraded, or failing, plus availability and P95 and P99 response times over the last hour up to the last 30 days. You choose which checks appear by tag, and you can publish incident and maintenance messages on it. Each dashboard gets its own URL, either a subdomain of checkly-dashboards.com or a custom domain you own.

A dashboard is the live operational view: check-level detail, response-time percentiles, and tag filtering, for a team or for anyone you share the URL with. A Checkly status page is the customer-facing communication surface, built around services and incidents rather than individual checks. Many teams run both: a dashboard for engineering and a status page for customers.

All of them by default. Add one or more tags to the dashboard and only checks carrying those tags are shown. Tags match with OR unless you turn on the AND operator, in which case a check must carry every listed tag. Because the filter is tag-based, new checks appear on the right dashboard without anyone editing it.

Yes. Toggle password protection in the dashboard settings and Checkly generates a password for viewers. The password works on both the checkly-dashboards.com URL and your custom domain. Private dashboards are available on Team and Enterprise plans, and Enterprise accounts can additionally require a Checkly account login.

Add your domain, for example status.acme.dev, in the dashboard settings, then create a CNAME record at your DNS provider that points to checkly-dashboards.com. In some cases you will also be asked to add a TXT record to verify domain ownership. Checkly provisions TLS for the domain.

Yes. Dashboard is a construct in the Checkly CLI, so header, tags, custom domain, logo, refresh rate, P95 and P99 visibility, incidents, privacy, and even the custom CSS file live in your repository next to your checks. Deploy it with npx checkly deploy like everything else.

Hobby and Starter plans include one dashboard, Team includes ten, and Enterprise plans are custom. Custom CSS and private dashboards are Team and Enterprise features. Incidents require a paid plan.

Put your uptime where people can see it

Tag your checks, create a dashboard, share the URL. Every plan includes one, and it takes less time than your next standup.

Start for freeBook a demo