No spreadsheet has to track which service owns which port, because portracker discovers every service and port on your servers and keeps the list current from a self-hosted dashboard. Begin with a single port, shown with its owning service, its source (Docker or the host system), and its address, with internal container ports told apart from ports published to the host. Step back and ports gather into services: expandable cards carrying an icon, a health dot, and a port count, in list, grid, or table layouts, where a Why this status popover names the failing component and the rule that fired. Step back again and each server gets its own panel with hostname, OS, CPU, memory, and uptime, plus TrueNAS apps, VMs, and LXC containers once an API key is added. Step back once more and the whole fleet appears, because other portracker instances can be linked as peers, a VM's instance can be nested under its host, and every server can be searched at once. Along the way, rename services, hide the noisy ones, attach notes, act on a selection in bulk, or press Generate port for an unused number before deploying something new. Optional sign-in with a first-run setup wizard, an autoxpose link that shows public URLs and SSL status, light and dark themes, and keyboard shortcuts finish the picture. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.