Self-hosted Docker management
Your Docker hosts.One control plane.
Manage containers, Compose stacks, logs, health and operations across your Docker hosts from one interface, on infrastructure you run yourself.
- Self-hosted
- Multi-host
- Security-first
Hosts
4
connected
Containers
38
across all hosts
Compose projects
7
discovered
Needs attention
1
workload
| Host | State | Containers |
|---|---|---|
| docker-01 | 12 | |
| docker-02 | 8 | |
| storage-01 | 6 | |
| apps-01 | 12 |
Needs attention
paperless-db
Health check failing
docker-02
01Operations
Docker operations without host hopping.
Stop moving between SSH sessions and separate Docker endpoints. Every connected host is managed from the same interface, and the work still happens on the machine itself, through its agent.
All hosts in one place
See workloads, health and resource state across every connected Docker host.
Operate safely
Run, create, change and remove workloads through defined agent capabilities, with backend-enforced permissions and audit history.
No inbound port
Each Docker host runs one small service that connects outward to the control plane, so managing a host does not mean opening a port on it.
02Multi-host
Built for more than one Docker host.
Host state, workload counts, agent status and health signals are in one list, without a separate management session per machine. A host that has been replaced can be archived, which takes it out of the working lists without losing what it ran.
| Host | State | Containers | Docker | Agent |
|---|---|---|---|---|
| docker-01 | 12 | 27.3.1 | Connected | |
| docker-02 | 8 | 27.3.1 | Connected | |
| storage-01 | 6 | 26.1.4 | Connected | |
| apps-01 | 12 | 27.3.1 | Connected |
03Stacks
A Compose file, its history, and the host it runs on.
A managed stack keeps its Compose configuration, the environment it needs and every revision it has had, so deploying an earlier one is the rollback. Compose projects already running on a host are discovered and grouped alongside them, and stay read-only.
Nextcloud
- nextcloudnextcloud:30-apache
Running - postgrespostgres:16-alpine
Running - redisredis:7-alpine
Running
04Operational context
Know what is happening before you touch it.
Read a workload's state, its health, its output and the events around it before you act on it. The context sits beside the thing you are managing rather than in a separate tool.
State
Running
up 6 days
Health
Unhealthy
check failing since 10:43
Restarts
3
since it was created
Logs
10:42:18 nextcloud Server started, listening on port 8010:42:19 nextcloud Cron job finished in 0.42s10:43:02 paperless-db Health check failed (exit code 1)10:43:12 paperless-db Health check failed (exit code 1)10:43:22 paperless-db Container marked unhealthyRecent events
- 10:43:22Workload marked unhealthypaperless-db
- 10:31:05Container restartednextcloud
- 09:58:41Host reconnectedstorage-01
05Security
Remote control without a remote shell.
An agent exposes a fixed set of operational capabilities and no way to run a command. Each host holds its own identity, the channel between it and the control plane is encrypted, and the control server authorizes an action before any agent is asked to perform it.
Unique agent identity
Each enrolled host uses its own agent identity and can be revoked independently.
Explicit capabilities
Operations such as restarting a container or reading logs use defined and validated actions.
Permissions by operation
Backend-enforced permissions decide who may perform which operations. Restarting a container and removing one are separate grants.
Auditable changes
Security-relevant and infrastructure-changing actions are recorded with actor, target and result context.
Browser session
Dockplane application
An authenticated operator requests an operation on a workload.
HTTPS
Control server
Checks the session, applies backend authorization and attaches audit and correlation context.
Authenticated agent channel
Dockplane agent
Accepts a named capability with a validated payload and re-checks it before acting on the host.
Docker Engine API
Docker Engine
Performs the requested operation locally on the managed host.
Example capabilities
host.metricscontainer.inspectcontainer.logscontainer.restartcontainer.replacestack.deploy06Versions
What is running, and what is not updating itself.
Settings reports the control server, the browser application, the database schema, the agent protocol range and what every enrolled agent reports. A fleet part-way through a rollout is marked as running mixed versions rather than as broken.
No self-updating
Dockplane can check the public release listing and say whether something newer exists. It is off until an administrator turns it on, and nothing acts on the answer.
Upgrade in your own order
Upgrade the control plane first, then the agents. An older agent keeps working while its protocol version is one the server accepts.
Usable at the width you have
The management lists and settings adapt to the space they are given, down to a stacked list below a tablet's width.
07Self-hosted
Your control plane belongs on your infrastructure.
Dockplane runs on systems you control and works without an external management service.
No vendor account
There is no service to sign up for and no tenant at a provider. The accounts Dockplane knows about are the ones you create in your own installation.
Understandable
The architecture, permissions and agent trust model are documented instead of being hidden behind a remote service.
Scoped to Docker
What Dockplane manages is Docker and its immediate operational environment. It is not on its way to becoming a datacenter panel.
Bring your Docker hosts together.
Deploy Dockplane and manage your Docker environment from one self-hosted control plane.