~4KB
What is running on this port? One command. 4KB.
Instant port inspector with process details.
LinuxThe problem
Every developer hits port conflicts multiple times per week. "Port 3000 already in use." The answer requires lsof -i :3000 | grep LISTEN — a command nobody remembers, with output nobody can read. Or ss -tlnp | grep :3000, which is equally cryptic.
The solution
OmniWho takes a port number and tells you exactly what is using it: process name, PID, how long it has been running, memory usage, and CPU. One command, human-readable output, 4KB binary.
Why Bare-Metal Matters
OmniWho reads /proc directly via syscalls. No libc parsing, no shell pipes, no grep. The entire tool is 4KB because it does exactly one thing: answer the question every developer asks five times a day.
Technical Specifications
| Feature | Value |
|---|---|
| Binary Size | ~4KB |
| Function | Port inspector — what is using this port? |
| Output | PID, process name, uptime, memory, CPU |
| Dependencies | None |
| Speed | Instant (reads /proc directly) |
Comparison
| OmniWho | lsof -i | ss / netstat | |
|---|---|---|---|
| Size | ~4KB | System utility | System utility |
| Syntax | omni-who 3000 | lsof -i :3000 | grep LISTEN | ss -tlnp | grep 3000 |
| Output | PID + name + memory + uptime | Raw columns | Raw columns |
| Dependencies | None | libc | libc |
| Memorable | Yes | No — who remembers the flags? | No |
Use Cases
Port Conflicts
Start your dev server and port 3000 is taken. omni-who 3000 tells you what to kill.
Server Debugging
SSH into a production server. Something is listening on port 8080. omni-who 8080 identifies it instantly.
Container Debugging
Drop the 4KB binary into a minimal container to debug port bindings without installing lsof or net-tools.
Try Now — Free
Coming Soon
This product is under active development. Contact us for early access or to be notified when binaries are available.
Talk to the Team