Dev tools · alternatives · 2026
24 alternatives to PortTraceX
Reveal why a port is in use
PortTraceX is a developer tool that identifies which processes are using specific ports and why. It diagnoses port conflicts through root-cause analysis, provides safety indicators to prevent system issues, and offers… Below are 24 products that do a similar job, ranked by how close each is in meaning and then by launch-day votes.
- 1
Port Checker▲87simple tool to check open ports on your computer
2014 · portchecker.co · its alternatives →
- 2
Hey HN, we built Subtrace (https://subtrace.dev) to let you see all incoming and outgoing requests in your backend server—like Wireshark, but for Docker containers. It comes with a Chrome DevTools-like interface. Check out this video: https://www.youtube.com/watch?v=OsGa6ZwVxdA, and see our docs for examples: https://docs.subtrace.dev. Subtrace lets you see every request with full payload, headers, status code, and latency details. Tools like Sentry and OpenTelemetry often leave out these crucial details, making prod debugging slow and annoying. Most of the…
2025 · github.com · its alternatives →
- 3
A command-line tool to kill processes and containers running on specified ports. - jkfran/killport
2023 · github.com · its alternatives →
- 4
I built a small CLI tool that answers "what's using my port?" without the lsof/ss/netstat incantation dance.
Feb 2026 · github.com · its alternatives →
- 5
Port Kill helps you find and free ports and caches blocking your dev work. - treadiehq/port-kill
2025 · github.com · its alternatives →
- 6
Port Checker is a simple tool to check for open ports and test port forwarding setup on your router. Verify and diagnose connection errors on your computer.
2014 · portchecker.co · its alternatives →
- 7
Hi HN, I built a small Linux CLI tool called witr (Why Is This Running?). The idea came from a situation most of us have hit: you log into a machine, see a process or port running, and immediately wonder why it exists, who started it, and what is keeping it alive right now. witr traces a process, service, or port back to its origin and responsibility chain and explains it in a way that’s quick to read, especially when you’re debugging under pressure. This is v0.1.0. It’s intentionally small and focused. Feedback, criticism, and edge cases are very welcome. Repo:…
Dec 2025 · github.com · its alternatives →
- 8
tracexec helps you to figure out what and how programs get executed when you execute a command. It's useful for debugging build systems, catching fd leaks, understanding what shell scripts actually do, figuring out what programs does a proprietary software run, etc.
2024 · github.com · its alternatives →
- 9
- 10
Linux system exploration and troubleshooting tool with first class support for containers - draios/sysdig
2014 · github.com · its alternatives →
- 11
A cool-as-shit dynamic traceroute powered by custom software, married with an informative article about how the BGP routing protocol works and guides the shape of the Internet.
2023 · how-did-i-get-here.net · its alternatives →
- 12IB
I found it odd there wasn’t a simple web tool to scan Docker Hub images for vulnerabilities. So I built one. It’s powered by the popular open-source tool Trivy.
2023 · containercve.com · its alternatives →
- 13
- 14
Hi HN, Recently I wasted several hours wrangling my dev environment only to find out that the browser frontend was talking to the wrong version of the backend. This got me thinking--why on earth are we still using simple numbers to describe which process to connect to? Why not use names instead? I thought of all the times a program wouldn't start because of port conflicts. The more I thought about it, the crazier it seemed. Modern operating systems already offer no-conflict ports: if you make your TCP server listen on port 0, the OS assigns you a random available port. But that only solves…
Jul 2026 · portzero.net · its alternatives →
- 15
- 16
Tracking history of USB events on GNU/Linux. Contribute to snovvcrash/usbrip development by creating an account on GitHub.
2019 · github.com · its alternatives →
- 17
Local Area Network discovery tool with an interactive Terminal User Interface (TUI) written in Go. Discover, explore, and understand your LAN in an intuitive way. Knock Knock.. who's there? 🚪 - ramonvermeulen/whosthere
Jan 2026 · github.com · its alternatives →
- 18
Relicx▲285Monitor, debug and test real-world CX flows in minutes
2022 · app.relicx.ai · its alternatives →
- 19
An AI port manager for your Mac.
Aug 2026 · portradar.devmesh.xyz · its alternatives →
- 20
CLI tool for inspecting and managing services listening on localhost ports - raskrebs/sonar
Mar 2026 · github.com · its alternatives →
- 21
Trace▲85A lightweight GraphQL query performance monitoring dev tool
2021 · gotrace.info · its alternatives →
- 22
Find, kill, and guard the processes on your ports
Jun 2026 · automatalabs.ca · its alternatives →
- 23
A beautiful web dashboard for Linux. Contribute to tariqbuilds/linux-dash development by creating an account on GitHub.
2014 · github.com · its alternatives →
- 24
Flytrap 2.0▲120The fastest and most detailed tool for fixing bugs
2023 · useflytrap.com · its alternatives →
Also compare
- Port Checker alternatives
- Subtrace – Wireshark for Docker Containers alternatives
- Killport – CLI tool to kill processes running on a specified port alternatives
- Portview – a diagnostic-first port TUI (Rust, cross-platform) alternatives
- Port Kill – A lightweight macOS status bar development port monitor alternatives
- Open Port Checker alternatives
Ranked by how close each launch is in meaning, then by votes. Prices were read from each product’s own site when checked and can change. Refine with your own description →