First run
Updated 2026-09-08 · Pharos 0.5.10
Sign in at /admin/login. Create services first — they are the headings
your customers read — then put components inside them.
A component with no service never appears on the public page and does not count toward the headline uptime figure, even though it still shows in the admin and is still checked. Always put components in a service.
Choosing a source
The Source field decides whether a check exists at all:
- Built-in check — creates an HTTP or TCP check with your target and interval.
- Heartbeat — generates an unguessable token once and shows you the URL to call.
- Manual, Uptime Kuma, Webhook, Upstream — no check row; status is set by hand or over the API. These labels behave identically inside Pharos today.
Hidden service versus disabled component
| Service hidden | Component disabled | |
|---|---|---|
| Shown to customers | No | No |
| Checks keep running | Yes | No |
| Counts toward headline uptime | Yes | No |
| History kept | Yes | Yes |
Hide a service to stop showing customers something you are still watching. Disable a component to stop watching it entirely while keeping its past.