Best Portainer Alternatives in 2026 (All Free, Tested)
Looking for Portainer alternatives? We tested Arcane, Dockhand, Dockge, Komodo and Coolify: free Docker UIs with 2026 pricing, stats and a migration plan.
Updated Published 37 min read

Portainer is still the default answer when someone asks for a Docker management UI, and the search for Portainer alternatives keeps growing for one reason: every free path comes with strings. Community Edition is alive and free, but SSO, RBAC, audit logs, and registry management sit behind Business Edition. The free Business tiers (3 Nodes Free, the old 5 Nodes Free) bring annual renewal paperwork and commercial-use clauses. Paid starts at $155/yr, and that tier is non-commercial only.
I run Docker across VPS and homelab machines, and I use Arcane on my own servers for day-to-day management and deploys. For this update I re-tested the field: which free Portainer alternative matches how you work, what Portainer licensing costs a solo operator in 2026, and how to move your stacks off Portainer with a rollback plan.
- A decision tree so you can self-select in under a minute
- Dated numbers: stars, licenses, last commits, version tags from 2026-10-27
- A Portainer-exit migration path with a real rollback branch
- A security baseline that applies to every Docker management UI on the list
Affiliate Disclosure
Some links in this guide are affiliate links. If you buy through them, we may earn a small commission at no extra cost to you. This helps us keep testing and updating these recommendations.
Why people are leaving Portainer in 2026
Portainer CE is not dead. The repo shows 38,729 stars and an active push cadence (last push 2026-10-27), it ships under the Zlib license, and for a single-host homelab with no SSO needs it still works. That is not the problem.
The problem is where the feature line sits. RBAC, OIDC/SSO, registry management, audit logs, HA, and most edge features are Business Edition only (per docs.portainer.io and the CE-vs-BE post on portainer.io). Portainer’s own pitch is blunt: “Most people should install Business Edition. It is free for up to 3 nodes.” So the official funnel sends you to a licensed product, even at zero cost.
What has changed since the last update: CE is dead-ish as a feature project but very much alive as a security-maintenance project. Version 2.45.3 shipped 2026-10-21 explicitly labeled “LTS,” with recent CVE hardening in the 2.45.x line: SSRF hardening in 2.45.1, a bind-mount-hide bypass fix in 2.45.2, and a breaking cert-trust change in 2.45.3 (more on that in the security baseline). If you run CE today, you get patches. You do not get new features.
The licensing timeline is what pushed people to look for Portainer alternatives in the first place:
- 2024-07-10: the 5 Nodes Free (5NF) license changed at renewal. Home users kept it; business use was pushed to paid. The blog post from that date is still the reference.
- 3 Nodes Free (3NF): free forever up to 3 nodes, but you renew annually. Portainer emails a new key 14 days before expiry (per portainer.io/renew-3-nodes-free-license-key, fetched 2026-10-27).
- Home & Student: $155/yr, up to 15 nodes, strictly non-commercial. The pricing page says license keys will be revoked for any business use, any company size.
- Starter: from $1,045/yr, billed annually, 5/10/15 nodes, capped at 16 vCPUs per node, community support.
- Scale: from $2,095/yr, billed annually, 5-25 nodes, 24 vCPUs per node, 9x5 NBD support.
Community pain points line up with that. In r/selfhosted threads people call out the stagnant mobile UI, an API that falls behind what automation needs, and the missing volume/stack backups in CE. There is also a specific fear: leaving Portainer should not mean locking your stacks in yet another proprietary database.
The Home & Student trap
The $155/yr Home & Student tier is strictly non-commercial. The pricing page states license keys will be revoked for any business use. If you run an LLC, invoice consulting clients, or host anything that makes money, do not buy it. The floor for commercial use is Starter at $1,045/yr as of 2026-10-27.
Portainer pricing in 2026: the licensing math for solo operators
The honest annual comparison for 2026:
| Path | Cost per year | What you accept |
|---|---|---|
| Portainer CE | $0 | No SSO/OIDC, no RBAC, no audit logs, no HA, limited edge |
| Portainer BE 3 Nodes Free | $0 | Annual renewal paperwork, max 3 nodes |
| Portainer Home & Student | $155/yr | Non-commercial only, revocation clause |
| Portainer Starter | from $1,045/yr | 5/10/15 nodes, 16 vCPUs/node cap |
| Portainer Scale | from $2,095/yr | 5-25 nodes, 24 vCPUs/node cap |
| Arcane, Sencho, Dockge, Komodo, Coolify, Dokploy, lazydocker, Dozzle, 1Panel | $0 | Your own ops and backups |
| Dockhand | $0 for personal and internal business use | BSL 1.1, not OSI open source |
The dollars are only half of it. The real cost of the Portainer free paths is friction and revocation risk: a renewal you must remember, a node count you must not exceed (“we reserve the right to limit some or all of the product capability should the node count be exceeded” is the exact wording on the renewal page), and a home license that evaporates the moment you invoice anyone.
Rule of thumb I use: if you invoice anyone, Home & Student is not for you. If you need SSO today and do not want to pay, Portainer CE is not for you.
3 Nodes Free renewal mechanics
3NF renews free, but you must renew every year. Portainer says it sends the replacement key 14 days before your current key expires, and the form has spam-filter quirks (gibberish names get stuck). The separate “7 days” rule on that page is about moving a key to a different instance during a server move, not about the renewal window. What exactly happens if a key lapses (lockout vs. feature downgrade) is not clearly documented
How this update was tested (October 2026)
Numbers in this article come from GitHub API pulls on 2026-10-27, release pages read the same day, and portainer.io pricing fetched 2026-10-27. Hands-on claims mean a real install on a throwaway €4-5/mo Hetzner CX-class VPS, not my production fleet. Twelve tools compared, seven covered in depth.
VPS prices jumped across the board in 2026. If you’re rethinking a rented box, see what changed and when a mini PC wins.
The previous version of this article made two wrong claims about Arcane: that it had no vulnerability scanning and no auto-updates. Both are wrong as of September 2026. And we missed Komodo v2.0.0 entirely.
Corrections vs the previous version
Komodo shipped v2.0.0 in March 2026 and we missed it. This version adds Swarm support, outbound Periphery, and deprecates :latest. Fixed throughout this piece. Also: Arcane now has Trivy vulnerability scanning in the UI (v2.12.0, 2026-09-16), Copacetic image patching and scheduled backups (v2.10.0, 2026-08-31), and S3 backups (v2.9.0, 2026-08-25). One claim dropped entirely: the “around since 2022” history line, because the current repo was created 2025-04-19 and the pre-rename lineage is unconfirmed.
Where I could not re-verify something before publish, I hedge inline instead of stating it as tested. That applies to a couple of vendor pricing tiers and to Portainer’s exact expiry behavior.
Best free Portainer alternatives at a glance
Decision-first. The table, then the tree, then the reviews.
| Tool | Stars | License | Last commit | Vuln scan | SSO/OIDC | Backups | Multi-host | API | Best for |
|---|---|---|---|---|---|---|---|---|---|
| Arcane | 8,091 | BSD-3-Clause | 2026-10-27 (v2.17.1) | Trivy | OIDC, passkeys | S3, Git | agents | yes | Like-for-like Portainer swap |
| Dockhand | 6,899 | BSL 1.1 | 2026-10-26 (v1.0.55) | Grype/Trivy safe-pull | OIDC, MFA (LDAP paid) | restic | Hawser | OpenAPI | Security-first management |
| Sencho | 497 | AGPL-3.0 | 2026-10-27 (v0.98.1) | Trivy, scan policies | OIDC, TOTP, RBAC | S3 archives | node-link + Pilot | API tokens | Compose fleets with guardrails |
| Dockge | 24,696 | MIT | 2026-04-19 (CI push 2026-10-23) | no | no | files on disk | agents | limited | Pure compose UI |
| Komodo | 12,818 | GPL-3.0 | 2026-10-23 (v2.3.4) | no built-in | OAuth | snapshots | Periphery (outbound) | strong | Multi-server fleets, Swarm, builds |
| Coolify | 65,041 | Apache-2.0 | 2026-10-27 (v4.5.0) | no built-in | teams | yes | multi-server | yes | PaaS with one-click services |
| Dokploy | 38,074 | Apache-2.0 (verify file) | 2026-10-26 (v0.30.10) | no built-in | yes | yes | multi-server | yes | PaaS, Traefik-based |
| lazydocker | 53,213 | MIT | 2026-04-19 | no | n/a | no | no | n/a | Terminal work |
| Dozzle | 14,746 | MIT | 2026-10-27 (v11.3.5) | no | n/a | no | swarm/k8s read | no | Real-time logs |
| 1Panel | 37,290 | GPL-3.0 | 2026-10-27 (v2.4.1) | some | yes | yes | no | yes | Whole-server panel |
| CapRover | 15,194 | Apache-2.0 (verify file) | 2026-10-26 (v1.15.5) | no built-in | yes | no | swarm | yes | Swarm PaaS, one-click apps |
| UsulNet | 133 | AGPL-3.0 | 2026-05-21 | Trivy | business tier | S3/B2/SFTP | NATS | REST + WS | All-in-one, still beta |
Blank or “no built-in” cells mean exactly that. Stars are a community proxy, not a quality score. Last commit is the maintenance pulse; anything over about 90 days gets flagged in its section.
- Pick Arcane for a like-for-like Docker management UI
- Pick Dockhand when security workflow leads: scan-before-swap, LDAP, secret managers
- Pick Sencho for compose-on-disk plus fleet features and free RBAC/SSO (pre-1.0, small community)
- Pick Dockge for pure compose on one host (with the pulse caveat)
- Pick Komodo for a multi-server fleet, Swarm fleets, or builds (NAT-friendly outbound agents)
- Pick Dokploy or Coolify if what you want is a PaaS
- Pick lazydocker, Dozzle, or plain Docker CLI if you did not need a dashboard
What to run it on at home
None of these UIs needs much hardware; the containers they manage do. If you are moving a Portainer host off a VPS or an old laptop, a small mini PC plus a USB disk enclosure (DAS) covers most homelab stacks. For a broader look at quiet, low-power boxes, see the best home server mini PCs guide.
| Piece | Pick | Price (Oct 23, 2026) | Why |
|---|---|---|---|
| Mini PC | Beelink EQ14 | $369 | N150, 16GB, dual 2.5GbE, low idle draw. Runs the UI plus a starter stack |
| DAS | TerraMaster D4-320 | $170.99 | 4 bays over 10Gbps USB-C for media, backups and bulk volumes |
| UPS | CyberPower CP1500PFCLCD | $239.95 | Pure sine, NUT-compatible. A power cut mid-write is how volumes get corrupted. More in the UPS guide |
If you want something even more compact and quieter than the Beelink, the ASUS DC510 mini PC is a solid Thunderbolt-dock-adjacent alternative that sips power and stays silent under load.
Why this instead of a NAS, and when a NAS is the better call: skip the NAS: mini PC + DAS.
All picks are $0 to self-host. Dockhand is free under BSL 1.1 for personal and internal business use. A management UI adds no hosting cost when it runs on a VPS you already pay for; a dedicated small box is about €4-5/mo.
Arcane: the closest like-for-like Docker management UI
Arcane is my default recommendation when someone wants Portainer-shaped features without Portainer licensing, and it is what I run on my own servers. As of 2026-10-27: 8,091 stars, BSD-3-Clause (true OSS), Go backend with a SvelteKit frontend, current release v2.17.1 (2026-10-25). The repo lives at getarcaneapp/arcane now; old ofkm/arcane links redirect.

