Arcane vs Dockhand: Which Docker Manager Should You Choose?
Arcane vs Dockhand compared for 2026: licensing, security, auto-updates, and pricing. Find out which Docker management UI fits your homelab or VPS best.
Updated Published 32 min read

Disclosure: this guide contains referral links. If you buy through them, I may earn a commission at no extra cost to you.
Managing Docker containers doesn’t have to mean Portainer. For years, Portainer was the only serious web UI for Docker, and it worked fine until the licensing changes started pushing people toward paid tiers for basic features. That opened the door for alternatives, and two of them have been getting real attention: Arcane and Dockhand.
I deployed both on the same VPS running a mix of compose stacks, and I still run Arcane on my own servers. This Arcane vs Dockhand comparison comes from running them, not from reading feature lists.
Re-checked 2026-10-26
This Arcane vs Dockhand comparison was re-checked on 2026-10-26. Four things moved since the last pass: Arcane now ships native Podman support and a full Swarm management workspace, Dockhand added passkey sign-in, Dockhand’s BSL license switched to a per-version Apache 2.0 conversion, and one claim needed correcting. An earlier version said Arcane phones nothing home. That was wrong. It sends a minimal version heartbeat to checkin.getarcane.app with {version, instance_id, server_type}. No user data, but it is a phone-home. Turn it off with ANALYTICS_DISABLED=true. Dockhand still advertises zero telemetry.
Versions in this article: Arcane v2.17.1 (2026-10-25) and Dockhand v1.0.55 (2026-10-23). Numbers below were pulled from GitHub and the official docs on 2026-10-26.
Quick comparison
How the two Docker management UIs stack up at a glance.
| Arcane | Dockhand | |
|---|---|---|
| License | BSD-3-Clause (fully open source) | BSL 1.1 (per-version conversion to Apache 2.0, four years after each release) |
| Backend | Go | Bun + SvelteKit |
| Frontend | SvelteKit / TypeScript | SvelteKit 2 / Svelte 5 |
| GitHub stars | 8,082 | 6,881 |
| Repo created | April 2025 | December 2025 |
| Contributors | 95 | 46 |
| Commits | ~4,183 | ~732 |
| Releases | 110 (latest v2.17.1) | 42 (latest v1.0.55) |
| Pricing | Free, always | Free (homelab), SMB $499/host/yr, Enterprise $1,499/host/yr |
| GitOps | Built-in | Git integration + webhooks |
| Vuln scanning | Trivy (since v2.12.0) | Grype/Trivy, safe-pull before swap |
| Auto-updates | Tag-based + scheduled, delay knob (v2.17.0) | Scheduled with rollback, minimum image age (v1.0.52) |
| Backups | Rustic encrypted snapshots: local + S3, scheduled volume + system backups | restic + SFTP, retention policies |
| SSO / auth | OIDC + passkeys + MFA (free) | OIDC + passkeys + MFA (free) |
| RBAC | Access control built in | Enterprise tier |
| Swarm | Full management | None |
| Podman | Native since v2.17.0 | Quadlet fixes only |
| Telemetry | Version heartbeat, opt-out | None |
| i18n | English | 5 languages since v1.0.54 |
| CLI tool | Yes | No |
| Multi-env agent | arcane-agent | Hawser (NAT traversal) |
Architecture
These two took very different paths under the hood.
Arcane
Arcane is written in Go. That matters because Go compiles to a single binary, so the whole thing runs lean. Memory footprint is small. The backend handles API requests, container management, and serves the SvelteKit frontend.
There’s a REST API you can hit directly, which is handy for scripting. Arcane also ships a CLI tool for people who want terminal access alongside the web UI.
For managing remote hosts, there are arcane-agent binaries for linux and darwin across amd64, arm64, armv7, and even riscv64. Agents connect back over an edge tunnel signed with ML-DSA-87 keys, and they can self-upgrade. The tunnel was redesigned in v2.16.0 to multiplex traffic over a single connection, which helps when you have a lot of agents.
Dockhand
Dockhand runs on Bun (not Node) with SvelteKit handling both the API routes and the frontend. The database is SQLite by default, with PostgreSQL 14+ as an option via DATABASE_URL if you need multi-replica.
What’s unusual is the OS layer. Dockhand builds its container image from scratch using Wolfi packages via apko. No base image with leftover packages you don’t need. The attack surface is smaller because of this.
For remote hosts, there’s Hawser. It lives in its own repo now (Finsys/hawser, Go) and handles NAT traversal. In Edge mode it dials out over a WebSocket, so a remote machine behind a firewall or carrier-grade NAT still connects without opening inbound ports. Standard mode listens directly and refuses to bind non-loopback without a TOKEN set, which is the right default.
My take on architecture
Both dashboards, for reference:


