I built a self-hosted UI for Docker Compose across multiple hosts (single binary, no paid tier) - Dockmesh
retained text
Hi r/docker, I've been running Docker Compose on a few machines at home for years. Over that time I've tried quite a few management UIs, but never really found one that worked the way I wanted. Some didn't quite fit my workflow, others had things like SSO, multiple hosts or backups locked behind a paid tier. Eventually I decided to build my own. It's called **Dockmesh**, and I've just released version 0.5.1. **A bit about how it works** Dockmesh is a web UI for managing Docker Compose stacks across multiple hosts. One thing I wanted to keep from the start was the ability to work with normal Compose files. Your stacks stay as plain `compose.yaml` files on disk. You can edit them manually, keep them in Git or use `docker compose` directly without going through Dockmesh. The server is a single Go binary with the UI embedded. Other hosts run a small agent that connects outbound to the server over mTLS, so you don't have to open incoming ports on every machine. **What it can do so far:** * Manage Compose stacks across hosts, including deployments, rollbacks, Git-based deployments and moving stacks between hosts * Check for image updates, apply them and roll back if needed * Back up volumes, stacks and Dockmesh itself, with age encryption and support for local storage, SMB, SFTP, WebDAV and S3 * Manage users with scoped roles, SSO (OIDC, SAML, LDAP, OAuth2) and 2FA * Send alerts for containers, hosts, disks, backups and certificates * Run vulnerability scans using Grype * Optionally handle reverse proxying and HTTPS through Caddy There's also a hash-chained audit log, agent updates from the UI and a few other things. The UI is available in English and German. **Everything is open source (AGPL-3.0). There's no paid tier or separate edition.** **Getting started** The easiest way to install it is: `curl -fsSL` [`https://get.dockmesh.dev`](https://get.dockmesh.dev/) `| sudo bash` The installer detects amd64/arm64, verifies the checksum and sets up a systemd service. If you'd rather inspect the script before running it (understandably), it's available in the repo. There's also a manual installation guide. **A few things worth mentioning** This is still a pre-1.0 project, so there's definitely more work to do. I test releases on lab VMs before publishing them, including server/agent upgrades, older-version upgrades, backup targets and SSO login. I'm currently working on getting the initial server and host setup into the browser, along with an in-app updater. I also want to be upfront about AI usage: parts of the code were written with AI assistance. I review and test changes before releasing them. Dockmesh is mainly built for homelabs and small teams running anywhere from a few to a few dozen Docker hosts. It's not trying to replace Kubernetes. **I'd be interested to hear what you think**, especially from people already managing Compose stacks across multiple machines. What's something your current setup does that you'd miss if you switched? Repo: [https://github.com/Dockmesh/dockmesh](https://github.com/Dockmesh/dockmesh) Docs: [https://dockmesh.dev](https://dockmesh.dev/)
document fetched 2026-11-18 00:41 · canonical https://reddit.com/r/docker/comments/1xyeo51/i_built_a_selfhosted_ui_for_docker_compose_across