Skip to content
QuickStatus.dev

A private status page your checks keep current

Some status is for a smaller audience: the internal tools your team depends on, a staging environment, or a page for a few large customers. A private QuickStatus.dev page shows the same live components and incidents as a public one, behind one shared password.

Private pages are part of Pro, $15/month for the whole workspace.

Start free, no card Read the status page docs

Who it is for

  • Your team. One place to see whether the admin panel, the internal API, or last night's backup is fine, before anyone asks in chat.
  • A few key customers. A page for a dedicated deployment that only that customer should see.
  • Before you go public. Build the page, link the checks, and watch it for a week. Switch it to public when you are ready.

How it works

  • Same page, one password. The page stays at its URL. Visitors see the page name and logo, then a password field. After they enter the shared password once, the page works as usual.
  • Kept current by checks. Link each component to a check. With Create an incident automatically on, a confirmed failure opens an incident and resolves it when the check has stayed up. Maintenance windows and 90-day uptime bars work the same as on a public page.
  • Your own domain. Serve it at a hostname such as status.yourcompany.com with a CNAME and a TXT record. The password still applies there.
  • Switch any time. Make an existing page private on Page settings, or switch it back to public, which clears the password.

What changes when a page is private

  • Subscribe and RSS are off, so updates cannot be passed on without the password. Your team hears about problems through alerts instead: email, Slack, Discord, PagerDuty, Telegram, or a webhook.
  • The status badge returns 404.
  • Everyone uses the same password, at least 8 characters. There is no per-person sign-in or SSO yet.
  • If the workspace leaves Pro, private pages stay locked until you switch them to public.

Checks for things inside your network

HTTP, DNS, and TCP checks need a public address. For what only runs inside your network, the check reports out instead: a heartbeat check for jobs and backups, and the server agent for Linux servers. Both can drive a component on a private page.

Set it up

  1. Sign in and click New status page. Give it a name; the subdomain fills itself in.
  2. Check Make status page private and set a shared password of at least 8 characters.
  3. Optionally add a Custom domain, then add the CNAME and TXT records shown on Page settings.
  4. Add components, link a check to each, and under When the check is down pick Create an incident automatically.
  5. Share the link and the password with the people who need them.

Pricing

  • Pro, $15/month: 5 status pages in any mix of public and private, a custom domain, 25 checks every 60 seconds from 5 regions, and 90 days of results
  • Free: 1 public status page. See what the free status page includes.

See pricing

Private status page FAQ

Can I have a public page and a private page?

Yes. Pro includes 5 status pages, in any mix of public and private. Private does not use a separate quota.

Does a private page support SSO or per-person logins?

Not yet. A private page uses one shared password of at least 8 characters for everyone who opens it.

Can visitors subscribe to a private page?

No. Subscribe and RSS stay off on private pages, so updates cannot be passed on without the password. Tell your team through alerts instead: email, Slack, Discord, PagerDuty, Telegram, or a webhook.

Can I monitor services that are not on the public internet?

HTTP, DNS, and TCP checks need a public address. For jobs and servers inside your network, heartbeat checks and the server agent report out to QuickStatus.dev, so they can still drive components on a private page.