A Docker Management UI That Actually Speaks Your Language
You've got Docker running on a box somewhere. Maybe it's a homelab server, maybe it's a small production setup. Either way, you've probably spent more time than you'd like squinting at the command line, trying to remember whether it's docker ps -a or docker container ls to see what's actually running. Arcane is a web-based management UI for Docker that aims to make that whole experience a bit more human, and it's built with translation in mind from the start.
What It Does
Arcane is a Docker management interface—a web UI that sits on top of your Docker setup and lets you manage containers and related resources through a browser instead of memorizing CLI flags. The project describes itself as "Modern Docker Management, Designed for Everyone," which is a fair summary of what a UI layer like this is trying to accomplish.
Under the hood, it's written in Go (the README links to the package on pkg.go.dev under getarcane.dev/arcane/v3), and it's licensed under BSD-3-Clause. The current main branch is the v3 version of the project, with the previous 2.x line available on a separate release branch if you need it. The README points to an official documentation site for setup instructions, configuration details, and development guides, which is where you'll want to go for anything beyond the basics.
Why It's Cool
-
It's built for translation, not just translated. The README links to a Crowdin project for the UI, and the title of this piece isn't a gimmick—the project treats localization as a first-class concern. If you've ever used a tool that only speaks English and had to explain it to someone who doesn't, you know why that matters. The Crowdin badge shows the localization progress, and there's an open invitation to help translate.
-
It's a Go project, which means a single binary. The README links to the Go package reference, which tells you the backend is written in Go. That's a practical choice for a self-hosted tool—you're not juggling a Node runtime and a Python environment just to manage your containers.
-
Feature requests live in Discussions now. This is a small thing, but it says something about how the project is run. The maintainers moved feature requests to GitHub Discussions (with upvoting) and reserved Issues for bug reports. That's a deliberate choice to keep bug reports visible and prioritized, and it's the kind of process decision that tends to make a project easier to contribute to over time.
-
There's a real security posture. The README links to a Snyk vulnerability badge and a Software Bill of Materials (SBOM) at
getarcane.app/sbom. For a tool that has access to your Docker daemon—which is effectively root on the host—that's not a minor detail. Being able to check the dependency tree is worth something. -
It's honest about its versioning. The note at the top of the README tells you plainly that
mainis v3 and points you to the 2.x branch if that's what you need. No ambiguity about which branch is stable.
How to Try It
The README doesn't include install commands directly—it defers to the official documentation site for setup and configuration. So the practical path is:
- Head to the repository: github.com/getarcaneapp/arcane
- Follow the link to the official documentation at getarcane.app for setup instructions and configuration details.
- If you want the previous stable line, check out the
release/2.x.xbranch;mainis v3.
If you're interested in contributing translations, the Crowdin project is at crowdin.com/project/arcane-docker-management. And if you have a feature idea, the README is clear that it belongs in Discussions, not Issues—Issues are for bugs only now.
Final Thoughts
Arcane is worth a look if you run Docker and want a browser-based management layer, especially if you or your team work in multiple languages and appreciate a project that takes localization seriously rather than treating it as an afterthought. The Go backend and the SBOM are reassuring signals for a tool that touches your Docker daemon. The main caveat is that the README is thin on specifics—you'll need to spend time on the documentation site to know whether it fits your workflow. But the project is clearly active, the process around it is thought through, and it's openly asking for help with translations. If that sounds like your kind of project, go poke around.
Follow @githubprojects for more developer tools and open source projects.