Portero
Know exactly what's running on every port of your Mac
185 followers
Know exactly what's running on every port of your Mac
185 followers
Portero is a free, open source Mac app that shows every open port and the process behind it. See what's running, kill processes on busy ports, fix 'address already in use' errors, and block ports with the built-in macOS firewall.
Free
Launch Team / Built With
AWS Activate CreditsCredits that fuel your startup’s next milestone
Promoted
This looks super handy for tracking down port conflicts. One thing I'd love to see is a way to save profiles or groups of ports I'm monitoring for specific projects, so I don't have to keep an eye on a long list manually every time I switch contexts.
@mnevvertumazji Interesting. Today favorites are the only grouping (star what matters, it also protects from kills), plus search and category filters. Per-project profiles you can switch between is a neat framing for context switching. Adding it to the ideas list, thanks!
The "which node, from which project" problem is exactly why raw lsof never stuck for me — mapping a port back to a working directory is the useful part, not just listing PIDs. Two implementation questions: to enumerate every process's ports and to add a firewall block, does Portero need a privileged helper/root, or does it stay inside the user sandbox? And does a blocked port persist across reboots via pf rules, or only for the current session?
@ctresb It polls every few seconds by default, but what's the battery/CPU tradeoff on a laptop with that running constantly? would be nice to know if there's an on demand mode, or if the polling stays cheap regardless of how many ports are open
Are you planning to support deep Docker integration where Portero queries the local Docker socket? If we could resolve a generic docker-proxy process down to the exact container name and Docker Compose service, this would instantly become a must-have tool for local microservice debugging.
the visibility ceiling is worth spelling out — unprivileged lsof only sees sockets owned by your own uid, so a root daemon listening on a port stays invisible until the app escalates. for a dev tool that's fine. tagged as security software, that's exactly the port you'd want to see.
Congrats @ctresb on the launch, "Which node?" is the whole developer experience in two words, I've killed the wrong process on the wrong project more times than I'll admit.