pickfit

BrowseInfra & DevOps tools

Homepage

A self-hosted application dashboard configured via YAML or Docker labels, with widgets and integrations for over 100 services.

Tested on Linux

Use it

Linux x86_64

  1. git clone repo and install pnpm via npm

    git clone --depth 1 https://github.com/gethomepage/homepage.git && npm install -g pnpm
  2. pnpm install

    cd homepage && pnpm install
  3. pnpm build

    cd homepage && pnpm build
Where the README and reality differ
  • README: pnpm install / pnpm build
    What worked: pnpm is not preinstalled; npm install -g pnpm first

Check that it works

curl -sS -f http://localhost:3000/api/healthcheck

The output should contain “up”.

First thing to try

cd homepage && mkdir -p config && cp -rn src/skeleton/* config/ && cat > config/services.yaml <<'EOF'
- Media:
    - Self:
        href: http://localhost:3000/
        description: Homepage itself
        widget:
          type: customapi
          url: http://localhost:3000/api/healthcheck
          mappings:
            - field: status
              label: Status
    - Sonarr:
        href: http://localhost:8989/
        widget:
          type: sonarr
          url: http://localhost:8989
          key: dummy
EOF
cat > config/bookmarks.yaml <<'EOF'
- Developer:
    - Github:
        - abbr: GH
          href: https://github.com/
EOF
cat > config/widgets.yaml <<'EOF'
- datetime:
    text_size: xl
    format:
      timeStyle: short
- search:
    provider: duckduckgo
    target: _blank
- openmeteo:
    label: Berlin
    latitude: 52.52
    longitude: 13.41
    units: metric
EOF
cd homepage && HOMEPAGE_ALLOWED_HOSTS=localhost:3000 pnpm start
curl -sS -f http://localhost:3000/api/healthcheck

Run HOMEPAGE_ALLOWED_HOSTS=localhost:3000 pnpm start in the homepage folder, then open http://localhost:3000 in your browser.

What it does

  • Add services and web bookmarks
    How to use it
    1. Create the config folder with mkdir -p config && cp -rn src/skeleton/* config/, then list your services in config/services.yaml and your links in config/bookmarks.yaml.
    2. Start the dashboard with HOMEPAGE_ALLOWED_HOSTS=localhost:3000 pnpm start.
    3. Check your bookmarks with curl -sS -f http://localhost:3000/api/bookmarks.
    Tested
  • Add widgets for over 100 services
    Not shown working
  • Find Docker services automatically from labels
    Not tested
  • Show weather, time, date and search widgets
    Not shown working

How far pickfit got

Linux x86_64

  1. Installs
  2. Starts
  3. 1 of 4 features work
  4. Works offline

Good for

  • show status and stats of Docker containers on a dashboard
  • monitor self-hosted apps like Sonarr, Radarr and Plex
  • keep bookmarks on a browser start page

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

Linux x86_64

Its service answers requests

  • Replayed from scratch
  • Works offline
  • Checked on 15 Nov 2026

Differences the test machine hit

  • README: HOMEPAGE_ALLOWED_HOSTS=gethomepage.dev:1234 pnpm start
    In the test: Works, but next start warns it does not work with output: standalone and suggests node .next/standalone/server.js
  • README: copy src/skeleton to config/
    In the test: pnpm build already copies missing skeleton files into config/

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.