Deploy Homarr on Ubuntu — drag-and-drop homelab dashboard with service integrations, widgets, and a built-in icon pack.
Grab the automated bash script from GitHub to follow along with the video.
wget https://raw.githubusercontent.com/mhmdali94/Docker/main/management/homarr/homarr-ubuntu.sh
chmod +x homarr-ubuntu.sh
sudo bash homarr-ubuntu.sh
wget https://raw.githubusercontent.com/mhmdali94/Docker/main/management/homarr/homarr-ubuntu.sh
chmod +x homarr-ubuntu.sh
The script installs Docker if needed, then deploys Homarr with persistent configuration storage automatically.
sudo bash homarr-ubuntu.sh
Open your browser and navigate to:
http://<your-server-ip>:7575
Start building your homelab dashboard by adding tiles for all your self-hosted services.
# In the Homarr UI:
# 1. Click the edit icon (pencil) to enter edit mode
# 2. Click "+ Add tile" → search for your service by name
# 3. Enter the service URL (e.g. http://your-server-ip:9000 for Portainer)
# 4. Homarr pulls the status and icon automatically for 100+ known services
# 5. Drag tiles to arrange your perfect dashboard layout
| Port | Purpose |
|---|---|
| 7575 | Homarr Web UI |
Homarr is a modern, self-hosted homelab dashboard with a drag-and-drop interface that requires no YAML editing. It integrates deeply with popular self-hosted services — connecting to Sonarr, Radarr, qBittorrent, Portainer, and dozens more via their APIs to show live stats directly on dashboard tiles. A Portainer tile shows running containers count; a Radarr tile shows movies being downloaded; a Pi-hole tile shows the current block rate. Built-in widgets handle the basics (weather, search, calendar, RSS) and the icon search covers thousands of applications from the Homarr icon pack. It is the fastest way to get a polished homelab start page running.
Most homelab dashboards are either too minimal (just links) or too complex (YAML-heavy). Homarr hits the sweet spot: drag tiles to arrange them, click to configure integrations, see live service data without opening each app separately. The Sonarr/Radarr/qBittorrent integrations alone make it the top choice for media server homelab setups — you see at a glance what is downloading, what just finished, and how much disk space remains.
Homarr serves its web UI on port 7575 by default. For home network use, access it directly via the IP and port. For external access or HTTPS, proxy through Nginx Proxy Manager. The Docker socket mount (/var/run/docker.sock) is optional but enables automatic container detection — only mount it if you understand the security implications.
Dashy (YAML-based, more themes and widgets, better for power users), Homepage (ultra-lightweight YAML dashboard, minimal UI), Heimdall (simpler, no live integrations), Organizr (media stack focused with tab interface). Homarr is the best choice for media homelab setups where live Sonarr/Radarr/qBittorrent integration data is the primary requirement.
Skip Homarr if you want configuration-as-code and full YAML control — use Dashy instead. Also skip it if you need minimal resource usage (Homarr uses more RAM than Homepage or Dashy). For a single-user setup with fewer than 10 services and no media stack integrations, a browser bookmark bar or a simple HTML page may be sufficient.
PrismaTechWork provides end-to-end infrastructure services — from initial deployment and security hardening to ongoing monitoring, automated backups, and dedicated support. Whether you need a single-server setup or a multi-site network, our team ensures your infrastructure is built right, secured properly, and maintained reliably.
Homarr uses a drag-and-drop UI editor — no configuration files, accessible to non-technical users, excellent media server integrations. Dashy uses YAML configuration — more customisation options, version-controllable in git, more widgets and themes, better for power users. If you run Sonarr, Radarr, and qBittorrent and want live data on your dashboard with zero config editing, choose Homarr. If you want maximum control and are comfortable with YAML, choose Dashy.
Homarr has built-in integrations for: Sonarr, Radarr, Lidarr, Readarr, Prowlarr, qBittorrent, Deluge, Transmission, ruTorrent, Portainer, Dockge, Pi-hole, AdGuard Home, Jellyfin, Plex, Emby, SABnzbd, NZBGet, Overseerr, Jellyseerr, Tautulli, and more. Each integration connects via the service's API key to pull live data — queue lengths, download speeds, recently added media, container counts.
Yes. Homarr supports multiple user accounts with different permission levels. Admin users can create, edit, and delete boards. Standard users can view boards they have access to. You can create a shared family board with media links and a private admin board with infrastructure tools — each accessible to only the appropriate users. Boards can also be set as public (no login required) for simple home network use.
Add it as a custom tile: enter any title, URL, and manually select or upload an icon. Without a built-in integration, the tile acts as a simple link with an optional status check (Homarr pings the URL and shows up/down). For services with APIs not yet in Homarr, check the Homarr GitHub issues — community integrations are frequently added. You can also use an iframe widget to embed lightweight dashboards of other services.
Homarr includes widgets for: weather (using OpenWeatherMap), date and time (multiple time zones), search (DuckDuckGo, Google, Bing, or custom), RSS feed reader, iframe embeds, DNS hole statistics (Pi-hole/AdGuard), Docker container overview, and media stats (Jellyfin/Plex recently added). Widgets are added from the tile picker in edit mode and configured inline.
Mounting /var/run/docker.sock gives Homarr the ability to list, start, stop, and inspect all containers on your host — equivalent to root access. On a private home network, this is generally acceptable. For internet-facing or multi-tenant setups, use a Docker socket proxy (e.g. Tecnativa/docker-socket-proxy) to expose only read-only container listing. Never mount the Docker socket on a public server without a proxy.
Update Homarr by pulling the latest image and recreating the container: docker compose pull && docker compose up -d in the Homarr directory. Your board configurations and API keys are stored in the data volume and are preserved across updates. Check the Homarr release notes before updating — major versions occasionally include migration steps or breaking changes to integration APIs.
Yes, with caution. Set a board as public (no login required) and it can serve as a public-facing landing page accessible without authentication. However, ensure the public board only contains links to services you intend to expose — do not include internal services or API key-backed integrations on a public board. For a team or family use case, a public board showing media services behind a VPN is a common and safe setup.