Arcane: a self-hosted web dashboard for managing Docker containers and Compose projects
Arcane is a self-hosted web interface for managing Docker containers, Compose projects, images, volumes and networks from one dashboard, with remote agents for other hosts.
If you run Docker on a home server or a VPS and you are tired of doing everything from the terminal, getarcaneapp/arcane gives you a web dashboard for that host. You install it as one more container, open it in a browser, and from there you can start and stop containers, edit Compose projects, watch images for updates, and manage volumes and networks. It is built for self-hosters: it runs on your own hardware, it talks to your own Docker engine, and there is no hosted account standing between you and your containers.
Quick facts
- What it is: a self-hosted web application for Docker management, with a dashboard, Compose project editor, image updates, backups and remote agents.
- Platform: it runs as a container on a host with Docker Engine and Docker Compose. A Linux install script installs Docker and Arcane together.
- License and cost: BSD-3-Clause, and free to run yourself.
- Languages: a Go backend with a SvelteKit frontend.
- Latest release: v3.0.1, published on November 15, 2026. The main branch is the v3 version of Arcane.
- Popularity: about 8,700 GitHub stars as of November 17, 2026.
How to install
The official documentation offers two ways in: Docker Compose, or a Linux install script. The Compose route needs Docker Engine and Docker Compose already on the host. Start by generating an encryption key. On the Docker host, in a terminal, run this command and copy the output:
docker run --rm ghcr.io/getarcaneapp/manager:latest /app/arcane generate secretThe key is a passphrase of at least 32 characters. If you would rather generate it with OpenSSL, run this command on the Docker host, in a terminal, instead:
openssl rand -hex 32Next, in a new folder on the Docker host, save the following as compose.yaml. Replace <your-encryption-key> with the key you just generated, and replace every /opt/docker value with the folder that holds your Compose projects:
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:In the folder that holds compose.yaml, start Arcane with this command:
docker compose up -dThen open Arcane at the address in ARCANE_APP_URL, which is http://localhost:3552 in the file above. From another device on your network, use the Docker host address instead, in the form http://<docker-host-ip>:3552. If you are on a Linux host and would rather let the installer do it all, run this command in a terminal instead of the Compose steps; it installs Docker and Arcane in one step:
curl -fsSL https://getarcane.app/install.sh | sudo bashFirst setup
Sign in as arcane. Arcane generates the first admin password on first start and writes it to /app/data/initial-admin-password inside the container. On the Docker host, in a terminal, copy that file out of the container with this command:
docker compose cp arcane:/app/data/initial-admin-password .Read the password from the copied file, sign in, and set a new password when Arcane asks. If you would rather choose the first admin account yourself, set ARCANE_DEFAULT_ADMIN_USERNAME and ARCANE_DEFAULT_ADMIN_PASSWORD in the environment before the first start; the default username is arcane. Nothing else needs an account: Arcane talks to the Docker socket on its own host, so there is no cloud account to create and no API key to fetch before you can use it. What it does need from you is the encryption key from the install step, a projects folder for ARCANE_PROJECTS_DIRECTORY, and a reachable address in ARCANE_APP_URL.
What stands out
- Remote agents that open no ports. One manager can control other Docker hosts, and each remote host runs a small Arcane agent that connects out to the manager and relays requests to its local Docker engine, so the host can sit behind NAT or a firewall. You enroll an agent with a single-use token from the manager, and the agent will not start without ARCANE_MANAGER_API_URL and ARCANE_AGENT_TOKEN.
- Compose projects stay plain files. Your projects live in the folder you point ARCANE_PROJECTS_DIRECTORY at, and Arcane edits those files rather than hiding them in a database. Projects can sync from Git, with Compose override selection, synced environment variables, and stack environment files kept across Git syncs and editor saves.
- Updates with safety checks. Arcane watches images for updates and can block an image update that exceeds your vulnerability limits, shows Docker Hardened Image status from image labels, and pulls risk scores toward the riskiest image and overdue known-exploited vulnerabilities.
- Backups that reach remote hosts. System backups cover remote environments as well as the local one, volume backups have retention and pruning, and destinations include S3 and Git as well as local storage.
- Podman and Swarm, not just plain Docker. Native Podman support arrived in v2.17.0, with Podman pods and Quadlets in the documentation, and the same manager can run Docker Swarm cluster workloads, nodes and agents.
There is also an official command-line client, arcane-cli, and a REST API. Every Arcane instance serves its own interactive API documentation at /api/docs, with the raw OpenAPI 3.1 document at /api/openapi.json, and API keys are created under System, then API Keys, with permissions you choose per key.
How it was built with Claude
The repository carries an agent guide, AGENTS.md, and an AI usage policy, AI_POLICY.md, so AI-assisted work is part of how this project is built rather than a secret. The policy says Arcane is developed with AI assistance and that maintainers use AI tools productively in their workflow. Outside contributors must disclose any AI use, stating the tool and the extent of the assistance, and AI-assisted pull requests must have been fully verified with human testing. Maintainers are exempt from those rules. The agent guide sets ground rules for AI-assisted changes: never run state-changing Git commands, search for existing helpers before adding new code, run the formatter and linter after every change, and never claim manual verification that did not happen.
The commit history shows the same pattern in small doses. A full-history count was not possible here: a blobless clone of the repository timed out after 8 minutes, so the counts below cover only the latest 100 commits, from November 9 to November 16, 2026, read from the GitHub API. In those 100 commits, 8 carry a Co-Authored-By line, and 1 of the 8 names Claude Opus 5.5. Kyle Mendell authored 65 of those 100 commits. That is a one-week window, not a picture of the whole history, and it should not be read as one.
Try it with your AI. Paste this into your own AI assistant to install Arcane on your Docker host with the official Compose method from this article.
Help me install Arcane (getarcaneapp/arcane) on my Docker host using only the official
Docker Compose method. First check that Docker Engine and Docker Compose are installed
on the host and tell me their versions, and stop if either is missing. My Docker host
address is [host address or IP], my Compose projects folder is [projects folder path],
and the address I will open Arcane at is [Arcane URL, for example
http://localhost:3552]. Generate the encryption key only with this command: docker run
--rm ghcr.io/getarcaneapp/manager:latest /app/arcane generate secret, or with openssl
rand -hex 32. Write a compose.yaml using only the image
ghcr.io/getarcaneapp/manager:latest, port 3552, the Docker socket mount
/var/run/docker.sock:/var/run/docker.sock, a named volume arcane-data mounted at
/app/data, ARCANE_ENCRYPTION_KEY, ARCANE_PROJECTS_DIRECTORY set to my projects folder,
and ARCANE_APP_URL set to my Arcane URL. Then start it only with docker compose up -d
run in the folder holding compose.yaml. Get the first admin password only with docker
compose cp arcane:/app/data/initial-admin-password . and tell me to sign in as arcane
and set a new password. Show any risky step first and wait for my confirmation before
running it. Use only the official commands and interfaces named here. Do not install
anything from unknown sources, do not touch credential files, and do not delete
anything.Known limits
- Version 3 is a break from version 2. The main branch is v3, the last 2.x release lives on the release/2.x.x branch, and v3.0.0 removed legacy image tags, protocols, migration paths, CLI flags and configuration fallbacks, and prefixed configuration variables with ARCANE_. Check the v3 migration notes before upgrading a 2.x install.
- Downgrades are blocked by default. The example environment sets ARCANE_ALLOW_DOWNGRADE=false, so do not plan on rolling back without a backup and a deliberate change to that setting.
- An agent needs persistent data. The agent stores its own key, encrypted, in /app/data, so keep that on a persistent volume. Without it, the agent enrolls again on every restart, a used single-use token is refused, and a multi-use token creates another agent.
- The Docker socket is powerful. Arcane mounts /var/run/docker.sock, which gives it full control of the host Docker engine, so the admin account is effectively root over your containers. Guard the admin password, and on SELinux hosts use a socket proxy or relabel the mounts as the documentation describes.
- Auto-login is for development and testing only. The example environment warns not to enable it in production, where it would log users in without credentials.
- Security reports have their own channel. Do not open a public GitHub issue for a vulnerability; report it by email to [email protected], and write the report yourself, since the security policy says reports must be written by a human, not generated by AI.
Related on claudefox
- agentes.chat: a self-hosted Slack alternative where AI agents sit in your channels
- open-code-review: a Go CLI that reviews Git diffs with a model and line-level comments
- CleanYourTV: debloat an Android TV or Google TV over Wi-Fi with Claude Code and get an Apple TV-style home screen
- Live Backdrop puts your Wallpaper Engine wallpaper behind the Claude desktop app
Problems and feedback
Report bugs in the GitHub issue tracker at https://github.com/getarcaneapp/arcane/issues, where issues are used for bug reports. Feature requests belong in Discussions, in the feature-requests category, where they can be upvoted. For a security vulnerability, email [email protected] instead of opening a public issue.
Source: getarcaneapp/arcane repository, Arcane README, Arcane LICENSE (BSD-3-Clause), Arcane AGENTS.md agent guide, Arcane AI usage policy, Arcane security policy, Arcane CHANGELOG, Arcane releases, Arcane documentation: Installation, Arcane documentation: Remote Agents, Arcane documentation: API Reference, Arcane home page, Arcane issues
This story first appeared in the claudefox daily briefing for November 18, 2026.