PatchPanda is a self-hostable update manager for Docker Compose stacks: a web UI that inventories your running stacks, works out which image tag every service uses, traces each image back to its GitHub repository and then reports the newer releases with their notes – so an update is something you can read and review rather than a silent pull-and-restart.
It is written in .NET 10 with Blazor Server and ships as a single container. Rather than replacing your deployment manifests, it edits the compose and .env files you already have and then runs the ordinary docker compose pull and docker compose up -d for the target stack. You keep the files, and you can still roll back by hand.
app-web and app-worker) so a multi-container stack moves as a single unit.Watchtower-style agents watch image tags and restart containers when a new image appears. PatchPanda is release-oriented: it reads GitHub release notes, surfaces pre-releases and breaking-change markers, understands multi-container apps, and shows you an update plan before anything runs. That makes it a fit for hosts where you want to know what changed while still automating the routine pins.
The published image is ghcr.io/dkorecko/patchpanda:latest and the web UI listens on port 5091, with a reference compose file in the repository. It needs the Docker socket mounted at /var/run/docker.sock to see your stacks, BASE_URL so notification links point somewhere useful, and GITHUB_USERNAME with GITHUB_PASSWORD (a personal access token) for release lookups. AI summarisation and security scanning are optional: set OLLAMA_URL and OLLAMA_MODEL to enable them. Discord and Apprise notifications are optional as well.
Mounting the Docker socket gives the container control over the host daemon, so treat it as a privileged service and keep it on an internal network.
Beta software. The author ships PatchPanda as-is: keep backups, try it on non-critical stacks first, and expect the interface to change.
MIT – free and open source; the licence text is in the repository.