Analytics cookies only (Google Analytics, PostHog). No ad networks, no cross-site tracking. See our privacy policy.
upstream: github.com/bastienwirtz/homer (opens in new tab) · github.com/gethomepage/homepage (opens in new tab)
Pick Homer
If you want the lightest start page we measured (~2 MB idle against ~102 MB), a YAML config and no server-side code, and can accept browser-side requests.
Pick Homepage
If you want API calls proxied so keys stay out of the browser, Docker label discovery and an opt-in login.
Homer and Homepage are both YAML-configured start pages for your services, and both are single-purpose and easy to run. The difference is what sits behind the page. Homer is a folder of static files served by a small web server, so everything, including any API key you give it, is handled in the visitor's browser. Homepage is a Next.js application with a server side that proxies requests to your services and can discover containers from Docker labels. If you are choosing between Homepage and a browser-edited dashboard, Homarr vs Homepage covers that.
Homer's README describes it as "a full static html/js dashboard, based on a simple yaml configuration file." It lists fuzzy search, multiple pages with item grouping, theme customisation and keyboard shortcuts among its highlights. Its Dockerfile builds the Vue app and serves the result from an Alpine image with lighttpd, so there is no application server and no database.
Homepage's README calls it "a modern, fast, secure fully proxied, highly customizable application dashboard with integrations for over 100 services and translations into multiple languages. Easily configured via YAML files or through docker label discovery."
Both read YAML from a mounted config folder. Homer's main file is
assets/config.yml (extra pages can load their own YAML file), and in our install
you edit it and reload the page; there is no restart step. Homepage splits settings across several files in its config
folder, and its docs cover a separate docker.yaml for Docker connections.
For live status, Homer has "smart cards": a type key on a service item enables
an integration, with cards for apps such as AdGuard Home, Jellyfin, Immich and
Home Assistant. Because Homer is static, those requests come from the browser.
Its docs warn that config.yml "is exposed at /assets/config.yml via HTTP" and
that anything sensitive in it, such as API keys, "is visible to anyone who can
access your Homer instance". They suggest a credential-injecting proxy such as
CORSair.
Homepage goes the other way: "All API requests to backend services are proxied, keeping your API keys hidden." It also offers Docker container status and stats, and automatic service discovery from container labels. Homer's smart cards can show container counts through Docker Socket Proxy, Portainer or What's Up Docker, but its docs describe no discovery from labels.
Neither needs a login to run. Homer has no authentication of its own, and our
install leaves the port open, so put it behind a reverse proxy or VPN with
authentication before exposing it. Homepage offers "an optional built-in OIDC
login flow or simple password login" (opt-in), and its README says that if it is
reachable from an untrusted network it must sit behind a reverse proxy or VPN that
enforces authentication, TLS and Host header validation. Separately, its docs
require HOMEPAGE_ALLOWED_HOSTS for access via a URL other than localhost, which
is why our snippet sets it.
Homer is Apache-2.0 and Homepage is GPL-3.0. Either is fine for a private install; the GPL's source-sharing terms apply only if you distribute Homepage.
We list a minimum of 64 MB of RAM for Homer and 256 MB for Homepage; neither
project documents a RAM figure, so both are our estimates. In our install check
(GCP e2-standard-2, Ubuntu 26.04), idle at first boot with the default install
snippet and no real workload, Homer used ~2 MB of RAM and ~24 MB of disk
(November 2026), and Homepage used ~102 MB of RAM and ~347 MB of disk
(September 2026). The readings are from different months, and disk is
docker system df for the install, not the whole box.
Both are 1 out of 5. Homer is one docker run with a bind-mounted
homer-assets folder on port 8080. Homepage is one docker run on port 3000
with a config folder and the allowed-hosts variable.
Choose Homer if you want the lightest page we measured, are happy with a hand-edited YAML file, and either do not need live widgets or can accept browser-side requests and an exposed config file.
Choose Homepage if you want server-side proxied integrations that keep keys out of the browser, Docker label discovery, or an opt-in login.
Both installs are verified on Ubuntu 26.04; the snippets are on the Homer and Homepage pages. Either fits the smallest plan. Put TLS and authentication in front of both, and keep API keys out of Homer's config.
Homer lists a lower minimum: 64 MB vs 256 MB for Homepage.
No. Homer is Apache-2.0, Homepage is GPL-3.0.
Homer for the smallest YAML start page we measured (~2 MB idle in our first-boot check). Homepage for server-side proxied widgets, Docker label discovery and an optional login (~102 MB idle). Both are 1 out of 5 to install.
Not an application server. Its Dockerfile builds the Vue app and serves the static files from an Alpine image with lighttpd, with no database. Smart-card requests to your services are made from the visitor's browser.
Homer's docs warn that config.yml is exposed at /assets/config.yml over HTTP, so any API key in it is visible to anyone who can reach the instance. They suggest a proxy that injects credentials server-side, or authentication in front.
Yes. Homepage's README lists automatic service discovery from Docker labels, plus container status and stats.
Paid link — we earn a commission if you shop through it.
A simple Laravel tile launcher, or a drag-and-drop board with user accounts, groups and live integrations.
A browser-edited tile launcher stored in SQLite, or a YAML-configured dashboard with Docker label discovery.
One conf.yml with an in-browser editor vs. YAML files and Docker label discovery.