Dockge

devops

Self-hosted Docker Compose stack manager with a clean web UI. Edit, start, stop, and update compose stacks from the browser with a real-time terminal and live status view

#docker#compose#management#devops#self-hosted

Quick Start

mkdir -p /opt/stacks /opt/dockge && curl -fsSL https://dockge.kuma.pet/compose.yaml -o /opt/dockge/compose.yaml && cd /opt/dockge && docker compose up -d

Overview

Dockge is a web-based manager for Docker Compose stacks, built by Louis Lam, the developer behind Uptime Kuma. Where Portainer exposes the full Docker API surface — individual containers, networks, volumes, images, registries — Dockge stays focused on compose stacks, which is how most self-hosted setups are actually organised. You work with stacks as the unit, not individual containers.

The interface reflects that focus. Each stack has its own panel showing container statuses, an editable compose file, and controls to pull, start, stop, and restart. A real-time terminal streams output directly in the browser when you run a command or tail logs. The whole design is noticeably cleaner than Portainer for compose-based workflows, because it does not expose operations that are not relevant to how compose stacks are managed.

The built-in compose editor means you can update a service version, add an environment variable, or change a port mapping directly in the browser, then restart the stack in the same view. For a homelab running a dozen compose stacks, this is a meaningful quality-of-life improvement over SSH sessions with a text editor.

The scope is intentionally limited. Dockge does not manage Kubernetes, Docker Swarm, or multi-server environments. It does not have the RBAC depth of Portainer or the breadth of features that come from years of development. For a single-server compose-based self-hosted stack, that scope is appropriate. For anything larger or more complex, Portainer is still the right tool.

Dockge: Pros & Cons

Pros (The Wins)Cons (The Friction)
Compose-centric:
Manages stacks as the unit;
matches how most people work.
Single server only:
No multi-host management
or centralised view.
Browser compose editor:
Edit files and deploy
without leaving the UI.
Compose only:
No Kubernetes, Swarm,
or individual container management.
Real-time terminal:
Live log streaming and
command output in the browser.
Newer project:
Less RBAC depth and fewer
integrations than Portainer.
23.3k stars:
From the Uptime Kuma author;
same clean design approach.
Directory structure required:
Stacks must follow Dockge’s
expected folder layout.

Use Cases

Specific ways to use Dockge for your workflow.

01
Manage multiple Docker Compose stacks from a browser without SSH-ing into the server to run docker compose commands
02
Edit a compose file, pull new images, and restart a stack from a web UI rather than the command line
03
Get a live overview of all your running stacks and their container statuses on a single dashboard
04
Give a non-technical collaborator access to start and stop specific services without shell access

Deployment Strategy

Recommended ways to host Dockge in your own environment.

docker
self-hosted