Dev tools · alternatives · 2026
24 alternatives to Killport – CLI tool to kill processes running on a specified port
A command-line tool to kill processes and containers running on specified ports. - jkfran/killport
Killport is a command-line tool that terminates processes running on a specified port. Designed for developers, it simplifies the task of freeing up ports without manually identifying and stopping applications. The… Below are 24 products that do a similar job, ranked by how close each is in meaning and then by launch-day votes. Killport – CLI tool to kill processes running on a specified port launched in 2023; newer entries below may have overtaken it.
- 1
Port Kill helps you find and free ports and caches blocking your dev work. - treadiehq/port-kill
2025 · github.com · its alternatives →
- 2
CLI tool for inspecting and managing services listening on localhost ports - raskrebs/sonar
Mar 2026 · github.com · its alternatives →
- 3
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 →
- 4
A kill switch for Parse. Contribute to stevegraham/parseport development by creating an account on GitHub.
2013 · github.com · its alternatives →
- 5
- 6
- 7
Kill ports instantly on macOS. No terminal, no lsof,
Jun 2026 · mamawe.gumroad.com · its alternatives →
- 8
An AI port manager for your Mac.
Aug 2026 · portradar.devmesh.xyz · its alternatives →
- 9
Find, open and kill ports in a couple of clicks. Works with Node, Python, Ruby, PHP, HTTP and pretty much any process listening on a TCP port.
2019 · portmanager.app · its alternatives →
- 10
Portero▲166Know exactly what's running on every port of your Mac
Jul 2026 · porteroapp.pages.dev · its alternatives →
- 11
- 12
#!/usr/bin/env docker run. GitHub Gist: instantly share code, notes, and snippets.
2024 · gist.github.com · its alternatives →
- 13
Devbox is a command-line tool that lets you easily create isolated shells and containers. You start by defining the list of packages required by your development environment, and devbox uses that definition to create an isolated environment just for your application. In practice, Devbox works similar to a package manager like yarn – except the packages it manages are at the operating-system level (the sort of thing you would normally install with brew or apt-get). See it in action: https://youtu.be/WMBaXQZmDoA
2022 · github.com · its alternatives →
- 14
2024 · github.com · its alternatives →
- 15
Port Checker▲87simple tool to check open ports on your computer
2014 · portchecker.co · its alternatives →
- 16
Developer's best friend. Kill stubborn ports in one click.
Nov 2025 · portless.app · its alternatives →
- 17
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 →
- 18
Hey there HN! ruroco (RUn RemOte COmmand) is a tool that lets you execute commands on a server by sending UDP packets (instead of knocking on ports). the tool consist of 3 binaries: - client -> runs on your notebook/computer and sends the UDP packets - server -> receives the UDP packets and makes sure that they are valid - commander -> runs the command encoded by the data of the UDP packet if it's valid The commands are configured on the server side, so the client does not define what is going to be executed, it only picks from existing commands. I use this tool to open up the SSH port…
2024 · github.com · its alternatives →
- 19
eBPF Port Knocking Tool. Contribute to eeriedusk/knockles development by creating an account on GitHub.
2022 · github.com · its alternatives →
- 20
curl on steroids. Contribute to tikalk/commandcar development by creating an account on GitHub.
2015 · github.com · its alternatives →
- 21
Find, kill, and guard the processes on your ports
Jun 2026 · automatalabs.ca · its alternatives →
- 22
- 23
- 24
Terminal JSON viewer & processor. Contribute to antonmedv/fx development by creating an account on GitHub.
2018 · github.com · its alternatives →
Also compare
- Port Kill – A lightweight macOS status bar development port monitor alternatives
- Sonar – A tiny CLI to see and kill whatever's running on localhost alternatives
- Witr – Explain why a process is running on your Linux system alternatives
- ParsePort - A kill switch for Parse alternatives
- PortTraceX alternatives
- PerfOps CLI 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 →