I run a lot of projects in parallel (ADHD? We'll never know) and half the time I open a new terminal, forget which port the last three services landed on, and end up guessing between 3000, 5173, and 8080 until something loads. So I built EchoPort: it scans localhost and shows you what's alive right now, no config file, no manual port list to maintain.
What it does
EchoPort scans your machine's localhost ports and shows which dev services are running. Three scan modes, depending on how much you want to sweep:
- Default: 8 essential ports (3000, 5173, 8080, and the other usual suspects)
- Common: around 50 ports and variations, covering React, Vite, Django, Rails, Storybook, and similar dev servers
- All: sweeps the full 65,535 port range
Noise filtering
Some Windows services (SSDP, WSDAPI, WinRM, Delivery Optimization) respond to HTTP requests and show up as false positives on a full scan. EchoPort filters the known offenders by default. If you want to see one anyway, you can add it back manually.
Preferences that stick
Scan mode, auto-refresh, interval, and any manually added ports persist in the browser. Close the tab, come back later, and it's exactly how you left it.
Stack
React, TypeScript, Vite, Tailwind CSS. Nothing exotic, just fast to run and easy to read.
Try it
npm install
npm run dev
Opens at http://localhost:5173. It's local by design, since it's scanning your own machine.
Repo: https://github.com/obrenoalvim/echoport
What's your current trick for keeping track of which dev server is on which port?
Top comments (0)