Arcane is a free, open-source web interface for managing Docker — and it is not a replacement for Docker. You install it as one more container on a machine that already runs Docker Engine, open it in a browser, and from there you can start and stop containers, edit Compose stacks, prune images, watch volumes and networks, and update everything with one click. Version 3.0 landed on 14 November 2026, a fix release followed a day later, and the project is climbing GitHub Trending fast enough that its star count moved by more than 500 in a single day.
That is the honest pitch, and the honest correction in the same breath: Arcane sits on top of Docker Engine. It does not run containers by itself, it does not replace the Docker daemon, and if Docker is not installed, Arcane has nothing to manage. What it replaces is the terminal — and, for a growing number of self-hosters, Portainer and Dockge.
Why developers are switching right now
Arcane is not a brand-new project. The repository was created on 19 April 2025, and by mid-November 2026 it had grown to 114 releases. What changed is version 3.0. The 3.0.0 release, published on 14 November 2026, rebuilt the dashboard around a customizable widget grid, added a redesigned activity center, live upgrade progress with streaming logs, vulnerability-based update blocking, and expanded backup and GitOps features. The next day, 15 November 2026, version 3.0.1 followed with fixes for agent-mode startup, tighter certificate and update verification, and corrections to Docker, Swarm and backup behaviour.
The timing did the rest. Version 3.0 shipped, the project surfaced on GitHub Trending, and the numbers moved quickly. When this article was written on 18 November 2026, the repository showed 9,285 stars and 509 forks on its GitHub page — up from 8,776 stars and 407 forks recorded the day before, a gain of 509 stars and 102 forks in about a day. Star counts move fast on a trending project, so treat those figures as a snapshot dated 18 November 2026, not a permanent score. The project is licensed under the BSD-3-Clause license, its backend is written in Go, its frontend in SvelteKit and TypeScript, and its own site describes it as "Always free. Forever. Never changing."
The switchers are easy to find. The project's homepage quotes users from r/selfhosted who moved from Portainer and Dockge, and the recurring words are the same in almost every comment: cleaner interface, faster, easier to use, and auto-updates that remove the need for a separate Watchtower container. Those are user reports, not measurements — no independent benchmark of Arcane against Portainer exists — but the pattern is consistent enough to take seriously: people are not switching for one feature, they are switching because the everyday workflow feels lighter.
There is also a simpler reason the moment is now. Docker management has been a two-tool problem for years: Portainer for the full dashboard, Dockge for Compose stacks, and usually Watchtower or Diun bolted on for updates. Arcane tries to be all three in one container, and version 3.0 is the first release where that claim looks complete rather than aspirational.
What you actually get: the dashboard and daily workflow
Open Arcane and the first thing you see is the dashboard, which version 3.0 rebuilt as a free-form widget grid you can rearrange and save. Widgets show container health, memory usage rings, per-environment reclaimable space, and update status, with label filters so a host running dozens of containers stays readable. The activity center, also redesigned in 3.0, aggregates activity across environments in one place instead of making you click through hosts one at a time.
The daily workflow is deliberately boring, which is the point. You see which containers are running, which have updates, and which are unhealthy. You click a container to see its logs in the redesigned log viewer, its resource usage, and its configuration. You update one container or all of them, and version 3.0 streams the upgrade progress and logs live instead of leaving you staring at a spinner. You prune the images, volumes and networks you no longer need from the same screen.
Two details matter more than they sound. First, Arcane lets you edit Compose files in the browser and keeps them in sync with the files on disk — users report editing a compose file over SSH and seeing the change reflected in Arcane, and vice versa. Second, the interface is built to work on a phone: the project ships a mobile app beta for iOS and Android, and the web UI itself is responsive, which is why so many self-hosters mention managing their homelab from the couch. A live demo is available from the project's homepage if you want to click around before installing anything.
Containers, images, volumes and networks — the full Docker surface
This is the section that decides whether Arcane can replace your current dashboard, because it is the section where the simpler tools fall short. Arcane manages the whole Docker surface, not just one corner of it.
Containers get the full treatment: start, stop, restart, pause, remove, inspect, logs, live stats, and health status. Images can be browsed, pulled, inspected and pruned, and version 3.0 added image scanning with vulnerability information, including Docker Hardened Image status and the option to block updates when an image carries too many vulnerabilities. Volumes can be listed, inspected, backed up and pruned. Networks can be listed, inspected and pruned. Nothing here is exotic — it is the standard Docker surface, presented in one place, which is exactly what a management UI is for.
Image builds are included too: Arcane can build images from Dockerfiles and build contexts, which you point at with an optional /builds mount. That will not replace a CI pipeline, and the project does not pretend it will, but it covers the common homelab case of rebuilding a custom image after editing a Dockerfile.
The honest way to think about this section is as a checklist. If your current tool only handles Compose stacks, you are probably opening a terminal for everything else. Arcane's bet is that you would rather not.
Projects and Compose stacks: where Arcane beats Dockge
Projects are Arcane's name for Compose stacks — a folder holding a compose file, its environment files and its overrides. You point Arcane at a projects folder (the default is /opt/docker, set with the ARCANE_PROJECTS_DIRECTORY variable) and it picks up the stacks already there, so existing setups do not need to be re-created inside the tool. You can also create new projects in the browser, edit their Compose files with syntax highlighting, and manage their environment variables.
This is the direct comparison with Dockge, and it is worth stating plainly. Dockge is a good tool — its own description calls it a "fancy, easy-to-use and reactive self-hosted docker compose.yaml stack-oriented manager" — but stack-oriented is the whole story. Dockge manages Compose stacks. It does not manage images, volumes or networks, and it does not do container updates. Arcane does all of that, plus stacks. That is why users describe moving from Dockge to Arcane rather than the other way around, and why the project's own homepage quotes a user saying Arcane "fixes my main annoyances with dockge (the narrow compose editor, and no ability to see networks, images, or volumes)".
Arcane also adds two things Dockge users often bolt on separately. First, Git sync: point a project at a Git repository and Arcane keeps the Compose files in sync, with GitOps lifecycle hooks for running actions around deployments. Version 3.0.1 fixed a real annoyance here, keeping stack .env files intact across Git syncs and editor saves. Second, templates: Arcane ships a template system with template registries, so spinning up a common service is a form with fields rather than a blank compose file. Neither feature is unique in the wider ecosystem, but having them in the same tool as the stack editor is the point.
Auto-updates that replace Watchtower and Diun
The feature that comes up most in user reports is auto-updates, and it is easy to see why. Most self-hosters run Watchtower or Diun as a separate container whose only job is to notice new images and restart things. Arcane builds that job in.
Turning it on takes three steps in the interface: open Settings, then Automations, pick the agent, and enable Image Update Watcher plus Auto Update on a schedule. Schedules are five-field cron expressions, or descriptors such as @daily and @every. You can set an update delay in hours so a freshly published image is not pulled the minute it appears, exclude specific containers from automatic updates, and disable update checks per container. Updates can be applied by hand per container, or for everything at once, and version 3.0 added queued agent updates and counts to the "update all" action.
Version 3.0 also added the safety net that the bolt-on tools mostly lack: vulnerability-based update blocking. Arcane can scan images before updating and hold back an update when the new image carries too many vulnerabilities, with risk scoring to decide what "too many" means. Combined with the update delay, that covers the two classic Watchtower failure modes — pulling a broken release at 3 a.m., and pulling an image with a known vulnerability — without a second container.
One caution belongs here. Automatic updates are convenient and they are also a way to break a working system while you sleep. The delay setting exists for a reason, and excluding databases and anything you cannot afford to restart unexpectedly is not paranoia, it is practice. Arcane gives you the controls; it cannot decide your risk tolerance for you.
Remote hosts, agents and Swarm
A single-host dashboard is enough for one server. Arcane goes further with remote agents: small Arcane agents installed on other machines, which the main instance manages over an encrypted tunnel. The docs cover agent setup, and version 3.0.1 spent much of its changelog on agent behaviour — agents now skip manager-only scheduled jobs, skip manager-only RBAC and OIDC backfills on startup, and avoid redundant database work, all of which is the kind of fix that only matters once you actually run agents in production.
Docker Swarm is supported as well, with cluster management, workloads, nodes and agents, and configs and secrets. That puts Arcane in different company from Dockge, which is single-host by design, and closer to Portainer, which has built its reputation on multi-host and multi-cluster management. The difference is the price tag: Portainer's multi-node features sit in its paid Business edition, while Arcane includes agents and Swarm in the free, open-source build.
Agent connections use mTLS, and version 3.0.1 tightened that further by rejecting legacy edge SPIFFE client certificates. If you manage other people's servers, that kind of detail is not marketing copy — it is the difference between a tunnel you trust and one you do not. The docs also cover running Arcane behind a reverse proxy, TLS, and an outbound proxy, which is the normal shape of a production install.
Podman support: pods, Quadlets and Kubernetes YAML
Arcane is a Docker manager first, but it is not Docker-only. The documentation has a full Podman section: run Arcane on Podman, manage pods and Quadlets, apply Kubernetes YAML, manage Podman secrets, and run Podman auto-updates. For a homelab that has moved to Podman, or a shop standardising on it, that matters — most Docker dashboards treat Podman as an afterthought or not at all.
Be realistic about this, though. Arcane's Podman support is a real feature set, not a checkbox, but the project is still Docker-first in its naming, its docs order and its community. If you run Podman exclusively and need deep Podman-native behaviour, test the specific features you rely on in the demo before committing. If you run Docker with a Podman host or two on the side, Arcane covering both from one dashboard is a genuine advantage.
Arcane vs Portainer vs Dockge: the honest comparison
Three tools, three different answers to the same question. Portainer is the established full dashboard. Dockge is the focused Compose stack manager. Arcane is the newer project trying to cover both jobs at once. The table below uses only facts verified against each project's own pages on 18 November 2026.
| Feature | Arcane | Portainer | Dockge |
|---|---|---|---|
| License | BSD-3-Clause, free | Community Edition free; Business paid | MIT, free |
| GitHub stars (18 Nov 2026) | 9,285 | 38,842 | 24,851 |
| Containers, images, volumes, networks | Yes, all four | Yes, all four | No — stacks only |
| Compose stacks / projects | Yes, with Git sync | Yes (Stacks) | Yes — its main job |
| Built-in auto-updates | Yes, with delay + vulnerability blocking | Via webhooks / paid features | No — use Watchtower |
| Remote hosts / agents | Yes, agents + Swarm | Yes, multi-node (paid tiers) | No — single host |
| Podman support | Yes (pods, Quadlets, K8s YAML) | Limited | No |
| Backups (system + volumes) | Yes, built in | Paid / external | No |
| SSO / OIDC, roles, MFA | Yes, built in | Yes (Business) | No |
| Project age | Created Apr 2025 | Created May 2016 | Created Oct 2023 |
*Star counts are a snapshot from each project's GitHub repo page on 18 November 2026, and popularity is not the point of this table — Dockge's 24,851 stars are the larger number, and the honest reading is that Dockge earned them by doing one thing well for longer, while Arcane earned its 9,285 by doing more things in less time.
The fair summary is this. Portainer is the safe, established choice with the longest track record and the deepest enterprise features, and its free Community Edition covers a single host well. Dockge is the lightest choice if all you want is Compose stack management and you are happy running Watchtower beside it. Arcane is the choice if you want the full surface — containers, images, volumes, networks, stacks, updates, backups, agents — in one free tool, and you accept that it is a younger project with a shorter track record. Age cuts both ways: Portainer's maturity means stability, and Arcane's youth means faster change. Version 3.0 shipping a dashboard rebuild, vulnerability blocking and GitOps expansion in one release is the upside of that youth; the risk is that a project moving this fast will occasionally ship a 3.0.1 the next day.
Install Arcane in about ten minutes
You need Docker Engine and Docker Compose on the machine first. Arcane does not install Docker for you with the Compose method — it assumes Docker is already there. If you want one command that installs both, the project also offers a Linux install script, covered below.
Step 1 — generate an encryption key. Run this and copy the output:
docker run --rm ghcr.io/getarcaneapp/manager:latest /app/arcane generate secret
The key is a passphrase of at least 32 characters. You can also generate one with the Arcane CLI (arcane-cli generate secret) or with OpenSSL (openssl rand -hex 32). If you want to supply an exact 32-byte key instead, prefix it with hex: or base64:.
Step 2 — create a compose file. Save this as compose.yaml, replacing the placeholder key with the one from step 1:
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:
- ARCANE_APP_URL=http://localhost:3552
- PUID=1000
- PGID=1000
- ARCANE_ENCRYPTION_KEY=<your-encryption-key>
- ARCANE_PROJECTS_DIRECTORY=/opt/docker
cgroup: host
restart: unless-stopped
volumes:
arcane-data:
Three values deserve attention. ARCANE_APP_URL is the address you will open: keep http://localhost:3552 if you only use Arcane on the Docker host, or use http://<docker-host-ip>:3552 from other devices. The /opt/docker path appears three times — replace all three with the folder that holds your Compose projects. PUID and PGID set the host user and group IDs for files Arcane creates; if you omit them, they default to 65532:65532.
Step 3 — start it and sign in. In the folder with the compose file, run:
docker compose up -d
Then open the address you set as ARCANE_APP_URL. Sign in as user arcane. Arcane generates the first password on startup and writes it to /app/data/initial-admin-password; copy it out with docker compose cp arcane:/app/data/initial-admin-password . and set a new password when Arcane asks. If you would rather choose the first admin's username and password yourself, the docs cover a default admin account setup.
The one-command alternative. If the machine has no Docker yet, the Linux install script installs Docker and Arcane together:
curl -fsSL https://getarcane.app/install.sh | sudo bash
That is convenient and it is also a script piped into bash from the internet, so read it first if that sentence makes you uncomfortable — it should, at least a little. The project also ships an interactive uninstaller (curl -fsSL https://getarcane.app/uninstall.sh -o /tmp/arcane-uninstall.sh && sudo bash /tmp/arcane-uninstall.sh) that asks whether to keep Arcane's data, user and group, and Docker.
Requirements, security and the Docker socket question
The requirements are short: a Linux host (or a machine Docker runs on) with Docker Engine and Docker Compose, a folder for your Compose projects, and a browser. The official images start as root to prepare the container, then drop to a non-root user. Supported architectures are listed in the docs; the Compose method is the documented path, and the project also documents LXC container setup and an external Postgres database option for larger installs.
Now the security part, because it is the part people skip. Arcane mounts /var/run/docker.sock, the Docker socket. Anything that can talk to that socket can control Docker, which on most hosts means it can run arbitrary containers as root. That is normal for Docker dashboards — Portainer does the same — but it means Arcane's container is effectively privileged, and it must never be exposed to the internet without authentication, TLS and preferably a reverse proxy in front of it. The docs recommend a socket proxy to restrict what Arcane can do through the socket, and that is good advice rather than optional hardening.
Arcane's own security features are genuinely thorough for a free tool: OIDC single sign-on, passkeys and multi-factor authentication, roles and permissions, federated credentials, account recovery, agent mTLS, signed release artifacts you can verify, and vulnerability scans. Use the authentication features. Put Arcane behind a reverse proxy with TLS — the docs cover Nginx, Apache and Traefik, and remind you to forward WebSocket connections so live updates keep working. Do not expose port 3552 directly to the internet with the default setup. A management dashboard with root-equivalent Docker access and no TLS is not a homelab convenience; it is an incident waiting for a scanner to find it.
Honest limitations: what Arcane does not do
No tool is the right answer for everyone, and Arcane's limits are worth stating plainly rather than discovering them after a migration.
It is not a Docker replacement. Said twice in this article because it is the misunderstanding that causes the most trouble. Docker Engine does the work; Arcane is the window into it. If Docker breaks, Arcane cannot fix it, and if Docker is not installed, Arcane has nothing to show.
It is a young project. Created in April 2025, Arcane has about nineteen months of history behind it at the time of writing. Portainer's repository dates to May 2016. That youth shows up as speed — a major 3.0 release and a fix release in two days — and as risk: fast-moving projects change behaviour, deprecate things, and ship breaking changes. Version 3.0 itself lists breaking changes to legacy protocols and configuration, and the docs have a dedicated "Migrate to 3.0" page. Check the migration guide before upgrading a production host, and do not upgrade on a Friday.
It is not Kubernetes. Arcane manages Docker and Docker Swarm, plus Podman pods and Kubernetes YAML in a limited sense. If your workloads run on a real Kubernetes cluster, Arcane is not the tool for that job — Portainer's Kubernetes features or a native Kubernetes dashboard are. Arcane's Swarm support is real, but Swarm itself is a shrinking niche, and most new multi-host setups are Kubernetes, not Swarm.
The ecosystem is smaller. Portainer has years of forum threads, guides and third-party integrations; Dockge has a large community of stack templates. Arcane's community is growing fast — its Discord and GitHub Discussions are active, and feature requests now live in Discussions rather than issues — but you will find fewer answered questions for edge cases, and fewer pre-built templates than the older tools. The docs are good, which helps, but docs are not a community.
Auto-updates need supervision. Built-in updates are a feature, not a promise. A bad image release, a breaking change in a database container, or an update applied during a backup can still ruin your evening. The delay setting, per-container exclusions and vulnerability blocking reduce the risk; they do not remove it.
Who should switch — and who should stay put
Switch to Arcane if you run a homelab or a small server fleet on Docker, you currently juggle Portainer plus Watchtower, or Dockge plus a terminal, and you want one free dashboard that covers containers, stacks, updates, backups and remote hosts. Switch if you like Git-synced Compose projects, if you want vulnerability-aware updates without a second container, or if you manage a Podman host alongside Docker and want one window for both.
Stay put if Portainer Business already covers your multi-cluster needs and your team depends on its enterprise features and support. Stay with Dockge if all you ever do is manage Compose stacks, you like its simplicity, and you have no use for image, volume or network management. Stay with the terminal if your setup is five containers and a cron job — a dashboard is a tool, not a requirement, and the smallest setups do not need one.
The practical test costs an afternoon: install Arcane beside your current setup, point it at a copy of your projects folder, and run it for a week before deciding. It is one container, it is free, and it does not touch your existing stacks unless you tell it to. The trending numbers say a lot of people are running that test right now — 9,285 stars and counting, dated 18 November 2026.
| Release | Date | What changed |
|---|---|---|
| v3.0.0 | 14 Nov 2026 | Redesigned dashboard (customizable widget grid), redesigned activity center, live upgrade progress with streaming logs, vulnerability-based update blocking, expanded backups and GitOps, breaking changes to legacy protocols and config |
| v3.0.1 | 15 Nov 2026 | Agent-mode startup and performance fixes, tighter certificate and update verification (legacy edge SPIFFE certs rejected, updates always verified), Docker/Swarm/backup corrections, stack .env preserved across Git syncs |
| v2.17.3 | Before 14 Nov 2026 | Last 2.x release line; the main branch is now v3, with 2.x maintained on the release/2.x.x branch |
Frequently Asked Questions
Is Arcane a replacement for Docker?
No. Arcane is a web interface that manages Docker Engine. Docker must already be installed on the host, and Arcane talks to it through the Docker socket. If Docker is not running, Arcane has nothing to manage. Think of it as a dashboard for Docker, not a substitute for it.
Is Arcane really free?
Yes. Arcane is open source under the BSD-3-Clause license, and its own homepage says "Always free. Forever. Never changing." There is no paid edition listed on the project's site. You self-host it, so the only cost is the machine it runs on.
How is Arcane different from Portainer?
Portainer is the older, more established dashboard with a free Community Edition and a paid Business edition for multi-cluster features. Arcane is newer, covers a similar full surface (containers, images, volumes, networks, stacks), and includes built-in auto-updates, backups, remote agents and Swarm support in the free build. Portainer has the longer track record; Arcane has the faster release pace and the simpler all-in-one install.
How is Arcane different from Dockge?
Dockge manages Compose stacks and does that one job well — it has 24,851 stars for a reason. Arcane also manages stacks, but adds containers, images, volumes, networks, built-in auto-updates with vulnerability blocking, backups, remote agents and Podman support. If you only ever manage stacks, Dockge is enough. If you want the whole Docker surface in one place, Arcane is the broader tool.
Is it safe to expose Arcane to the internet?
Not without protection. Arcane mounts the Docker socket, which is effectively root-equivalent access to the host, so it must sit behind authentication, TLS and ideally a reverse proxy. Use OIDC or passkeys with MFA, never expose port 3552 directly, and consider the socket proxy the docs recommend. A management dashboard open to the internet with no TLS is an incident waiting to happen.
Does Arcane work with Podman?
Yes, with a dedicated Podman section in the docs covering pods, Quadlets, Kubernetes YAML, secrets and auto-updates. The project is Docker-first, so test the specific Podman features you rely on before committing, but running Docker and Podman hosts from one Arcane dashboard is a supported setup.
Sources
- Arcane on GitHub — getarcaneapp/arcane (9,285 stars, 509 forks, BSD-3-Clause, created 19 Apr 2025; figures from the repo page, 18 Nov 2026)
- Arcane v3.0.1 release notes (15 Nov 2026 — agent fixes, update verification, Docker/Swarm/backup corrections)
- Arcane v3.0.0 release notes (14 Nov 2026 — redesigned dashboard, live upgrade progress, vulnerability-based update blocking, GitOps expansion)
- Arcane homepage — getarcane.app ("Always free. Forever. Never changing."; demo, mobile beta, user reports from r/selfhosted)
- Arcane documentation (docs index: installation, projects, auto-updates, agents, Swarm, Podman, security)
- Arcane installation guide (Compose file, encryption key, Linux script, first admin account)
- Arcane auto-updates guide (Image Update Watcher, schedules, update delay, exclusions, vulnerability blocking)
- Dockge on GitHub — louislam/dockge (24,851 stars, 872 forks, MIT, created 23 Oct 2023; figures from the repo page, 18 Nov 2026)
- Portainer pricing (Community Edition free; Business edition paid, per-node licensing)
Related reading on Asad Webs: Univer: Build Your Own AI Office With This Open-Source Office SDK, Rakazo: The Open-Source Grok Bot Alternative You Actually Own, and Alibaba Open-Sourced Its AI Code Reviewer — 52,000 Stars and Counting. We checked the tools index at asadwebs.com/tools — there is no Docker or server-management tool there, so no tool is linked in this article.




Be the first to share a useful question or thought.