In my February 2026 testing, Arcane’s Go backend felt snappier for basic container operations. Page loads were fast, API responses came back quickly. Dockhand’s Bun-based stack was no slouch either, but I could feel the difference when clicking through lots of containers. The gap was marginal, and both were faster than Portainer. I have not re-run that head-to-head against v2.17.1 and v1.0.55, so treat it as a dated observation, not a current benchmark.
Licensing
If you want an open source Docker manager with no strings attached, the license is where these two split hard.
Licensing matters
Arcane is BSD-3-Clause. Fork it, modify it, use it commercially, sell it. No restrictions beyond keeping the copyright notice.
Dockhand uses BSL 1.1. The license was rewritten in September 2026. The Change Date is now per-version: each released version becomes Apache 2.0 four years after that version’s first public distribution. Early versions land around December 2029, later versions later. Free use covers dev, test, staging, and CI/CD, including inside companies. Production use by a business needs a paid license. Offering Dockhand as a hosted service needs a written agreement.
For most self-hosters, both licenses work fine. You’re running it on your own hardware for your own use. The BSL restriction only kicks in when you move it into business production or try to resell it.
If you’re building something on top of a Docker management UI, or you want to embed it in a product, Arcane gives you more freedom. If a small business runs production workloads through Dockhand, budget for the paid license.
Features: where each Docker container manager wins
Container and compose management
Both handle the basics well. You can start, stop, restart, and remove containers. You can view logs, inspect settings, and manage networks and volumes. Compose stack management works in both: deploy, update, and edit compose files from the web UI, and both can generate a compose file from a running container. Arcane calls it “Convert to Compose”, Dockhand calls it “Generate compose”.
Where Arcane does it better
- The REST API is well-documented and easy to script against
- CLI tool gives you terminal access to everything the UI does
- GitOps is built in, not bolted on. Point it at a git repo and it syncs your stacks automatically
- “Back up to Git” mode syncs stack state to a repo
- Full Swarm management workspace: initialize, join, leave, and unlock a Swarm, rotate join tokens, manage stacks, services, and tasks with scaling and rollbacks, plus configs and secrets. Node agents get an “Easy Join” flow
- Registry browsing since v2.15.0: walk repos and tags in your configured registries without leaving the UI
- Official mobile app in beta on both iOS (TestFlight) and Android (Google Play), with push notifications
Where Dockhand does it better
- File browser inside containers. Browse the filesystem without exec-ing in
- Scheduled auto-updates with safe-pull protection (pulls new image, scans it, rolls back if it fails)
- Scheduled container start/stop since v1.0.55
- Compose Validate linter runs advisory preflight checks before you deploy. It never blocks a deploy
- Notifications via SMTP and Apprise, plus MQTT, Zabbix, Pushover, and Teams
docker loadsupport for air-gapped hosts- Prometheus
/metricsendpoint for external monitoring (EXPORT_METRICS=truesince v1.0.37) - UI translations: German, Simplified Chinese, French (FR/CA), and Polish since v1.0.54
tag.transformandlink.templatelabels for nonstandard tag schemes like-lsNNNor-rN
Security features
This used to be the easy part of the comparison: Dockhand had scanning, Arcane didn’t. That changed in v2.12.0. Arcane added Trivy scanning in the UI with per-image CVE counts, a “Fix available” filter, and CSV export. v2.10.0 added Copacetic image patching for OS-level CVEs, and v2.14.0 redesigned the security view around risk scoring with bulk ignore and restore for findings. Both tools do docker security scanning now.
What still separates them:
- Dockhand scans before it swaps an image during auto-updates, with rollback if the new container fails. Arcane’s tag-based updates don’t gate on a scan result. Both now support waiting before an update though: Arcane added an update delay knob in v2.17.0, Dockhand added minimum image age in v1.0.52
- Dockhand plugs into external secret managers: 1Password, HashiCorp Vault, Infisical, Doppler, Bitwarden, Proton Pass, KeePassXC, Azure Key Vault, plus Psono (v1.0.54) and SOPS with age (v1.0.55)
- Dockhand’s custom Wolfi-based OS layer means fewer packages, fewer CVEs, and it exports findings as SARIF
- Arcane signs sessions, OIDC flows, and edge mTLS with ML-DSA-87, which is post-quantum crypto. Unusual for this category
- Passkeys and MFA are free on both now (Dockhand added passkeys in v1.0.52). LDAP and RBAC remain Dockhand Enterprise
- Dockhand ships with zero telemetry. Arcane sends a minimal version heartbeat to
checkin.getarcane.appwith{version, instance_id, server_type}. Disable it withANALYTICS_DISABLED=true
These UIs are themselves attack surface. Dockhand v1.0.45 shipped as an “important security upgrade” with API hardenings. Whichever you pick, keep it updated. Pin your image tags and read release notes before upgrading. Dockhand v1.0.52 changed PUID handling in a way that could alter stack file ownership on upgrade. It was reverted in v1.0.53 a day later. That is exactly the kind of rough edge that pinning protects you from. For the rest of the hardening, see how I secured my Docker server after the BSI security report.
For a homelab, the security gap between these two is now small. For a small business running production workloads, Dockhand’s scan-before-swap and secrets integration are still worth the trade-off of a more restrictive license.
GitOps and automation
Arcane's approach
GitOps is a first-class feature. You connect a git repository, and Arcane watches it for changes. When you push an updated compose file, Arcane pulls it and redeploys. There are lifecycle hooks for running tasks around deploys.
This works well if your workflow is already git-based: push a change and it deploys.
Dockhand's approach
Git integration exists but works differently. You connect repos and set up webhooks. When a push happens, Dockhand receives the webhook and acts on it.
The scheduled auto-update feature is separate and arguably more practical for most people. Set a schedule, and Dockhand checks for new images, scans them, pulls them, verifies they work, and rolls back if something breaks. I’ve had it catch a bad image update twice already. Since v1.0.52 you can set a minimum image age so nothing gets pulled the moment it is published, and tag.transform labels handle repos that bump versions with -lsNNN or -rN suffixes instead of proper semver tags.
If you want scheduled Docker auto-updates without either UI, Docker auto-update with Tugtainer covers the standalone route.
Multi-environment management and Podman
Both let you manage containers on remote hosts, but the mechanisms differ.
Arcane uses arcane-agent, a lightweight binary you install on a remote machine. It connects back to your main instance over an mTLS edge tunnel (multiplexed since v2.16.0) and can upgrade itself. If you followed my older guides, this is what used to be called arcane-headless.
Dockhand uses Hawser, and its main advantage is NAT traversal. If your remote machine is behind a firewall or NAT, Hawser Edge mode dials out over a WebSocket and still connects without opening ports. That is useful when machines sit in different networks.
The biggest change since the last pass is Podman. Arcane v2.17.0 added native Podman support, documented as a full section: run Arcane on Podman itself, manage pods, work with quadlets, generate Kubernetes YAML, use Podman secrets, and use Podman’s own auto-update mechanism. Dockhand has Podman and Quadlet update fixes, but no equivalent management story. If your fleet is Podman-based, this narrows the field fast. For the engine-level trade-offs, see our Podman vs Docker comparison.
Maturity and stability
Maturity numbers drift, and the two projects are on different clocks.
| Metric | Arcane | Dockhand |
|---|---|---|
| Repo created | April 2025 | December 2025 |
| Total commits | ~4,183 | ~732 |
| Releases | 110 | 42 |
| Contributors | 95 | 46 |
| Current version | v2.17.1 | v1.0.55 |
Two things stand out. First, the old hedge about Arcane’s history can be dropped: GitHub now 301-redirects ofkm/arcane to getarcaneapp/arcane, the same repository (id 968905557) created 2025-04-19. April 2025 is the true origin. Second, Dockhand’s commit count grew roughly 55% in the month between my two checks. Both projects ship weekly. Arcane has just had more runway.
Open issues and PRs sit at 14 for Arcane and 368 for Dockhand. Don’t read that as “Dockhand has 368 bugs”. Dockhand’s tracker is used more like a forum; Arcane’s team closes things out faster. It is a workflow difference, not a quality signal.
Stability in practice
In my original three-week test back in February, Arcane didn’t crash once and Dockhand froze its UI once after a bulk container restart. Seven months and thirty-plus Dockhand releases later, that kind of rough edge is less representative. Arcane has been boring on my production servers since then, which is what you want.
Pricing
This is the free docker management angle, and the two projects answer it very differently.
Arcane is free. There are no tiers and no paid features. Nothing gets stripped out for a “community edition”. BSD-3-Clause means you get everything. Their homepage says “Always free. Forever. Never changing.”
Dockhand has a tiered model (pricing checked 2026-10-26):
| Tier | Cost | What you get |
|---|---|---|
| Free | $0 | Full features for homelab, personal, non-profit, and education use. OIDC/SSO, MFA, passkeys, scanning, backups, and external secrets included |
| SMB | $499/host/year | Commercial production use, commercial support, priority updates |
| Enterprise | $1,499/host/year | RBAC, LDAP/AD, compliance audit logging, dedicated support |
The free tier is usable and wider than it used to be. OIDC/SSO, MFA, passkeys, vulnerability scanning, restic backups, and the secrets-manager integrations are all included at $0, which is better than what Portainer offers. But the license is clear about the line: dev, test, staging, and CI/CD inside a company are free, production use by a business is not. If you need RBAC or LDAP, you’re paying Enterprise prices.
Community and support
Arcane has the bigger community. 8,082 stars and 95 contributors versus 6,881 stars and 46 contributors. Both repos were pushed to the day I checked.
Dockhand has picked up an ecosystem on its own: strausmann/mcp-dockhand (64 stars) exposes 130+ API endpoints as MCP tools, raetha/ha-dockhand (48 stars) is a Home Assistant integration, and garanda21/dockhand_ios (38 stars) is an iOS client. None of them are official. When third parties start building against your API, that’s a good sign. Dockhand has also pushed i18n hard (5 languages) and picked up coverage from The New Stack, XDA Developers, and VirtualizationHowto.
On Arcane’s side, getarcane.app now has a public demo instance and an “Instance Generator” if you want to try before you deploy. That lowers the commitment cost for anyone on the fence.
Both have active Discord and GitHub channels. Response times have been reasonable from both teams in my experience.
Installation
Both are Docker-based installs, which is appropriate for Docker management tools. This is the operator path: what you need, what to run, how to verify, and what breaks.
What you need before you start:
- A Linux VPS or homelab box with Docker Engine and Compose v2. Any modern Docker host works; I run mine on a €4-5/mo VPS
- Free ports: 3552 for Arcane or 3000 for Dockhand (the
PORTenv var overrides it) - Optional but recommended: a reverse proxy (Caddy, Traefik) for TLS, and a socket proxy (
tecnativa/docker-socket-proxy) instead of raw socket access - A box to run it on. If you need one, I run my Docker hosts on Hetzner Cloud. The CX22/CX32 class handles both UIs easily, in the €4-10/mo range
Arcane
For the arcane docker install path, here is the compose file. The full Arcane Docker install guide covers socket proxy and OIDC setup if you want those.
Create a compose.yaml:
services:
arcane:
image: ghcr.io/getarcaneapp/manager:latest
container_name: arcane
ports:
- "3552:3552"
volumes:
- /var/run/docker.sock:/var/run/docker.sock
- arcane-data:/app/data
- /opt/docker:/opt/docker
environment:
- APP_URL=http://localhost:3552
- PUID=1000
- PGID=1000
- ENCRYPTION_KEY=<your-encryption-key>
- PROJECTS_DIRECTORY=/opt/docker
cgroup: host
restart: unless-stopped
volumes:
arcane-data:Generate the key with either of these:
openssl rand -hex 32
# or
docker run --rm ghcr.io/getarcaneapp/manager:latest /app/arcane generate secretThen docker compose up -d and open http://<host>:3552. Default login is arcane / arcane-admin, and you’ll be forced to change the password on first login. PUID/PGID default to 65532:65532 if you omit them. There’s also an official install script on getarcane.app and an LXC doc if you’re on Proxmox.
Two things that changed and will bite old configs: the image moved from getarcaneapp/arcane to getarcaneapp/manager, and JWT_SECRET is gone. Session tokens are now signed with an ML-DSA-87 key Arcane generates itself, so if you still have JWT_SECRET set, remove it.
One thing to watch: if you want Arcane to manage existing compose projects, mount the projects folder with matching paths inside and outside the container and set PROJECTS_DIRECTORY=/opt/docker. The path must be absolute. Relative paths in compose files break otherwise.
Verify it worked: after docker compose up -d, open http://<host>:3552, complete the forced password change, and confirm the dashboard shows the local engine. Then deploy a throwaway nginx:alpine stack from the UI. If the container appears in the Containers list, the socket wiring is good.
What broken looks like:
- Relative
PROJECTS_DIRECTORYor a missing matching volume mount: projects are invisible in the UI - Wrong-length
ENCRYPTION_KEY: the container starts but secrets and stored credentials fail to decrypt - Leftover
JWT_SECRETin an old env file: harmless in current releases, confusing to read later. Remove it - Port 3552 already bound:
docker compose up -dfails withport is already allocated. Find the offender withss -tlnp | grep 3552
For production, pin the tag (ghcr.io/getarcaneapp/manager:v2.17.1) instead of :latest.
Dockhand
For the dockhand docker install path, the full Dockhand Docker install guide covers PostgreSQL and scanning. The short version:
services:
dockhand:
image: fnsys/dockhand:v1.0.55
ports:
- "3000:3000"
volumes:
- /var/run/docker.sock:/var/run/docker.sock
- dockhand_data:/app/data
restart: unless-stopped
volumes:
dockhand_data:All environment variables are optional in current releases. Credential encryption uses an ENCRYPTION_KEY (base64 AES-256) that is auto-generated into a key file if you don’t set one. Set it yourself if you want to manage it; there’s a documented migration path from key file to env var. Older guides mention a SECRET_KEY variable. Current releases don’t need it, so drop it from your compose files.
Production knobs worth knowing about: PUID/PGID (recommended), HTTPS_MODE=on for native TLS with your own cert (since v1.0.33, no HTTP+HTTPS in parallel), COOKIE_SECURE, EXPORT_METRICS=true for a Prometheus endpoint, and OIDC auto-redirect (since v1.0.50). SQLite is the default database. For multi-replica, point DATABASE_URL at PostgreSQL 14+.
First-run setup walks you through creating an admin account. Pin the version tag rather than running :latest.
Verify it worked: after docker compose up -d, open http://<host>:3000, create the admin account, and confirm the host shows up in the dashboard. Deploy the same throwaway nginx:alpine stack. If you want metrics, set EXPORT_METRICS=true and check curl -s localhost:3000/metrics.
What broken looks like:
- Stale
SECRET_KEYin your env from old guides: current releases ignore it. Harmless but confusing. Remove it - Setting
PUID/PGIDwithout chowning the data directory first: permission denied on/app/data. Runchown -R 1000:1000on the volume path before the first start EXPORT_METRICS_PUBLIC=true: exposes metrics with no auth. Fine on localhost, never behind a public proxy
Pin your image tags
Both tools hold your Docker socket. A broken manager upgrade is an outage. Pin tags, read release notes, and back up each tool’s data volume before you bump the version. Arcane has built-in system backups with restore; Dockhand has restic and SFTP backups. Use them.
Both require access to the Docker socket, which is standard for these tools. If that makes you uncomfortable, the better answer than a raw socket mount is a socket proxy in front of it. My Arcane install guide shows the tecnativa/docker-socket-proxy setup, and the same pattern applies to Dockhand or anything else that manages Docker.
Which Docker manager should you pick?
The gaps narrowed, but the split is still real. The best Docker manager for you in 2026 comes down to which list you land in.
Pick Arcane if...
- You want something truly open source with no licensing concerns
- GitOps is part of your workflow
- You need a REST API or CLI tool
- Your hosts run Podman (native support since v2.17.0)
- You want full Swarm management from the UI
- You want OpenTelemetry export (v2.16.0) into an observability stack you already run
- You want the mobile app (iOS TestFlight and Android beta)
- Budget is zero, including for access control and support
- You want the fastest release cadence in this category (110 releases since April 2025)
Pick Dockhand if...
- Scan-before-swap auto-updates with rollback are a hard requirement
- You manage hosts behind NATs and firewalls (Hawser Edge mode)
- You already keep secrets in 1Password, Vault, Psono, SOPS, or similar
- You need the UI in German, Simplified Chinese, French, or Polish
- Scheduled container start/stop matters to your workflow
- You want restic backups to SFTP destinations with retention policies
- You want the hardened Wolfi-based image and SARIF exports
- You need LDAP/AD and are fine paying Enterprise prices for it
- You’re okay with BSL 1.1 per-version terms and a younger codebase
Both run happily on a budget mini PC. An ASUS DC510 mini PC or any of the best home server mini PCs handles both without breaking a sweat. Once you’ve picked a manager, the best Docker containers for a home server covers what to run on it.
My honest take
My answer has moved since February. When I first compared these two, Dockhand’s security tooling was the reason to pick it, because Arcane didn’t scan at all. Now Arcane scans, patches with Copacetic, backs up to S3 with Rustic, updates containers on tags, runs on Podman, manages full Swarm clusters, exports OpenTelemetry, and ships a mobile app on both platforms. All while staying BSD-3-Clause and cutting a release roughly every week. As a Portainer alternative, it has closed most of the reasons to look elsewhere.
Arcane is still my default, and it’s what runs on my own servers. The case for Dockhand narrowed to the things Arcane doesn’t do: scan-before-swap rollbacks, external secret managers (including SOPS and Psono now), i18n, SFTP backups, NAT traversal via Hawser, and LDAP if you pay. If any of those are hard requirements, Dockhand earns its license terms. If they’re not, Arcane is the easier recommendation.
One flip side worth stating plainly, since I got it wrong before: Arcane’s version heartbeat is a phone-home. It’s small, documented, and opt-out with ANALYTICS_DISABLED=true, but Dockhand sends nothing at all. If that matters to you, the choice is easy.
And if you’re still shopping, the full Portainer alternatives comparison covers Sencho, Dockge, Komodo, and the rest of the field.
Related articles
- Best Portainer alternatives in 2026 - the full Docker management UI comparison
- Install Arcane - full Arcane setup guide with socket proxy and OIDC
- Install Dockhand - full Dockhand setup guide with vulnerability scanning and Hawser
- Install Dockge - another Docker management UI worth trying
- Best Docker containers for home server - what to run once you’ve picked a manager
- Best self-hosted panels - server management panels compared
- Podman vs Docker - the container engine comparison
- Docker auto-update with Tugtainer - keep containers updated automatically
- Server monitoring tools - monitoring your Docker host
Did this guide work for you?
Need help with Astro, VPS, or a self-hosted app? View services →