What you get on the free tier: container/stack/image/network/volume management, OIDC, passkeys and MFA, per-permission API gating, and remote hosts via arcane-agent binaries (linux/darwin across amd64/arm64/armv7/riscv64). Since v2.17.0 there is also native Podman support (rootful and rootless), with example compose files under docker/examples/.
For install, follow our Arcane Docker install guide (with socket proxy setup) instead of copy-pasting from here. That guide already uses the hardened pattern this article recommends: socket proxy in front of docker.sock, reverse proxy with auth in front of the UI.
Socket proxy is the default posture
The Arcane install guide points the container at DOCKER_HOST=tcp://docker-socket-proxy:2375 instead of mounting /var/run/docker.sock. Full allowlist and threat model in the security baseline section below.
One install detail that bites people adopting existing compose projects: the project folder path must match inside and outside the container. If your stacks live at /opt/docker on the host, mount /opt/docker:/opt/docker and set PROJECTS_DIRECTORY=/opt/docker. Mapping that path to something else breaks relative mounts.
What’s new in Arcane 2.x: scanning, patching, backups
The corrections, itemized with release dates from the Arcane releases page (fetched 2026-10-27):
- v2.9.0 (2026-08-25): automated S3 backups, standalone container editing, batched update notifications, CLI coverage for vulnerabilities/activities/webhooks.
- v2.10.0 (2026-08-31): scheduled volume backups, selective system restores, Copacetic (Copa) direct image patching for OS-level CVEs, “Convert to Compose” for running containers, Swarm read access, ML-DSA-87 signing for sessions/OIDC/edge mTLS.
- v2.11.0 (2026-09-12): durable job execution with offline recovery, Docker event streaming, tag-based container updates, label filtering. v2.11.1 added a toggle to disable scans per environment.
- v2.12.0 (2026-09-16): Trivy vulnerability scanning in the UI with CSV export, a “Fix available” filter, per-image CVE counts, Trivy config and ignore-file support. Also “Back up to Git” sync mode and IPv6 network visibility.
- v2.14.0 (2026-09-26): bulk ignore/restore for vulnerability findings, redesigned risk-based security view, improved risk score model, container process visibility.
- v2.15.0 (2026-10-04): registry browsing (repos and tags), mobile table sorting, backup login (recovery codes), unsaved-changes warnings on deploy.
- v2.16.0 (2026-10-13): OpenTelemetry support, redesigned multiplexed edge tunnel, CLI previews and self-update tooling, JSON in container logs, confirm-before-bulk-update guard.
- v2.17.0 (2026-10-21): native Podman support (rootful and rootless), hostname config, and a configurable delay before auto-updating newly available images.
Cadence check: v2.13.1 to v2.17.1 landed in roughly five weeks (2026-09-22 to 2026-10-25), about four releases. That is a healthy release pulse. Dockge below is the contrast.
Two of these features mutate running containers: bulk update and Copa patching. Same rule as any auto-updater. Point them at a canary stack first and snapshot the volume before the first scheduled run. Arcane now ships guard rails for exactly this: confirm-before-bulk-update and a configurable delay before auto-updating new images. That softens the risk but does not replace canary testing. If you want a dedicated updater with rollback as a complement or instead, see how Tugtainer handles Docker auto-updates vs Watchtower.
Dockhand: security-first alternative with scanning and rollbacks
Dockhand is the pick when the security workflow matters more than OSI licensing. As of 2026-10-27: 6,899 stars, TypeScript on Bun, v1.0.55 (2026-10-23), roughly weekly releases.

