Over the past couple of weeks, a bunch of you asked me to take a look at Dockhand, so I finally got it installed, tested it, and did a full deep dive. I start by skimming the Dockhand site and the big headline features: it’s self-hosted only (no SaaS), zero telemetry, and it’s not phoning home. For a homelab, I really like that it can run with SQLite by default (even on something like a Raspberry Pi), but you’ve also got a PostgreSQL option if you want to build it out a bit more “seriously.” From there I walk through the interface and what it’s like actually managing Docker day-to-day: a drag-and-drop dashboard, quick host switching, containers, logs (including multi-container logs), shell access, and stacks. I also show the “gotcha” that if you didn’t deploy a stack from inside Dockhand, editing can be a pain until you redeploy/adopt it properly—very similar to Portainer/Dockge behavior. The really fun part is multi-server management with the Hawser agent, plus Git-based deployments. I deploy a stack straight from my repo, talk about scheduled Git sync and webhooks, and then dig into image management and built-in vulnerability scanning using Grype and Trivy. Finally, I cover settings like environments, registries, Git credentials, notifications via Apprise (I use Gotify), and why you should enable authentication early. Just keep in mind: Dockhand is brand new, so evaluate it accordingly before you bet the farm on it.