dockge
A fancy, easy-to-use and reactive self-hosted docker compose.yaml stack-oriented manager
⭐ 23,071 stars on GitHub · 🍴 744 forks · 📜 License: mit · 💻 Language: TypeScript
What is dockge?
For teams that live in Docker Compose rather than Kubernetes, Dockge is a clean way to manage stacks without handing your setup over to a heavyweight control panel. Its differentiator is simple but important: your compose.yaml files stay as normal files on disk, so the UI complements the CLI instead of replacing it.
Main components
- Stack-oriented Docker Compose manager for creating, editing, starting, stopping, restarting, and deleting services.
- Interactive
compose.yamleditor with a responsive web UI. - Real-time pull, up, down, and terminal output so you can see exactly what Docker is doing.
- Built-in web terminal for hands-on troubleshooting without jumping between tools.
- Image update workflow for refreshing stack containers from the UI.
- Multi-agent support for managing Compose stacks across multiple Docker hosts from one interface.
- Converter for turning
docker run ...commands into reusablecompose.yamldefinitions. - File-based stack storage, keeping Compose projects accessible to normal
docker composecommands and external editors.
Clear use cases
- Run a homelab dashboard for managing self-hosted apps like Nextcloud, Jellyfin, Gitea, Immich, and monitoring tools.
- Give a small operations team a safer web UI for common Compose actions without requiring everyone to SSH into the host.
- Manage multiple Docker hosts from one place while keeping each stack defined as plain Compose files.
- Convert ad-hoc
docker runexperiments into maintainable Compose stacks. - Troubleshoot failed deployments with real-time logs and terminal access instead of waiting on a vague spinner.
- Standardize Compose stack management on Linux servers, Raspberry Pi boxes, or small edge nodes.
The biggest strength is respecting the Docker Compose workflow — Dockge does not try to hide your stack definitions in a database or proprietary abstraction. That makes it much easier to trust than many commercial or closed-source panels: you can still use Git, SSH, your editor, backups, and plain docker compose whenever you want. Compared with Portainer, Dockge feels narrower but sharper; it is focused on Compose stack management, and that focus is exactly why it works well.
It is not the right choice if you need full container platform governance, RBAC-heavy enterprise features, Swarm/Kubernetes management, or broad infrastructure inventory. But for self-hosters and small teams who mostly want a fast, understandable UI over Docker Compose, the trade-off is excellent.
Best for homelab admins, small-business sysadmins, and developers running multiple self-hosted Docker Compose stacks who want a polished UI without giving up file-based control.
Topics: the project is tagged with popular topics:
- 🏷️
docker - 🏷️
docker-compose - 🏷️
docker-deployment - 🏷️
docker-stack - 🏷️
docker-stack-deploy - 🏷️
docker-ui - 🏷️
responsive - 🏷️
self-hosted - 🏷️
selfhosted - 🏷️
single-page-app
📸 Screenshots
Quick install
The project supports Docker Compose:
git clone https://github.com/louislam/dockge.git
cd dockge
docker compose up -d
Check the README in the repo for required env variables.
Minimum system requirements
| Component | Recommended |
|---|---|
| RAM | 1024 MB |
| CPU | 1 vCPU |
| Disk | 15 GB SSD |
| OS | Ubuntu 22.04 LTS / Debian 12 |
| Docker | 24.0+ |
⚡ Deploy fast on VSIS
Use the VSIS VPS Mini 1GB RAM / 1 vCPU / 15GB SSD (~70k/tháng) plan from VSIS.NET — high-speed VN-based VPS, 24/7 support, ideal for running dockge smoothly.
🎯 Benefits:
- One-command
docker compose up -ddeploy in 2 minutes - Dedicated IPv4, root access, unmetered domestic bandwidth
- Daily snapshot backup
- Free install assistance from the VSIS team
👉 See matching VPS plans at vsis.net
Resources
- 🔗 GitHub: louislam/dockge
- 🌐 Homepage: https://dockge.kuma.pet
- 📚 Official docs: see README in the repo
- 💬 Community: GitHub Issues + Discussions
Article compiled from GitHub data on 05/05/2026. Star/fork counts may have changed — see live numbers via the GitHub link.