One command. Full control of the cluster.
The admin panel Docker Swarm never shipped with: live console, GitOps deploys, SSO and audit logs, running from one binary next to the cluster. Every node in one place, no SSH-hopping.
Snapshotted from a running instance.
Nine real pages pulled from a live swarmdash cluster. The nav inside actually switches between them.
A real cluster, snapshotted — not a live connection. Buttons like Delete or Scale are inert here; they work for real once it's running on yours.
Nothing here is a paid add-on.
One admin. Agents everywhere.
admin runs once, on a manager node, and talks to a thin agent running
on every node — no overlay network or extra infrastructure to stand up.
Nothing about your cluster is behind a tier.
SSO, RBAC, GitOps and audit logs aren't a Business Edition — they're just what swarmdash does, on every node.
Open source. Audit it yourself.
swarmdash is Apache-2.0 licensed and the full source is public — nothing about how it authenticates, stores data or talks to your nodes has to be taken on faith.
Every request handler, auth check and Docker API call is public on GitHub — nothing runs on your cluster that you can't read first.
admin and agent run on your own nodes; nothing about your services or cluster state is sent anywhere else.
A random SWARMDASH_CLUSTER_SECRET you generate authenticates every admin↔agent call — there's no default or shared secret to leak.
The admin password is generated on first boot and printed once to the container logs — never a default shipped in the image.
Enabled on every response by default — not opt-in middleware you have to remember to turn on.
Every mutating action is recorded — who, what, when, success or failure — so a compromised session is visible, not silent.
docker stack deploy. That's the whole install.
One image for admin and agent.
The only dependency.
Runs once and serves the panel.
A global service, joins on its own.
Admin password is generated on first boot and printed once — grab it with
docker service logs -f swarmdash_admin.
Got a question? Just ask.
One Telegram chat for everything — it goes straight to the people building swarmdash.
Setup, configuration, whether swarmdash fits your cluster — ask before you install or after.
Missing something you need every day? Tell us what and why — that's what shapes the roadmap.
Something broke? Send what you did, what happened, and your swarmdash version.
Bring it to your cluster.
No Kubernetes-shaped detour, no four-service stack to babysit, nothing on your cluster you can't reach.