More than a Docker status page
Arcane puts Docker in a browser, but its useful scope goes beyond a resource dashboard. It manages containers, images, networks, and volumes, while treating folders of Compose files as first-class projects. You can edit, deploy, redeploy, or destroy projects from the interface. The projects directory remains the source of truth, which is better than trapping configuration inside an application database.
The project becomes more distinctive across several hosts. Arcane Manager connects to an Agent on each remote machine. Direct mode requires the manager to reach port 3553, while Edge mode lets the agent connect outward from behind NAT or a firewall. A remote environment can also cover a Swarm node. Arcane handles Swarm services, stacks, nodes, configs, and secrets. This is a coherent answer for Docker estates too large for occasional shell sessions but not headed toward Kubernetes.
Routine maintenance is built in. Arcane checks image digests, updates containers or Compose services, restarts unhealthy containers, prunes unused resources, and sends notifications through Shoutrrr providers. Scheduled Trivy scans keep findings per image. Git synchronization, webhooks, project templates, file workspaces, and build history bring deployment work into the same control plane.
The interface respects how Compose works
Arcane's best design decision is preserving normal project files. It recursively scans a projects directory and recognizes standard Compose names plus unambiguous custom YAML files. Existing projects remain usable outside Arcane, and relative mounts work when the host and container see the same absolute project path. That condition matters: the installation guide explicitly says the paths must match. Mounting /opt/docker into an unrelated container path is not enough.
Updates are Compose-aware. When an image digest changes, Arcane can group updates by project and recreate only affected services rather than pretending each container is independent. The 2.8.0 release added project tags, a volume workspace, chunked uploads for large files, and fixes around Compose includes, Git sync, Swarm stack edits, and long health-condition waits.
The access model is credible for a young dashboard. Six built-in roles range from administrator to viewer, custom roles can narrow permissions, and assignments can be global or scoped to an environment. OIDC group mappings are reconciled on login. API keys have independent permission sets and expiration. Teams can deny shell access while allowing ordinary container operations, a useful distinction on production machines.
Easy to try, harder to deploy responsibly
A basic installation fits in one Compose service. Create an encryption key and JWT secret, persist /app/data, expose port 3552, and provide Docker access. The image supports x86, ARM, and RISC-V systems. SQLite is the default, with Postgres available through a database URL. Official images prepare startup as root and then drop to a configurable non-root user.
The uncomfortable part is Docker access. Mounting /var/run/docker.sock gives Arcane full daemon control, which is effectively control of the host. The documentation acknowledges this and provides a socket-proxy configuration. Even that proxy must allow writes plus container, exec, image, network, and volume APIs. Treat Arcane as privileged infrastructure: keep it off the public internet, use TLS and strong authentication, restrict proxy trust, protect its secrets, and back up its data.
A reverse proxy must pass WebSockets, and Arcane needs a correct public application URL. Imported project directories add ownership and path-mapping work, especially under SELinux. Every remote Agent needs its own Docker access and token. Edge mode removes an inbound port requirement, not the need to secure the manager and credentials. Optional mutual TLS is worthwhile for a serious fleet, but adds certificate enrollment and proxy decisions.
Current rough edges deserve attention
The broad feature set is moving quickly, and the issue tracker shows the cost. A report filed on August 14 against 2.8.0 says Update All upgraded the manager but failed for all remote agents. Fleet-wide self-upgrade must fail predictably. Until the case is resolved, upgrade a staging agent first and retain a manual rollback path.
Another 2.8.0 report describes a homepage widget refresh taking one Arcane container from about 77 MiB to 269 MiB, with three remote-node widgets causing out-of-memory restarts under a 512 MiB limit. It is one report, not a controlled benchmark, but small-server owners should watch memory before building a wallboard around the widgets. A separate current report says Git sync can still fail on unreadable files despite a related fix in the latest release.
Healthy, fast-moving, and worth a guarded trial
The repository had 6,985 stars, 277 forks, and 135 open issues and pull requests combined when researched. Of those, 124 were open issues. The queue is substantial, but activity is unmistakable: the last push was August 13, 2026, version 2.8.0 shipped that day, and reports were filed on August 14. Recent release work includes outside contributors as well as the lead maintainer.
Documentation is a major strength. Guides cover installation, migrations, reverse proxies, socket hardening, OIDC, roles, remote agents, Swarm, scanning, updates, notifications, and GitOps. The main README is sparse, but its documentation site answers operational questions many projects leave vague.
Arcane is the right trial for a Docker-first team that wants one approachable control surface without giving up Compose files or access controls. Dockge is easier when Compose editing is the whole job, and Portainer is safer when Kubernetes or commercial support is mandatory. For a growing Docker fleet, Arcane offers an appealing balance of modern usability and operator features, provided you take its privileges seriously and validate upgrades before rolling them across every host.