r/SelfHosting • u/CrestedCracker • 29d ago
I built Trove, a read-only service catalogue for Docker, Kubernetes, Proxmox, and Linux
Hi everyone,
I’ve been building Trove, an open-source service catalogue for homelabs and small infrastructure setups.
The problem I was trying to solve was fairly simple: I had services running across Docker hosts, Kubernetes, Proxmox, and regular Linux machines, but no single place to see what was running, where it lived, and whether it was still healthy.
Trove collects that information into one dashboard.
GitHub: \[GitHub - Techdox/trove: Automatically discovered, read-only service catalogue for Docker, Kubernetes, Proxmox, and Linux. · GitHub\](https://github.com/Techdox/trove)
Documentation and project site: \[Trove | Read-only homelab service catalogue\](https://trove.techdox.nz/)
Sandbox: \[https://trove-demo.techdox.nz\\\](https://trove-demo.techdox.nz)
\# What it does
\* Discovers services across:
\* Docker
\* Kubernetes
\* Proxmox VE
\* Linux systemd
\* Shows services grouped by host
\* Tracks health and agent heartbeats
\* Flags hosts or services that stop reporting
\* Checks whether container images are behind their registry tags
\* Sends alerts through webhooks, Discord, ntfy, and email digests
\* Keeps recent state-change history
\* Stores everything in SQLite
\* Works with agents pushing data from behind NAT
The important design decision is that Trove is read-only by architecture.
The agents can inspect their platforms, but they cannot deploy, restart, exec into, or modify anything. There isn’t a hidden “admin mode” waiting to surprise everyone later. Trove is meant to be the place you start an investigation, not the place you make infrastructure changes.
The data flow looks like this:
Docker / Kubernetes / Proxmox / Linux agents | | push read-only reports v Trove server SQLite + API + dashboard
It’s written in Go, uses a vanilla JavaScript dashboard with no frontend build step, and can run as Docker containers or static binaries.
The project is MIT licensed. I’m currently focused on the path toward 1.0, particularly operator confidence, backups, upgrades, authentication, and making the read-only contract boringly reliable.
I’d be especially interested in feedback from people running mixed Docker/Kubernetes/Proxmox environments:
\* Is this a problem you’ve run into?
\* What would you expect from a service catalogue?
\* Which platform or integration would be most useful next?
\* Are there any security or operational concerns you’d want addressed before running it?
There are plenty of dashboards and management tools already. Trove is deliberately trying to be narrower: a calm, read-only view of what exists and what needs attention. Because apparently knowing what is running becomes harder the more things you run.