Starbase

Starbase 80 is a lightweight self-hosted homepage that gives homelab users quick access to Docker containers and other services through a clean, customizable…

  • Other
  • Productivity
  • Tools & Utilities
Starbase 80 is a lightweight self-hosted homepage that gives homelab users quick access to Docker containers and other services through a clean, customizable dashboard.

Platform availability

Available on 2 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server

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.

61/100 Good

Maintained
71last commit 70 days ago
Popular
55560 GitHub stars
Easy to install
452 install platforms, install notes, Docker image
Light to run
2016 GB minimum RAM, runs on ARM
Security check
94no serious findings, 1 minor, CI, tests

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

GitHub stars
560
Open issues
6
Last commit
2026-09-11
License
MIT
Activity
stale

Checked 19 days ago - source: GitHub (notclickable-jordan/starbase-80)

Resources & Compatibility

Minimum requirements: 16 GB RAM, 40 GB disk. ARM (e.g. Raspberry Pi) is supported.

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

First-install notes

  • Create and fill in your config.yaml Copy config.yaml.example to config.yaml, then add the integrations you want and the Neo4j database address and credentials. If these are missing or wrong, Starbase won't know what to collect or where to store it. source
  • Run setup after editing the config Run yarn starbase setup, or docker-compose run starbase setup if using Docker, so Starbase clones each listed integration and installs its dependencies. Without this step, the later run command may fail because the integration code and packages are not installed. source
  • Check Neo4j details in your config Make sure the Neo4j URI, username, and password point to a database that is actually running and reachable. If the address or password is wrong, Starbase may start but cannot save the data it collects. source
  • Create config.json Create config.json in the app data location, copy the sample from the GitHub repository, modify it for your services, then restart the container. source

Fetched 38 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Where do I put the Starbase 80 configuration file?

Mount it at /app/src/config/config.json in the container, typically by mapping a local config.json file in your compose file. Modify that file to define the services and links you want shown.

Do I need to restart the container after changing the configuration?

Yes, if you change the config JSON, restart the container and refresh the page to see the change.

Does Starbase 80 query Docker for service status?

No, it does not integrate with Docker. It simply displays the services and links you define in the config.

How do I hide the title or logo?

Set TITLE= or LOGO= as empty environment variables to hide those elements, or set HEADER=false to hide the title and logo together.

Answers sourced from github.com

Community

Collected 53 days ago - public community threads