Status Pages

Overview

Each project can publish one status page. Anyone with the link can open it without logging in. It lists only the applications you choose to show, and only their name, status and uptime. Nothing is published by default.

Publishing a Status Page

• Open the project and expand the Status Page section
• Check "Enable public status page" and enter a slug. The slug must be unique across the instance and can use only lowercase letters, numbers and hyphens (up to 80 characters)
• Optionally set a title. If you leave it empty, the page uses the project name
• Click Save, then under "Applications shown publicly" tick each application to list
• Use the View link to open the published page

Enabling the page and choosing applications both require the Operator role on the project. An application is listed only when the page is enabled and the application is ticked.

Public URL

https://<your-dashboard-domain>/status/<slug>

The page refreshes every 30 seconds. If the page is disabled or the slug doesn't exist, visitors see "Status page not found".

What the Page Shows

A banner at the top sums up the page: "All systems operational", "Some systems degraded" or "Major outage" when any application is down. Each application also shows its uptime for the last 24 hours, 7 days and 90 days.

How Uptime Is Calculated

DeployKit doesn't send external health probes. Uptime comes from the stored metrics instead: an hour with recorded metrics counts as an hour the application was up, because a stopped container produces no metrics. New applications are measured only from their first recorded sample, so a recent launch doesn't lower the 90-day figure. Values are rounded to one decimal. When there is no data yet, the page shows —.