Since version 1.4.0, Dockge can manage more than one machine. The multi-agent feature connects a main Dockge instance to Dockge installations on other Docker hosts, so every stack in your network is reachable from a single dashboard.
How Dockge agents work
An "agent" is simply another Dockge instance running on another host. The main instance connects to it and mirrors its stacks into your sidebar, grouped per host. Actions you trigger — deploy, stop, update — run on the remote machine, with the same real-time output you get locally.
Setting up an agent
- Install Dockge on the second host using the normal install steps. Create its admin account.
- Open your main Dockge instance and go to the agents area of the interface.
- Add the agent by entering the remote URL (e.g.
http://192.168.1.20:5001) and the remote username and password. - Save — the remote host's stacks appear in the sidebar under its own group.
Working across hosts
- The host selector shows which machine each stack belongs to, so a stop on host B never touches host A.
- Stacks still live as plain files on their own machines — the file-based philosophy doesn't change.
- Each agent keeps working standalone; if the main instance is down, you can log into any host directly.
Security best practices for agents
- Connect agents over a private network or VPN (WireGuard, Tailscale), never over the open internet.
- Use unique, strong passwords per host — the login guide covers resets.
- Keep every instance on the same recent version; the update routine is two commands per host.
When multi-agent is the right choice
A NAS plus a VPS plus a Raspberry Pi is a common homelab spread. Instead of maintaining separate browser workflows for each host, Dockge multi-instance support can bring their Compose stacks into one primary interface.
How Dockge's multi-instance model works
Multi-instance support arrived in Dockge 1.4.0. The official release notes describe a primary Dockge instance that your browser connects to; that primary instance then forwards requests and responses to the other Dockge instances you add. This lets one interface list stacks from several hosts.
Network and security planning
Treat every connected Dockge instance as an administrative endpoint. Limit which hosts can reach each instance, prefer private networking or a VPN, use strong credentials, and keep every node updated. A reverse proxy in front of an agent can add complexity because Dockge uses persistent WebSocket communication.
Before adding another host
- Confirm the remote Dockge instance works on its own.
- Make sure the primary host can resolve and reach the remote address.
- Use compatible, current Dockge versions across hosts when possible.
- Document which server owns each stacks directory before migrating or reorganizing files.
Official references
Technical details in this guide are checked against upstream sources. Verify release-sensitive commands before changing a production host.