The security story is concrete:
- safe-pull scans before it swaps: image updates run through Grype/Trivy first, with rollback if the new container fails.
- The maintainer flagged v1.0.45 (2026-08-27) as an “important security upgrade with a number of API hardenings”. A useful reminder that these UIs have CVEs too.
- Secret providers cover 1Password, HashiCorp Vault, Infisical, Doppler, Bitwarden Secrets, Proton Pass, KeePassXC, and Azure Key Vault.
- Auth covers MFA, LDAP, and OIDC/SSO.
- Stack backups are restic-based, with retention and bulk delete. SFTP backups with a dedicated SSH key and verified host keys arrived in v1.0.52.
- A Compose Validate linter runs as preflight before you deploy.
- On the ops side:
docker loadfor air-gapped hosts, notifications to MQTT/Zabbix/Pushover/Teams, OpenAPI docs at/api/docs(opt-in viaFEAT_API_DOCS), the Hawser agent for remote hosts, and Podman compatibility fixes. New since v1.0.48: scheduled container start/stop (v1.0.55), compose-file adoption from container labels (v1.0.52), and redeploy of individual services without recreating the whole stack (v1.0.52).
Image reference straight from the release notes:
docker pull fnsys/dockhand:v1.0.55 # or :latest, but pin in prodThe GitHub repo moved from fnsys/dockhand to Finsys/dockhand (capital F). The old GitHub path 404s as of 2026-10-27. The Docker Hub image is still fnsys/dockhand, so the pull command above has not changed.
For the full walkthrough (SQLite and PostgreSQL backends, OIDC/SSO, Hawser agents), use the Dockhand Docker install walkthrough.
Dockhand is source-available, not open source
Dockhand runs under BSL 1.1. It is free for personal use and internal business use, and it converts to Apache 2.0 in January 2029. If you resell or offer it as a hosted service, read the license first. I say this plainly because roundups often wave “open source” over anything with a public repo. Commercial tier pricing was not re-verified for this article; do not trust old numbers without checking dockhand.pro.
Failure modes to know: safe-pull reduces auto-update risk but does not eliminate it, so snapshot volumes before the first scheduled run. And v1.0.52 introduced a PUID change “that could alter stack file ownership on upgrade,” reverted in v1.0.53. That is exactly why you pin versions and read release notes before updating your manager.
Dockhand vs Arcane: which should you install?
Direct answer, not a feature dump.
Choose Arcane if
- You want a true OSI license (BSD-3-Clause) with no usage strings
- OIDC and passkeys on the free tier cover your auth needs
- You value the fastest release cadence in this category
- Podman support or OpenTelemetry matters to you
- You want the simplest footprint: one Go container and a volume
Choose Dockhand if
- Scan-before-swap with rollback is a hard requirement
- You need LDAP, or you already live in 1Password/Vault/Infisical/Doppler
- restic stack backups with retention beat an external cron job
- You are fine with BSL 1.1 for now and the 2029 conversion date is acceptable
My default is Arcane. Pick Dockhand when scan-before-swap rollbacks, LDAP, or enterprise secret managers are the deciding features. If you are genuinely torn, run both on one box during evaluation on different ports. They can coexist.
Full Arcane vs Dockhand comparisonSencho: Compose control plane with fleet features
Sencho is the newest entry here, and for Compose shops it fills the same slot Portainer does: a single container (saelix/sencho, UI on port 1852) that manages Compose stacks on one machine or a fleet. As of 2026-10-27: 497 stars, AGPL-3.0, TypeScript, still pre-1.0 (latest release v0.98.1, 2026-10-26) with commits landing the same day I checked.
The pitch is compose-on-disk plus a real ops layer. Your files stay the source of truth on the host, and Sencho adds the things Dockge never had: atomic deployments with automatic rollback, a Monaco editor with diff preview and one-click rollback to any prior deploy, health-gated updates, drift detection against running containers, Git-sourced stacks, and a Compose Doctor preflight that catches problems before you deploy. There is even an app store that accepts any Portainer-compatible template registry, with LinuxServer.io templates by default.
- SSO (OIDC plus Google/GitHub/Okta presets), TOTP 2FA, and five-role RBAC on the free tier
- Trivy scanning with VEX suppression, SARIF export, SBOM upload, and scan policies that can block a deploy
- Multi-node without a separate agent: run the same Sencho binary on each host and link them with an API token; the Pilot Agent covers nodes behind NAT through a single outbound WebSocket
- Fleet operations: snapshots of compose and env, secrets push to labeled nodes, bulk actions, remote updates, Blueprints with drift detection
- Scheduled ops on cron, webhooks, auto-heal and auto-update policies, read-only audit log
- Off-site stack archives to S3-compatible storage, notifications to Slack/Discord/generic webhook
- No telemetry and no outbound calls to the vendor
The multi-node model differs from Komodo’s Periphery or Arcane’s agents: every node runs a full Sencho instance and the primary proxies authenticated HTTP/WebSocket to it. No SSH, no Docker socket exposed on the network. For a two or three box setup it is pleasantly simple.
Two caveats. Pre-1.0 means what it says: the repo ships a KNOWN_LIMITATIONS.md and tells you to validate against your own setup before trusting it with critical infrastructure. And the community is small, 497 stars against Arcane’s 8,000 and Dockge’s 24,000. There is a paid “Admiral” plan (hardened builds, managed off-site recovery vault, LDAP/AD, audit export, priority support), but the Community tier is the real product: unlimited nodes, unlimited users, everything above included.
Recent additions worth knowing: v0.98.0 (2026-10-23) added a Blueprint “Needs attention” filter and node labels; v0.98.1 (2026-10-26) added GitOps retry after health-gate failure. Compose Doctor now “recognizes Docker socket proxy topologies”, and Sencho’s preflight plays nice with the hardened pattern this article recommends.
Install note: the same 1:1 path rule as Arcane applies. If stacks live at /opt/docker, mount /opt/docker:/opt/docker and set COMPOSE_DIR=/opt/docker. And like everything else on this list, Sencho mounts /var/run/docker.sock, so read the security baseline section before exposing the UI.
Dockge: still the best pure compose UI, but check the pulse
This is the “Portainer vs Dockge” answer for compose-only users. Dockge has 24,696 stars (the biggest of any Docker Compose UI), MIT license, TypeScript. The design is the selling point: your stacks are plain compose files on disk, with no proprietary database holding your deployments hostage. That is exactly what people fear losing when they leave Portainer.

