Features
Everything Dockplane manages, area by area.
Dockplane is deliberately scoped to Docker and its direct operational environment. What belongs to the product, what is planned and what stays outside it are all set out below.
01Capabilities
Hosts
Every connected Docker host in one inventory, with the state you need before acting.
Host inventory
Hostname, operating system and Docker Engine version per connected host.
Connectivity state
Online, offline and stale state, shown as state rather than as silence.
Host metrics
CPU, memory and disk signals for the host itself.
Workload counts
How many containers and Compose projects a host is carrying.
Agent state
Whether the agent is connected and which protocol version it reports.
Archiving
A host that has been replaced leaves the working lists and keeps everything it carried. Reversible, and not a delete: no host record is removed and none is merged with another.
02Capabilities
Containers
Every container on a connected host can be read and run. The ones Dockplane created can also be changed.
Container list
Containers across all connected hosts, filtered by host.
Inspect
Image, configuration, ports, mounts and labels for a single container.
Health state
Configured health checks and their most recent result.
Logs
Container log output with a timestamp column and horizontal scrolling.
Run state
Start, stop and restart any discovered container, through validated capabilities.
Create a container
Image, ports, mounts, environment and restart policy, from a typed specification.
Change a container
Editing replaces the container and keeps its identity and history. Volumes are never removed.
Remove a container
Available for containers Dockplane created. A discovered one keeps a read-only configuration.
03Capabilities
Managed stacks
A Compose file Dockplane holds, with its history, deployed to a host you choose.
Saved configuration
A Compose file and the environment it needs, stored with the stack.
Encrypted values
A value marked secret is stored encrypted and never shown again.
Revisions
Every saved configuration is kept, with the difference to the one before it.
Configuration rollback
Deploying an earlier revision is the rollback. It restores configuration, not volumes.
Deploy
The control server resolves the plan; the agent applies it and reports the result.
Stack lifecycle
Start, stop, restart and delete a deployed stack as one workload.
04Capabilities
Compose projects found on a host
Projects Dockplane did not deploy are discovered and read, so applications stay grouped.
Project discovery
Compose projects found on each connected host.
Project membership
Which containers belong to a project, and which do not belong to any.
Project state
Aggregated state across the containers of a project.
Project inspection
Labels and discovered configuration metadata where safely available.
Read-only
A discovered project is not deployed, changed or removed. Taking one over is not part of this release.
05Capabilities
Versions
What a deployment is running, and the one request it makes only if you ask it to.
Component versions
The control server and the browser application report their own release and commit.
Agent versions
What every enrolled agent reports, and the protocol range the server accepts.
Mixed versions
A fleet part-way through a rollout is marked as mixed rather than as broken.
Unknown and unsupported
An agent outside the accepted protocol range is an error; one that reports nothing readable is counted as unknown.
Optional update check
Dockplane can ask the public release listing whether something newer exists. It is off until an administrator turns it on, and nothing acts on the answer.
06Capabilities
Operational context
What happened, what it affected and whether the action you requested actually succeeded.
Normalized events
Operational events in one shape across hosts.
Action history
Requested, authorized, dispatched, succeeded, failed and timed-out actions.
Correlation IDs
A request identifier that ties the interface, API, agent and audit entry together.
Stale-state indicators
Data that is no longer current is marked instead of being presented as live.
07Capabilities
The interface
An operational surface that stays usable at the width it is given.
Tables that fit the window
A full table where everything fits, a compact one that keeps what somebody needs to act, and a stacked list below a tablet width.
What is always in view
What a thing is, which host it belongs to, what state it is in, and the way to act on it — at every width.
Controls that can be hit
Interactive targets sized against WCAG 2.2 AA rather than against a mouse.
08Capabilities
Security and administration
Who may do what, how they prove who they are, and what was recorded about it.
Local user accounts
Accounts with modern password hashing and secure password reset.
MFA and recovery codes
Time-based one-time passwords with recovery codes.
Sessions
Visibility over active sessions, with revocation.
Roles and permissions
Named permission collections enforced by the backend.
Agent enrollment
Short-lived enrollment tokens exchanged for a device-specific identity.
Agent revocation
Individual revocation without replacing credentials across the fleet.
Audit history
Actor, action, target, result and request context for sensitive operations.
09Direction
Planned, not available.
These capabilities are part of the product direction. They are listed separately so the current boundary stays unambiguous.
Images, networks and volumes
Read the resources behind the workloads. Destructive operations stay withheld.
Container metrics
CPU, memory and network usage per workload. Metrics are host-level today.
Host groups
Group hosts for navigation, and scope permissions to a group.
Resource scopes
Permissions that apply to a host, a group or a service rather than everything.
Image update detection
Notice when a newer image is available for a running workload.
Controlled update workflows
Apply an image update as a reviewed, auditable operation.
Backup and restore integration
Coordinate backups around the workloads Dockplane already knows.
Notifications
Route health and action outcomes to an external channel.
Maintenance windows
Suppress alerting and guard operations during planned work.
Safe runbooks
Repeatable operational procedures built from existing capabilities.
Service-level health
Health rolled up to the application rather than the container.
10Boundary
What Dockplane does not do.
Dockplane manages Docker across hosts. Broadening it into a general infrastructure suite would weaken both the security model and the product.
- Proxmox management
- Kubernetes management
- VM lifecycle management
- Pterodactyl panels
- General SSH fleet management
- Arbitrary shell orchestration
- Network-device management
- Generic cloud control plane functionality
Bring your Docker hosts together.
Deploy Dockplane and manage your Docker environment from one self-hosted control plane.