← Directory

homepage

Homepage is a highly customizable homepage (or startpage / application dashboard) with Docker and service API integrations.

  • Other
  • Productivity
  • Tools & Utilities
Homepage is a highly customizable homepage (or startpage / application dashboard) with Docker and service API integrations.

Platform availability

Available on 5 of 9 platforms

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

25/100 Low

Maintained
0GitHub repository no longer exists
Popular
No data
Easy to install
755 install platforms, install notes, Docker image
Light to run
No data

Based on 2 of 4 factors.

Availability: platform listings confirmed today, links checked 13 days ago

No GitHub repository data collected yet.

Checked 15 days ago - source: GitHub (BigBearTechWorld/homepage)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 15 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Save your config in a real folder In your compose file (the file that tells Docker what to run), map a real folder to /app/config, then back that folder up. It stores your services, bookmarks, and settings, so if it is lost your customized dashboard is gone. source
  • Keep your dashboard protected In your compose environment variables (settings passed to the container), set HOMEPAGE_AUTH_ENABLED to "true" and, if you use the MCP example, set a strong generated HOMEPAGE_MCP_TOKEN. Without that, anyone who can reach the port may be able to open your dashboard or endpoint. source
  • Use a Docker proxy for container info Add the docker-socket-proxy container from the docs and let Homepage use the restricted proxy instead of the full Docker socket (the control point that lets software manage containers). This lets Homepage safely show container and service details; without it, those widgets will not work or you expose your Docker setup. source

Fetched 15 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Where should Homepage store its configuration, and what should be backed up?

Map a real host folder to /app/config in your compose file and back that folder up. It contains your services, bookmarks, and settings, so losing it means losing your customized dashboard.

How can Homepage show Docker container information without exposing the full Docker socket?

Add a docker-socket-proxy container and point Homepage at the restricted proxy instead of the full Docker socket. Without this, the container widgets will not work or you may expose your Docker setup.

What should be enabled if Homepage can be reached directly on its port?

Set HOMEPAGE_AUTH_ENABLED to true in the compose environment variables. If using the MCP example, also set a strong generated HOMEPAGE_MCP_TOKEN so anyone reaching the port cannot open the dashboard or endpoint.

What can happen if the services.yaml file is edited incorrectly?

Homepage may display an application error saying a client-side exception has occurred. The browser console is where to look for more information.

Which kinds of services can Homepage integrate with through widgets?

Homepage supports hundreds of third-party service widgets, including the popular arr apps and many self-hosted apps such as Plex, Jellyfin, Emby, Transmission, qBittorrent, and Deluge.

Answers sourced from gethomepage.dev, gethomepage.dev, github.com, www.redditmedia.com

Community

Collected 14 days ago - public community threads