Your homelab should be yours to run.

Self-hosting offers control, but the installation experience can bury it under manual configuration. Find a deployment file, edit the folders and ports, work out the network, then repeat for the next app. A collection of useful software becomes a second job before it becomes useful.

The project's history made another requirement clear: access to the tools and documentation must not disappear with a community website. HomelabARR inherits work from earlier community projects. We treat that lineage as a responsibility, not a story about inventing the ecosystem from nothing.

For people running their own media servers, home automation, monitoring and everyday tools on a Linux machine with Docker. Community Edition serves that job directly. The wider HomelabARR work includes a multi-host agent and an iOS companion, so the interface is not tied to sitting in front of one server.

We built Community Edition into a dashboard for browsing a bundled catalog and deploying one app at a time. It handles container start, stop, restart, removal and logs, with a port view and a place for custom application definitions. The documented catalog contains 100+ apps, and the software is MIT licensed.

The deployment choices cover a local IP address and port, a domain with encrypted web access, or a domain with an additional sign-in layer. Those choices let the same catalog serve a simple home installation and a more deliberately exposed service. The companion app brings day-to-day operation to a phone.

Each app is a readable deployment file in the repository. The backend reads that file, applies the selected deployment mode and asks Docker to run it through the managed access boundary. In the simplest mode, proxy-specific routing is removed while a no-new-privileges restriction remains.

A media stack still consists of separate applications. They communicate through their shared network and consistent media paths, and the owner completes each application's own setup. One click per app is useful; pretending that it configures every account, indexer and library would not be.

The most revealing fix was a dependency that should never have existed. CE's install instructions pointed at a now-private commercial templates repository. Its container was also configured to read that external path, so a new user saw an empty catalog even though CE's own app files were already bundled inside.

We removed that dependency and corrected the installation instructions. Community Edition now owns its catalog and does not need access to the commercial Eight.ly library. That separation is the practical meaning of a usable open-source release: a new user can get the software and the definitions it needs from the public project.