Analytics cookies only (Google Analytics, PostHog). No ad networks, no cross-site tracking. See our privacy policy.
upstream: github.com/linuxserver/Heimdall (opens in new tab) · github.com/gethomepage/homepage (opens in new tab)
Pick Heimdall
If you want to add tiles in the browser with no YAML, like enhanced-app tiles and built-in search providers, and want an MIT licence.
Pick Homepage
If you want the dashboard as files in git, Docker label discovery, proxied widgets and the lower idle footprint we measured (~102 MB against ~146 MB).
Heimdall and Homepage both give you a page of tiles for your self-hosted services, but you build them in opposite ways. Heimdall is edited in the browser: add a tile, pick an icon, and it is stored in SQLite. Homepage is configured with YAML files and can add services itself by reading Docker labels. For another YAML-first comparison, Homarr vs Homepage puts Homepage against a drag-and-drop dashboard.
Heimdall's README: "Heimdall Application Dashboard is a dashboard for all your web applications. It doesn't need to be limited to applications though, you can add links to anything you like." It can show a search bar using Google, Bing or DuckDuckGo. Our catalog entry describes a Laravel app on SQLite, and the linuxserver.io image bundles nginx and PHP.
Homepage describes itself as an application dashboard with "integrations for over 100 services", easily "configured via YAML files or through docker label discovery". It is a Next.js app.
In Heimdall you type an application title and, for supported apps, pick it from a list. Per the README, "Foundation" apps fill in the icon and a default tile colour, and "Enhanced" apps accept details of the app's API so the tile shows live stats, for example queue size and download speed for NZBGet and SABnzbd. Nothing is edited as a file; the tiles live in the database.
In Homepage, services, bookmarks and widgets are YAML in the config folder, so the whole dashboard can be kept in git. Its widgets read from the services' own APIs, and the README says requests are proxied so API keys stay hidden. Docker integration adds container status and stats, and services can be discovered from labels.
Our Heimdall snippet has no login by default: anyone who can reach the port can
add tiles, because the seeded admin user has no password. Set a password on that
user or enable the image's htpasswd basic auth before publishing it.
Homepage's README says it must sit behind a reverse proxy or VPN that enforces
authentication if it is reachable from an untrusted network, and offers an
optional OIDC or simple password login.
Heimdall is MIT and Homepage is GPL-3.0. Both are fine for a private install.
We list 256 MB of RAM for both; neither project documents a figure, so this is
our estimate. In our install check (GCP e2-standard-2, Ubuntu 26.04), idle at
first boot with the default install snippet and no real workload, Heimdall used
~146 MB of RAM and ~482 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.
Both are 1 out of 5. Heimdall is a one-service compose file with a config
volume on port 8080. Homepage is one docker run with a config folder on port
3000 and HOMEPAGE_ALLOWED_HOSTS set.
Choose Heimdall if you want to manage tiles in the browser with no YAML, like its enhanced-app tiles and built-in search providers, and want an MIT licence.
Choose Homepage if you want your dashboard as files in git, Docker label discovery, proxied widgets for over 100 services, and the lower idle footprint we measured.
Both installs are verified on Ubuntu 26.04; the snippets are on the
Heimdall and Homepage pages. Back
up Heimdall's heimdall-config folder or Homepage's config folder, and put
authentication and TLS in front of either.
No. Heimdall is MIT, Homepage is GPL-3.0.
Heimdall if you want to manage tiles in the browser without YAML (~146 MB idle in our first-boot check). Homepage if you want a dashboard defined as files, Docker label discovery and proxied widgets (~102 MB idle). Both are 1 out of 5 to install.
Not in our install: anyone who can reach the port can add tiles. Set a password on the seeded admin user, or enable the linuxserver.io image's htpasswd basic auth, before publishing the port.
Per Heimdall's README, Enhanced apps accept details of the app's API so the tile can show live stats, for example queue size and download speed for NZBGet and SABnzbd. Foundation apps only fill in the icon and a default tile colour.
Yes. Homepage's README lists automatic service discovery based on 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 static page served as plain files, or a Next.js dashboard with proxied integrations and Docker label discovery.
One conf.yml with an in-browser editor vs. YAML files and Docker label discovery.