Cairn gives the people you host services for one calm directory page that explains each service in plain language and shows whether it works right now. Your family does not want another dashboard; they want to know what this thing is and what to click. Group tools by need, write a welcome note in your own words, and give each service a Learn more page that explains whom to ask for an account. Status comes from the monitor you already run, Gatus, Uptime Kuma, Cachet, or a hosted status page, polled by your server so a visitor's browser never has to call anything. Labels say honestly where a service stands: coming soon, beta, new, deprecated, or retired, with dead links removed for the last two. Search finds the one service by name from anywhere on the page, eight shipped languages plus your own inline translations cover the relatives abroad, and legal notice and privacy pages are served by Cairn itself, because self-hosters never have anywhere to put those. The whole directory is one YAML file and a five-megabyte image. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. GPL-3.0 licensed.

Every homelab outgrows the browser bookmark folder, and Compass answers by building the front page for you, discovering your services automatically instead of asking you to maintain cards by hand. Point it at Docker, Kubernetes, Tailscale, Headscale, NetBird, DNS records, a JSON API, or a plain static list, and it renders everything it finds as a searchable directory with icons, descriptions, and tags filled in from a catalog when a source leaves them blank. Each card shows whether the service is actually up, using the Prometheus or Gatus monitor you already run, and pinned and recent services keep daily tools one click away. Opening a service reveals its connection details, source metadata, extra links such as runbooks and health endpoints, and panels you embed from Grafana. Markdown pages live beside the directory, so architecture notes and on-call runbooks sit in the same navigation, with live service cards and charts embedded directly inside the prose. A debug view shows per-source health, what each source returned, and why a service you expected is missing, while group-based access decides which sources each person can see. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache License 2.0 licensed.