Catalog & integrations¶
Top-nav Catalog (/catalog → 303 to Integrations) is the hub for optional products and topology. Each section shares:
- An ops-hero (title + dual-line pulse for the section)
- A full-width tab bar under the hero: Integrations · Certificates · Templates · Network
| Tab | Path | Purpose |
|---|---|---|
| Integrations | /integrations (default) | Connect Kuma, Grafana, Pi-hole, NPM |
| Certificates | /certificates | TLS vault + service maps + SSH deploy |
| Templates | /templates | Service template catalog & deploy |
| Network | /dns | Host DNS, service paths, Hosts/Path maps (Network maps) |
Core fleet ops (SSH, backups, patch, Docker) work without any Catalog entry.
Integrations (products)¶
| Product | Role |
|---|---|
| Uptime Kuma | Status, TLS days, deep links, fleet Services |
| Grafana | Dashboard inventory, deep links, preferred names (Inventory tab) |
| Pi-hole | v6 multi-instance stats, local DNS/CNAME fan-out, gravity/actions |
| Nginx Proxy Manager | Proxy hosts (read-only) + certificate pull into vault |
| Certificates | Encrypted store, PEM upload, deploy maps, NPM renew |
| Network maps | Host A + service paths; Pi-hole adopt; LAN/cloud/Internet Hosts map + Path map |
Credentials and cert PEMs are Fernet-encrypted and included in self-backup.
Design principle¶
- PiHerder owns fleet truth
- External tools enrich via adapters and deep links
- Prefer n8n + token REST over embedding every vendor API
Related¶
- Operator scenarios — task index
- Templates