Self-hosted Docker operations, built for safe changes.

See what a deploy will change, check it against your rules, keep every revision, and roll back when something goes wrong.

docker-commander.app · Documentation · Releases · Sponsor

---

Why Docker Commander?

• Safe changes. Preview a deploy, check it against policy rules, keep every revision and restore a known-good one.
• One binary. The web UI is embedded, there is no external database and no runtime dependency. Linux, macOS and Windows.
• Many hosts. Local, TCP+TLS and SSH daemons from one place, with alerts watching all of them.
• See what happens. Live and historical CPU, memory and network, logs, events, disk usage and alerts that tell you when something breaks.
• AI access without a shell. An optional MCP server lets AI tools read and safely operate Docker as you, within your permissions.

📸 Screenshots

Dashboard: host overview, disk usage, and running containers at a glance.

Deploy preview: before a deploy, every service that would change and why — image, digest, ports, env — and which containers it would recreate.

Deploy history: every deploy is a revision you can diff against what runs now, and restore.

Container detail: live CPU and memory with history, and tabs for logs, an interactive console, processes, the file browser, filesystem changes and env.

Aggregated logs: many containers in one stream, color-coded by source, with level filters, regex search and structured parsing.

More screenshots are on each page of the manual.

✨ Features

Safe changes

• Projects: Compose folders edited in the browser, with live validation. Deploy to any host. Projects
• Deploy Preview: see per service what a deploy changes and what gets recreated. Projects
• Drift detection: compare the files with what actually runs; ignore or reconcile. Projects
• Revisions and rollback: every deploy is kept, with its image digests. Restore one. Projects
• Policy rules: seven checks (privileged, host network, socket mounts, :latest…), each off, warn or block. Policy rules
• Project secrets: encrypted at rest, write-only, masked everywhere they would show. Projects
• Image updates: an alert when a newer image is behind a running tag. Alerts

Operate

• Containers: run, start/stop/restart, limits, console, file browser, commit, bulk actions. Containers
• Stacks: every Compose project on a host, CLI-started ones too; edit and redeploy in place. Stacks
• Images, volumes, networks: pull, build, push, scan with Trivy; browse volume files; connect networks. Images
• Domains and reverse proxy: route a domain to a project's service, with Let's Encrypt certificates. Projects
• Backup jobs: run your own backup command (restic, borg…) against volumes, with history. Backup jobs
• Recovery bundle: move projects, hosts, registries and rules to another instance. Recovery

Observe and alert

• Dashboard and Resources: CPU, memory, network and disk per container and stack, top talkers. Resources
• Logs and events: many containers in one stream, regex search, parsing rules. Logs
• Alerts: state, resource, network, log and crash-loop rules; webhooks, e-mail, Prometheus. Alerts
• Maintenance windows: silence delivery during planned work; deploys silence themselves. Alerts
• Troubleshooting: subnet overlaps, MTU, duplicate ports, log rotation, disk space. Troubleshooting

Hosts and access

• Multi-host: local, TCP+TLS and SSH daemons, with SSH host-key verification. Hosts
• Users and roles: per-section permissions, read-only accounts, optional LDAP. Users & roles
• Sign-in: passwords with TOTP or passkeys, revocable sessions, audit log. Your profile
• HTTPS: your own certificate, a self-signed one, or Let's Encrypt. Deployment
• Behind a reverse proxy: at the root of a (sub)domain or under a path such as /dockercmd/. Deployment
• Self-update: one click, or opt-in automatic updates within a version range. Settings

AI tools (MCP)

• Optional and off by default: Claude Code, Claude Desktop or Cursor can read and safely operate Docker as you. MCP
• Bounded: your permissions, narrowed per token; changes are rate limited and audited; no exec, file reads or prune.

🚀 Quick start

Binary. Download the file for your OS from Releases and run it:

chmod +x dockercmd-linux-amd64
./dockercmd-linux-amd64           # http://127.0.0.1:8470

Homebrew (macOS and Linux):

brew install koduj-dev/tap/dockercmd

Debian / Ubuntu: apt install dockercmd from the signed APT repository; Fedora and others get a .rpm (and .deb) on every release, with the systemd service. Docker: ghcr.io/koduj-dev/docker-commander, multi-arch and non-root; mounting the Docker socket gives it control of the host.

Then open http://127.0.0.1:8470, create the admin account and pair an authenticator.

Installing has every option in full (the Docker command, go install, building from source, running as a service) and how to verify a download's signature. Configuration lists every setting.

🧪 Tested

Alongside ~1200 Go unit tests and ~420 frontend tests, the repo carries 150 adversarial "pentest" cases that assert attacks are rejected, an integration tier against real Docker daemons, and deploys to separate daemons over TCP and SSH. Engine 24 to 29 and recent Compose releases are tested nightly. See How it's tested and Docker versions.

📚 Documentation

• Getting started and Installing
• Manual: one page per screen
• Deployment, Configuration, Security model
• Architecture, How it's tested

🗺️ Roadmap

What's next is in NEXT.md; what shipped is in CHANGELOG.md.

🤝 Contributing

Issues and pull requests are welcome. See CONTRIBUTING.md, the Code of Conduct, and SECURITY.md to report a vulnerability privately.

🤖 Made with AI

Roughly 95 % of this project was built with AI (Claude Code) — code, tests, and docs — under human direction and review. 🎉

📄 License

MIT