Analytics cookies only (Google Analytics, PostHog). No ad networks, no cross-site tracking. See our privacy policy.
Self-host Homer
updated Nov 2026deployed by usprices checked · Jul 2026Install verified on Ubuntu 26.04 · Nov 2026 · how we test
We earn commissions when you shop through the links below. Full disclosure →
A static start page for your services, built from a single YAML file: groups of links and cards with icons, fuzzy search, themes, multiple pages and optional smart cards that show live status from supported apps. It has no database and no login; the container just serves a folder of files.
Pick Homer when you want the simplest possible start page: a static site generated from one YAML file, with groups of links, optional smart cards that show live status for some apps, fuzzy search, themes and keyboard shortcuts, and nothing to log in to or keep in a database. It is Vue, licensed Apache-2.0, and the container only serves the files in a folder you mount. Our snippet follows the README's `docker run` with the image pinned to `b4bz/homer:v26.08.3` (released 2026-08-30, amd64, arm64 and arm), runs it as your own user id so the mounted folder stays writable, and lets the image copy its default `config.yml` and assets into the empty folder on first start. We did not find an upstream RAM minimum, and a static file server needs little, so our 64 MB floor is an estimate. In the catalog, Homepage is also YAML-driven but adds a server process with service stats and Docker label discovery, Dashy adds an in-browser editor, Homarr is edited by drag and drop and has accounts, Heimdall keeps its tiles in a database, and Glance is a feed reader as much as a launcher; Homer is the one that is just files.
What you need
Any VPS with at least 64 MB of RAM
A domain you control — most self-hosted setups need HTTPS in front of them
Paid link — we earn a commission if you shop through it.
Install
Run these commands on your server:
# Homer — README's docker run, pinned to v26.08.3; default config files are copied into ./homer-assets on first startmkdir -p homer-assetsdocker run -d --name homer --restart=unless-stopped \ --user "$(id -u):$(id -g)" -p 8080:8080 \ -v "$(pwd)"/homer-assets:/www/assets \ b4bz/homer:v26.08.3timeout 120 bash -c 'until curl -fsS -o /dev/null http://localhost:8080/; do sleep 3; done'# → http://SERVER_IP:8080 — no login; edit homer-assets/config.yml and reload the page, there is no restart step
Homer's README and documentation flag these before you rely on it:
non-negotiableThere is no authentication: anyone who can reach the port sees every link, and Homer is static files, so any protection has to be added in front of it, for example with a reverse proxy. Do not list internal-only URLs on a publicly reachable instance.
non-negotiableThe container runs as uid and gid 1000 by default and INIT_ASSETS=1 needs the config folder to be writable by that user. Our snippet passes your own uid and gid with --user; if you mount a folder owned by someone else the first start cannot copy the default config and you get a blank page.
non-negotiableHomer is not meant to be opened as a file: the README says it will not work over file:// and has to be served by an HTTP server, which the container does. Edits to config.yml apply on the next page load; no restart is needed.
non-negotiableHomer is a static page, so anything in config.yml (including any API keys you put in for smart cards) is downloadable by anyone who can load the page; keep secrets out of it.
non-negotiableThe image tag format is a calendar version (v26.08.3), and the latest tag moves; we pin the exact tag, so upgrading is a tag change after you read the release notes.