You point it at a stacks directory with DOCKGE_STACKS_DIR (default /opt/stacks) and it picks up compose.yaml plus .env per folder. See how to install Dockge with Docker Compose for the full setup, including the pin-a-version caveat.
Now the caveat, because I would not hang a fleet on hope.
Dockge maintenance pulse
The last release, 1.5.0, shipped 2025-03-30, about 19 months ago as of 2026-10-27. The last substantive commit was 2026-04-19 (“fixed missed v-html xss warning vulnerability”); the only commit since is a CI change on 2026-10-23 (“ci: drop the self-hosted ARM runners”, #1010). “Is this still developed?” is an open community question (GitHub issue #893, r/selfhosted threads, community forks appearing). Also: Dockge 1.5.0 disabled the Console/terminal feature by default, which I consider the right security call, not a regression. Pin :1.5.x, keep your compose files in Git, and any tool can adopt them later.
Dockge 1.5.x is still the nicest pure compose UI to use on a single host. Set your expectations before betting more than one box on it, and remember multi-host via agents gets clumsy around 8 hosts and 90 containers (a complaint that shows up repeatedly in r/selfhosted). At that size, look at Komodo, Arcane agents, or Sencho’s node-link model.
Komodo: fleet management for multi-server homelabs
Komodo is the multi-server docker management answer: 12,818 stars, GPL-3.0, Rust, current release v2.3.4 (2026-10-22). It builds, deploys, and manages across many servers through Periphery agents, and it has a strong API for automation. If your complaint about Portainer is “the API is falling short,” this is usually where people land.

Komodo v2.0.0 shipped 2026-03-24 and changed the product significantly. The headline additions: Docker Swarm support (manage clusters, nodes, services, stacks, configs, secrets), outbound Periphery (the agent initiates the connection to Core, so NAT’d nodes work without inbound firewall rules), PKI auth between Core and Periphery with auto-rotating keys, passkey/TOTP 2FA, and full interactive OpenAPI docs at demo.komo.do/docs.
It is compose-on-disk friendly, and community migration write-ups exist for exactly this move (FoxxMD’s Portainer/Dockge to Komodo guide is the reference people link in r/selfhosted). I am citing it, not copying it.
Upgrading from Komodo 1.x?
The :latest tag is deprecated in v2. Komodo images ship as :2, so anyone following old install snippets gets v1. Pin :2 and follow the v2 upgrade guide.
Ops reality check before you commit:
- Komodo is stateful. It wants a MongoDB-compatible database: either MongoDB or FerretDB (FerretDB v2 backed by Postgres + the Microsoft DocumentDB extension is the documented alternative; setup docs ship both
mongo.mdxandferretdb.mdx). Budget roughly 300-500 MB extra RAM on top of the core. I do not run Komodo on a 1 GB box by choice. - That database is one more stateful thing to back up. Arcane, Dockhand, Sencho, and Dockge are effectively single-container plus volume shapes; Komodo is not.
- Agent version skew is a real ops task. After a core upgrade, upgrade Periphery agents next, then re-run the fleet check.
Back up the Komodo database
Treat the Komodo DB like production state. Scheduled dumps or volume snapshots, and test a restore once. Losing it does not kill your stacks (the compose files live on the hosts), but you lose inventory, sync state, and API keys.
If you are building a 3-5 node homelab fleet for this kind of tooling, quiet nodes like a compact mini PC such as the GMKtec M5 Ultra beat a tower of old laptops on noise and power draw.
The socket-proxy pattern from our Arcane Docker install guide (with socket proxy setup) applies to Komodo’s Periphery agents too. Do not hand a raw docker.sock to anything with a network listener.
Coolify and Dokploy: when the real answer is a PaaS, not a UI
Category correction. If what you do is “push code, deploy app, get HTTPS”, a self-hosted PaaS is the right shape of tool, not a container management UI. Two serious options:
Coolify
- PHP/Laravel under Apache-2.0, 65,041 stars (2026-10-27).
- Git-push deploys plus 360+ one-click services.
- Built-in reverse proxy with Let’s Encrypt.
- Covers Docker and Docker Compose, with Kubernetes claims in the docs.
- Best for people who want batteries included and a large template catalog. Paid Coolify Cloud exists if you do not want to run the control plane.
Dokploy
- TypeScript, 38,074 stars (2026-10-27), created 2024-04-19 and the fastest star growth in this space.
- Git deploys plus Docker/Compose services, with databases and backups built in.
- Traefik-based routing.
- Best for people who want a leaner PaaS with Traefik under the hood. This is what I run across my own VPS fleet.
License note: the GitHub API reported NOASSERTION for the Dokploy repo on 2026-10-27; Coolify reports Apache-2.0. Check the license file in the repo before you make a legal call.
A self-hosted PaaS means you own urgent patching
Coolify v4.4.7 (2026-10-21) shipped with the note “fixes multiple critical CVEs in dependencies… Update immediately.” If you run an older line (v4.0-v4.3), the patch script is curl -fsSL https://cdn.coollabs.io/coolify/patch.sh | sudo bash. This is the ops cost of self-hosting a PaaS: when a CVE drops, you are the one patching on a Sunday night, not a vendor.
Both replace Portainer-style deploy workflows, not the low-level Docker poking. Keep lazydocker or the Docker CLI on the box for the 3 a.m. work. And plan for weight: a PaaS adds Traefik plus build workers, so 2 GB RAM is a realistic floor.
Step-by-step Dokploy install guideIf you cannot choose between the PaaS options, Coolify vs Dokploy vs Kamal 2 compared walks the tradeoffs properly. For a hands-on setup, see the Coolify install guide or how to deploy a Docker Compose app in Dokploy.
No dashboard needed: lazydocker, Dozzle and plain Docker CLI
The honest baseline, and the section most roundups skip. Before adopting any Docker management UI, try two weeks of terminal work. Many people do not go back.
- lazydocker (53,213 stars, MIT, Go TUI, last push 2026-04-19): containers, logs, and stats in your terminal. Zero server footprint, nothing listening on a port, nothing to patch on the VPS. Dormant for 6+ months, but stable: v0.25.2 still works fine.
- Dozzle (14,746 stars, MIT, Go, v11.3.5 from 2026-10-24, active): a real-time log viewer in the browser for Docker, Swarm, and Kubernetes. Tiny and single-purpose.
- Plain Docker CLI + compose: covers the majority of what people open Portainer for. Honorable mention for the VS Code Docker extension over SSH.
docker compose psanddocker compose up -dfor state and restartsdocker compose logs -f –tail=100for tailsdocker compose pull && docker compose up -dfor updatesdocker statsanddocker system dffor resourcesdocker compose execfor shell accessdocker system prunefor cleanup (read the flags first)
Cost is zero and the attack surface does not grow. Nothing runs on the VPS to patch. That is a better default than most people admit.
1Panel, CapRover, Rancher and UsulNet: the adjacent options
Short mentions so nobody searching for these feels stranded.
1Panel (37,290 stars, GPL-3.0, Go, v2.4.1 from 2026-10-22) is a full Linux server panel with a Docker UI bolted on: firewalls, files, apps store, the works. FIT2CLOUD-backed. v2.4.0 (2026-10-20) added vLLM monitoring and IPv6 firewall controls, confirming the “AI management platform” positioning in the repo description. Heavier than a pure Docker management UI, and the default branch is currently dev-v2, so check the release channel before assuming stable behavior. Choose it when you want a whole-server panel, not just containers.
CapRover (15,194 stars, TypeScript, mature since 2017, v1.15.5 from 2026-10-23) is a Docker Swarm PaaS with one-click apps. The GitHub API showed NOASSERTION for the license on 2026-10-27 (historically Apache-2.0, verify the file). Still a reasonable choice if you are already committed to Swarm.
Rancher (v2.15.2, 2026-09-23) is for readers who moved to Kubernetes. It is a full K8s management plane from Suse, a different animal from everything above. I do not review it hands-on here, and current Community vs Prime packaging changes often enough that you should read their docs before planning around licensing.
UsulNet was covered in depth in the previous version of this article as an all-in-one container management platform (PostgreSQL, Redis, NATS, multi-node). The repo has since moved to fran-olivares/usulnet with 133 stars and a last push in May 2026. It is a solo-dev beta product and those move or die fast; re-verify current status and limits on their site before committing. Install instructions from the earlier test are in the UsulNet install guide.

When Portainer is still the right choice
No tribalism here. Four cases where I would stay on Portainer:
- 3 Nodes Free is genuinely free if 3 nodes cover you and an annual renewal email is acceptable friction. Just read the terms: one license per company domain, node-count enforcement is reserved as a right.
- Kubernetes management. Nothing on this list does Kubernetes management except Portainer BE, Rancher, and KubeSolo (Portainer’s single-node Kubernetes for the edge). Arcane is read-only Swarm at best; Komodo now manages full Swarm (not Kubernetes); Dockge, Sencho, and Dockhand are Docker/Compose tools.
- Edge/IIoT fleets. The Portainer Edge Agent is still the product nobody has fully matched for large numbers of unreliable uplinks.
- You already paid. If migration cost exceeds renewal cost this year, renew and migrate later with a plan.
Also fine: Portainer CE on a single homelab host when none of the gated features matter to you.
If you stay on 3 Nodes Free
Calendar the annual renewal. Portainer sends the new key 14 days before expiry, but spam filters have eaten submissions before (their own FAQ warns about it). Keep the signup email. And do not exceed 3 nodes “temporarily” while testing; the license agreement does not have a soft edge there.
If none of those four cases apply, the feature gating plus renewal paperwork is your reason to move.
How to migrate from Portainer without downtime
You can migrate from Portainer to any compose-on-disk tool without dropping traffic. The honest framing: this is per-stack sequencing, not magic. Do one stack at a time, keep the old path working until the new one is verified.
- Inventory. List every stack in Portainer: name, images, env vars, volumes, networks, published ports. A spreadsheet is fine.
- Export. Pull each stack’s compose file and env from the Portainer UI. Stacks also live inside the
portainer_datavolume under numberedcompose/directories, but the exact layout varies by version. Do not trust a path you have not seen; look in a throwaway VM on your version first. - Recreate on disk. One directory per stack, for example
/opt/stacks/<name>/compose.yamlplus.env. Then prove parity by hand before any UI sees it:
mkdir -p /opt/stacks/myapp
cd /opt/stacks/myapp
# copy compose.yaml and .env from the Portainer export
docker compose up -d
docker compose ps
curl -I http://127.0.0.1:8080/health # hit the real health endpoint- Point the new tool at the stacks directory:
Dockge
services:
dockge:
image: louislam/dockge:1.5
environment:
- DOCKGE_STACKS_DIR=/opt/stacks
volumes:
- /opt/stacks:/opt/stacks
- /var/run/docker.sock:/var/run/docker.sockUse “Scan Stacks Folder” in the UI to adopt existing stacks. Pin the tag, do not run :latest here.
Komodo
Run Periphery on each host and point it at the stack directories. Keep core and Periphery versions in lockstep after upgrades. Remember the Komodo database needs its own backup schedule. And pin :2, not :latest. The :latest tag is deprecated and gets you v1 images.
Arcane
Mount the projects path identically inside and outside the container and set PROJECTS_DIRECTORY:
volumes:
- /opt/docker:/opt/docker
environment:
- PROJECTS_DIRECTORY=/opt/dockerExisting compose projects are adopted when the paths match. Absolute paths only.
Sencho
Same 1:1 path rule: mount the stack directory identically and set COMPOSE_DIR:
volumes:
- /opt/docker:/opt/docker
- /var/run/docker.sock:/var/run/docker.sock
- ./data:/app/data
environment:
- COMPOSE_DIR=/opt/dockerCompose projects on the mounted path show up as adoptable stacks. The UI listens on port 1852.
- Move backup config. If you adopt in-UI backups (Arcane S3, Dockhand restic, Sencho archives), configure them and run one manual backup plus one restore test before you trust the schedule.
- Verify with the checklist below. For day-to-day operations after migration, see how to update a container with Docker Compose.
- Rollback plan. Stop Portainer, do not delete it, and leave
portainer_dataintact for one release cycle. If the new tool fails you, start Portainer again and re-point. Decommission only after the verification checklist passes on a host reboot.
- Export compose + env for every stack
- Recreate as plain dirs and
docker compose up -donce by hand - Adopt in the new tool (Dockge, Komodo, Arcane, or Sencho config above)
- Verify:
docker compose ps, health endpoints, logs, host reboot - Rollback-ready: Portainer stopped but present, data volume untouched
- Decommission Portainer only after a clean reboot cycle
- Post-exit cleanup: reclaim disk space from old overlay2 directories after decommissioning Portainer
Secrets do not belong in Git
When stacks move to plain directories, the temptation is to push /opt/stacks to a repo with .env included. Do not commit production secrets. See Docker Compose secrets: what works and safer alternatives for patterns that survive contact with a public repo.
Verify and failure modes, in order of how often they bite:
- Parity comes first:
docker compose psshould show the same services and health as Portainer did. Broken looks like a service silently absent because the env file did not come along in the export. - Then
curl -Ieach health endpoint. DNS and TLS stay the same, but upstream container names change with the compose project name. Traefik labels that matched the old project name will 502. - Reboot with
sudo rebootand confirm every stack returns. Tools that read files on disk (Dockge, Arcane projects, Komodo stacks, Sencho stacks) recover; anything you only clicked together in a UI will not. - In a scratch VM, remove the management UI and confirm your stacks keep running. Files-on-disk tools leave them intact; database-backed tools can take the definition with them.
- If you read stacks out of
portainer_dataand the directory layout surprises you, stop and inspect the live volume instead of guessing. Env files forgotten in the export are the single most common broken deploy. - Portainer-created networks and stale volumes outlive the container. Prune carefully, and use the overlay2 cleanup guide above for the disk space side.
Security baseline for any Docker management UI
This applies to Arcane, Dockhand, Sencho, Dockge, Komodo, 1Panel, Portainer, and anything else that can start containers. The same principles in how I secured my Docker server after the BSI report apply here. A management UI is just another attack surface.
docker.sock equals root on the host
Any container with /var/run/docker.sock mounted can start a privileged container and own the host. A Docker management UI with the raw socket is a root web panel. Treat it that way in your threat model.
Four non-negotiables:
- Put a socket proxy in front of the raw socket: tecnativa/docker-socket-proxy (or equivalent), allowing only the verbs the UI needs.
- Put a reverse proxy with auth in front of the UI, or keep it on VPN/localhost only. Never publish a management UI on
0.0.0.0raw. - Turn terminal and exec features off unless you are actively using them. Dockge 1.5.0 disabling the Console by default is the right call.
- Update the UI itself. These projects have CVEs like everything else. A concrete example: the eMudhra/emSign intermediate CA compromise (CVE-2026-111943) was patched within three days by three tools on this list: Portainer 2.45.3 (2026-10-21), Komodo v2.3.4 webpki-roots bump (2026-10-22), and 1Panel v2.4.1 (2026-10-22).
The socket proxy pattern, using the env-var names from the current tecnativa/docker-socket-proxy README (double-check them against the repo before you deploy, the semantics have shifted over the years):
services:
docker-socket-proxy:
image: tecnativa/docker-socket-proxy:latest
container_name: socket-proxy
environment:
- EVENTS=1
- PING=1
- VERSION=1
- AUTH=0
- SECRETS=0
- POST=1
- BUILD=0
- CONTAINERS=1
- EXEC=1
- IMAGES=1
- INFO=1
- NETWORKS=1
- NODES=0
- PLUGINS=0
- SERVICES=0
- SESSION=0
- SWARM=0
- SYSTEM=0
- TASKS=0
- VOLUMES=1
volumes:
- /var/run/docker.sock:/var/run/docker.sock:ro
arcane:
image: ghcr.io/getarcaneapp/manager:latest
environment:
- DOCKER_HOST=tcp://docker-socket-proxy:2375
# no /var/run/docker.sock mount hereThen put the UI behind a Traefik reverse proxy with auth (forward auth, Traefik basic authentication on Docker services, or your SSO layer). Verify after setup: from outside the host, confirm the UI port does not answer directly (curl -v https://host:3552 should time out or refuse), and from the UI confirm it cannot reach API verbs you did not allow. If a terminal feature is enabled, that is the test surface.
Failure modes here are boring and severe: a port accidentally bound to 0.0.0.0, an allowlist so broad that POST=1 plus CONTAINERS=1 is effectively “create root container”, a terminal left enabled after an eval, and agent version skew after core upgrades (core, then agents, then a fleet check).
Ops notes for small boxes: Trivy and Grype scans burst CPU and RAM during image scan. On 1 GB, schedule scans off-peak or disable them per environment (Arcane v2.11.1 has that toggle). And if you want the UI and socket proxy isolated from production workloads, even a budget Hostinger VPS is enough for a management plane of one.
FAQ
Is there a completely free Portainer alternative?
Yes. Arcane, Sencho, Dockge, Komodo (including v2 with Swarm support), Coolify, Dokploy, lazydocker, and Dozzle are all $0 to self-host with no license key and no renewal. Dockhand is free under BSL 1.1 for personal and internal business use, with a conversion to Apache 2.0 in January 2029. None of these require an email signup to unlock features.
What happens if I do not renew Portainer's 3 Nodes Free license?
Renewal is free but annual. Portainer says it sends a new key 14 days before your current one expires. What happens exactly if a key lapses, lockout versus feature downgrade, is not clearly documented on the site. Users report expiry warnings after reboots (GitHub discussion #12301), so treat the renewal as mandatory. The “7 days” clause on the renewal page is about moving your key between instances during a server migration, not a renewal grace window.
Is Dockge still maintained?
The honest answer as of 2026-10-27: the last release, 1.5.0, is from 2025-03-30 (~19 months). The last substantive commit was 2026-04-19; the only commit since is a CI change on 2026-10-23. “Is this abandoned?” threads and community forks exist. The files-on-disk philosophy is still the right one and 1.5.x works well. Pin :1.5.x, keep compose files in Git, and check the repo pulse before you expand beyond one host.
Is Sencho ready for production?
Sencho is pre-1.0 (v0.98.1 as of 2026-10-27) with a small community, and the maintainers say so themselves: the repo ships a KNOWN_LIMITATIONS.md and asks you to validate against your own setup before deploying on critical infrastructure. The feature set is real: SSO, RBAC, Trivy scanning, fleet ops. And its own authors run it in production. For a homelab or a small fleet you can roll back from, it is worth an install. For a fleet you cannot afford to babysit, Arcane or Komodo are safer bets today.
Can I manage multiple servers from one dashboard for free?
Yes. Komodo does it with Periphery agents (now with outbound connections for NAT’d hosts), Arcane with arcane-agent, Dockhand with the Hawser agent, and Sencho by linking full instances (or the Pilot Agent for NAT hosts). All free at the tiers described above. Budget time for version skew: upgrade the primary, then the nodes or agents, then verify the fleet state.
Which alternative has SSO/OIDC without paying?
Arcane ships OIDC plus passkeys and MFA on the free tier. Sencho has OIDC with Google/GitHub/Okta presets, TOTP, and five-role RBAC free. Dockhand has OIDC/SSO and MFA free, but LDAP and RBAC sit on its Enterprise tier. Portainer CE does not include OIDC/SSO at all; that is Business Edition.
Do these tools work with Kubernetes?
Mostly no. Arcane has read-only Swarm access at best. Komodo now manages full Docker Swarm (not Kubernetes, keep that distinction precise). Dockge, Sencho, and Dockhand are Docker/Compose tools. For Kubernetes you want Rancher, Portainer BE, or KubeSolo (Portainer’s single-node Kubernetes for the edge). If someone sells you a “Portainer replacement for K8s” in this category, read the docs twice.
Verdict: which Portainer alternative should you pick?
Restating the tree in prose, because this is the decision:
- Arcane if you want a like-for-like Portainer replacement. Single Go container, BSD-3, free OIDC and passkeys, and since v2.9-v2.17 it scans, patches, backs up, and supports Podman and OpenTelemetry. This is the default, and what I run on my own servers.
- Dockhand when scan-before-swap rollbacks, LDAP, or enterprise secret managers matter more than OSI licensing. Accept BSL 1.1 with eyes open.
- Sencho if you want compose-on-disk with fleet features, free RBAC/SSO, and Trivy policies that can block a deploy, and you can live with pre-1.0 software and a small community.
- Dockge for single-host pure compose simplicity, with the pulse caveat and a pinned tag.
- Komodo for multi-server fleets, Swarm fleets, NAT-friendly outbound agents, and API-driven automation. Budget RAM and a database backup.
- Dokploy or Coolify when the real job is deploying apps. I run Dokploy on my fleet; Coolify if you want the bigger template catalog.
- lazydocker, Dozzle, or the plain CLI when you did not need a dashboard at all. Try this first.
- Portainer if you need Kubernetes, Edge/IIoT at scale, or the 3 Nodes Free renewal is friction you accept.
Whatever the tool, keep the boring ops basics: stack definitions as files on disk, config in Git (without secrets), volumes backed up to S3-compatible storage. Tools come and go, including the ones I just recommended. Those habits make any of them replaceable.
Cost close-out: every tool in the verdict is $0 in license fees. Run it on the VPS you already have, or spend about €4-5/mo on a small dedicated box.
Arcane install guide (with socket proxy)Related articles
- Install Arcane - full setup guide with socket proxy and OIDC
- Install Dockhand - security-focused Docker manager
- Arcane vs Dockhand - side-by-side comparison
- Install UsulNet - all-in-one Docker management platform
- Install Dockge - lightweight compose management UI
- Best Docker containers for home server - what to run once your manager is set up
- Best self-hosted panels - server management panels compared
- ServerOS panel review - multi-VPS panel with a built-in MCP server
- Traefik reverse proxy for Docker - proper reverse proxy setup
Did this guide work for you?
Need help with Astro, VPS, or a self-hosted app? View services →


