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/homarr-labs/homarr (opens in new tab)
Pick Heimdall
If you want a simple tile launcher with optional enhanced tiles, a search bar and the smaller disk footprint we measured (~482 MB against ~577 MB).
Pick Homarr
If you want multiple users with permissions, OIDC or LDAP sign-in and a wide set of live integrations, with slightly lower idle RAM (~135 MB against ~146 MB).
Heimdall and Homarr are both dashboards you edit in the browser rather than in a YAML file, so the choice is about how much they do beyond launching apps. Heimdall is a tile launcher: a Laravel app on SQLite, with optional live stats for supported apps. Homarr is a drag-and-drop board with user accounts, groups and integrations that stream live data. If you would rather keep the dashboard in files, Homarr vs Homepage is the comparison to read.
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 also be a browser start page with a search bar for Google, Bing or DuckDuckGo.
Homarr's README lists "Highly customizable with an extensive drag and drop grid system" and "Easy and fast app management - no YAML involved", plus "Detailed and easy to use user management with permissions and groups" and "Support for single sign on via OIDC / LDAP".
Heimdall separates "Foundation" apps, which only fill in the icon and colour, from "Enhanced" apps, which take the app's API details so the tile shows live stats such as download queue size and speed. If those apps run in Docker, the README says to use the Docker network address in the config.
Homarr's integration set is larger and more central. Its repository includes
integrations for AdGuard Home, Pi-hole, Jellyfin, Plex, Proxmox, Uptime Kuma and
many more, with "Realtime widget updates using WebSockets, tRPC and Redis". Its
source also contains Docker discovery code that reads homarr.* container labels
such as homarr.name and homarr.href.
Homarr has built-in users, groups and permissions, and our install creates the
first admin account on first visit. Heimdall has user accounts too: its source
includes a user-management screen with a password per user, and the seeded
admin user has none, so our snippet has no login by default. Set that password
or enable the linuxserver.io image's htpasswd basic auth before publishing the
port.
Heimdall is MIT and Homarr is Apache-2.0. Either is fine for a private install.
We list 256 MB of RAM for Heimdall, our estimate because the project documents no
figure, and 500 MB for Homarr, the minimum its docs state. 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 Homarr used ~135 MB of RAM and ~577 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. Heimdall is a one-service compose file on port 8080.
Homarr is one docker run on port 7575; it needs a 64-character
SECRET_ENCRYPTION_KEY, and its image bundles Redis and defaults to SQLite.
Choose Heimdall if you want a simple tile launcher with optional enhanced tiles, a search bar and the smaller disk footprint we measured.
Choose Homarr if you want multiple users with permissions, OIDC or LDAP sign-in, a wide set of live integrations, and the slightly lower idle RAM we measured.
Both installs are verified on Ubuntu 26.04; the snippets are on the
Heimdall and Homarr pages. Back up the
config folder (Heimdall) or appdata and homarr.env (Homarr), and put TLS in
front of either.
Heimdall lists a lower minimum: 256 MB vs 500 MB for Homarr.
No. Heimdall is MIT, Homarr is Apache-2.0.
Heimdall for a simple tile launcher with a search bar and optional enhanced tiles (~146 MB RAM, ~482 MB disk in our first-boot check). Homarr for user accounts, groups, OIDC or LDAP and a wide set of live integrations (~135 MB RAM, ~577 MB disk).
No. Homarr's README lists easy app management with no YAML involved; boards are edited with a drag-and-drop grid in the browser.
Its Docker image defaults to SQLite, stored under /appdata, and bundles a Redis server. Our install is one container with a generated SECRET_ENCRYPTION_KEY.
Homarr's README lists single sign-on via OIDC and LDAP. Heimdall's README describes neither. Heimdall has its own user accounts with optional passwords, our install starts with no password set, and the linuxserver.io image supports htpasswd basic auth.
Paid link — we earn a commission if you shop through it.
A browser-edited tile launcher stored in SQLite, or a YAML-configured dashboard with Docker label discovery.
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.