PortKiller releases Swift port tool

1/ PortKiller is an open-source desktop utility for developers who keep tripping over occupied localhost ports, stale `kubectl port-forward` sessions, and tunnel processes. The project’s GitHub repo describes it as a cross-platform tool to monitor ports, manage Kubernetes port forwards, integrate Cloudflare Tunnels, and kill processes with one click. (github.com) 2/ The core problem it targets is familiar: local backend work often sprawls across terminal tabs, background processes, and port conflicts. PortKiller’s pitch is that those tasks can be handled from one GUI instead of a mix of `lsof`, `kill`, `netstat`, `kubectl`, and tunnel commands. That framing comes from the repository feature list and app description. (github.com) 3/ The repo says PortKiller auto-discovers listening TCP ports, lets users search by port number or process name, and offers one-click termination with both graceful and force-kill options. It also includes favorites, watched ports, notifications, and category views for common process types such as web servers and databases. (github.com) 4/ The Kubernetes piece is what makes it more than a simple “kill port 3000” app. PortKiller says it can create and manage `kubectl port-forward` sessions, auto-reconnect on connection loss, and show logs and connection status. That puts a GUI on a workflow many backend developers still manage manually in shells. (github.com) 5/ The Cloudflare angle is similar. The repo says the app can view and manage active Cloudflare Tunnel connections and provide quick access to tunnel status. For developers exposing local services for demos, testing, or webhook callbacks, that means tunnel visibility sits alongside local port and Kubernetes forwarding controls. (github.com) 6/ On platform support, the current public materials point to macOS and Windows. The GitHub README lists Homebrew and DMG installation options for macOS and ZIP downloads for Windows, while the Windows README describes a native Windows app with system tray support and WinUI 3. The repo is primarily Swift, with C# used in the Windows codebase. (github.com) 7/ That matters because “cross-platform” here does not mean Electron. The project advertises native UI on each platform, with menu bar integration on macOS and system tray behavior on Windows. For developers who care about lightweight tooling and OS-native behavior, that is part of the appeal. (github.com) 8/ The project also appears to have real open-source traction, not just a mockup. GitHub showed about 4.8K stars, 182 forks and 36 releases when indexed, with the latest tagged release listed as v3.3.1 on February 16, 2026. The release page also shows packaged assets for macOS and Windows. (github.com) 9/ Recent release notes show the project is still adding workflow-specific features. Version 3.3.0 included “cloudflared protocol selection for tunnels in settings and UI,” while version 3.2.0 added custom Kubernetes namespaces for macOS, according to the GitHub releases feed. (github.com) 10/ The practical use case is straightforward: if you are running a local API on 3000, a database on 5432, a frontend dev server on 5173, and one or more `kubectl port-forward` sessions, PortKiller is trying to make that state visible in one place. Instead of hunting for which PID owns a port or which forwarding session died, the app surfaces those controls in a desktop interface. That is an inference from the documented feature set. (github.com) 11/ It is also worth being precise about what is verified. I could confirm the public GitHub repository, install methods, feature list, platform support, release history, and recent release notes. I could not reliably recover the full contents of the referenced X post through web fetch, so the screenshots/demo details should be treated as originating from that social post rather than independently reproduced here. (github.com) 12/ The next place to watch is the GitHub releases page and repository activity. As of the latest indexed release, v3.3.1 was the current tagged version, and the main branch showed newer commits after that release, which suggests continued development. (github.com)