Website: dockge.kuma.pet
Dockge is a self-hosted manager for Docker Compose stacks, from Louis Lam, the author of Uptime Kuma. It gives each stack a folder on disk with a normal compose.yaml inside, then puts a web interface in front of it for editing, starting, stopping and updating. Unlike tools that keep their own copy of your configuration in a database, Dockge reads and writes the files you already have, so docker compose from a shell and the web UI act on the same thing. It runs as a container itself, listens on port 5001 by default and expects your stacks under /opt/stacks unless you set DOCKGE_STACKS_DIR.
It is deliberately narrower than Portainer: the focus is compose stacks, with a reactive UI that streams pull, up and down output as it happens. If you need to manage single containers, networks or volumes without a compose file, the project’s own FAQ points you at Portainer or the Docker CLI instead. Version 1.4.0 added agents, so one interface can manage stacks across several Docker hosts. The 1.5.0 release updated the bundled Docker client to 28.0.4 and Compose to 2.34.0, and disabled the web console by default for security; you can turn it back on with DOCKGE_ENABLE_CONSOLE=true if you accept the risk. It needs Docker 20+ or Podman on Linux; Windows is not supported yet.
compose.yaml, so the file can be changed without leaving the interface.docker run command and get an equivalent compose file.docker compose commands; Dockge does not lock them into its own store.MIT. You can use it commercially, modify it and redistribute it, provided the copyright notice and permission notice are kept. There is no copyleft obligation on the stacks you manage with it.