Portracker

Portracker is a self-hosted, real-time port monitoring and discovery tool that automatically maps running services and open ports across your network.

  • Infrastructure
  • Monitoring & Logging
  • Network Services
  • Productivity
  • Security
  • Tools & Utilities
Portracker is a self-hosted, real-time port monitoring and discovery tool that automatically maps running services and open ports across your network. It helps homelabbers eliminate spreadsheet tracking and avoid port-conflict deployment failures, with Docker and TrueNAS collectors and peer instances for multi-server dashboards.

Platform availability

Available on 3 of 9 platforms

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

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.

27/100 Low

Maintained
0GitHub repository no longer exists
Popular
No data
Easy to install
553 install platforms, install notes, Docker image
Light to run
602 GB minimum RAM, runs on ARM

Based on 3 of 4 factors.

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

No GitHub repository data collected yet.

Checked 43 days ago - source: GitHub (BigBearTechWorld/portracker)

Resources & Compatibility

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

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

First-install notes

  • Start the Docker Socket Proxy first Before starting Portracker, run the docker-socket-proxy helper container and set Portracker's DOCKER_HOST=tcp://localhost:2375. This lets Portracker see your containers while giving it far less direct Docker power than a normal Docker connection. source
  • Open port 4999 and keep /data Map the app port with -p 4999:4999 so your browser can reach the login page, and back up the folder mapped to /data. If the port is blocked you can't open the UI, and losing /data can lose your saved settings. source
  • Create the first admin account During first-time setup, create the initial admin username and password. Without this account you won't be able to log in, and this setup step only works before any user exists. source

Fetched 34 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Does Portracker need an external database like PostgreSQL or Redis?

No. It runs as a single process with an embedded SQLite database and has no external database dependencies.

Do I need to enter running ports manually?

No. Portracker scans the host system to find and display running services and their ports automatically.

Does it provide extra context for Docker or TrueNAS?

Yes. It includes specialized collectors for Docker and TrueNAS to gather contextual information from the host.

Can I monitor internal instances without exposing their dashboards?

Yes. A common pattern is to run an edge Portracker on a bastion host with peer connections to internal instances, which avoids exposing internal dashboards.

Answers sourced from github.com, www.blog.brightcoding.dev

Community

Collected 42 days ago - public community threads