p0rt – see every dev server, port and Docker container in your menu bar

ddeunert1 pts0 comments

p0rt · never wonder what's running again<br>:p0rt<br>Never wonder<br>what's running again.<br>p0rt knows what’s alive: every dev server and Docker container, at a glance in your menu bar. Open, restart, or kill any of them without touching the terminal.<br>Download free trialBuy for $19.99

macOS 14+·Apple Silicon & Intel·7-day free trial

Tue 9:41 AM<br>:p0rt5 servers5 servers<br>checkout-api<br>~/Development/checkout-api

:3000node0.4%41 MB2h 4m<br>:5432postgres:16container2h 4m<br>:6379redis:7container2h 4m<br>moss-atlas<br>~/Development/moss-atlas

:5173vite0.2%36 MB1h 18m<br>tin-canary<br>~/Development/tin-canary

:5199node0.1%31 MB4h 12m<br>Filter servers…

Your whole stack. One glance.

the daily questions<br>Your development environment shouldn't be a mystery.<br>None of these questions are hard. They’re interruptions. p0rt answers all of them in one glance.

~ every morning<br>?Is Postgres still running?<br>?What's using port 3000?<br>?Did I stop that vite server yesterday?<br>?Which Compose stack is up?<br>?What did my agent leave running?

the promise<br>Awareness. Speed. Flow.<br>awareness<br>Always know what's running.<br>Every dev server, every container, every project. One glance at the menu bar replaces the guessing.

speed<br>One click instead of six commands.<br>Open, restart, or kill any server right where you see it. No lsof, no docker ps, no hunting PIDs.

flow<br>Stay focused. Keep building.<br>No Terminal detours, no Docker Desktop, no context switches. Checking your stack stops being a task.

01 / notice · awareness<br>Catches what you forgot.<br>Your AI agent spins up a dev server and moves on. You never see it, but p0rt does: the menu-bar icon lights up the moment an unfamiliar server starts listening, even with the panel closed.

context-window-rebuild0.0% · 33 MBNEW<br>~/Development/context-window-rebuild<br>:3002node8s

02 / stop · speed<br>Kills the server, never your session.<br>One click ends the whole npm run dev tree, every child process included: a graceful SIGTERM first, then Force if it won't budge. Your shell, your editor, your Claude Code session? Never touched.

pocket-prophet0.2% · 31 MB<br>~/Development/pocket-prophet<br>:3001nodeStop this server?KillForce

03 / everywhere · flow<br>Lives in Notification Center.<br>Nothing else puts your dev servers in Notification Center: the same list, the same one-click open and kill, without even reaching for the menu bar.

:3000cedar-sandbox1d 17h<br>:5199otter-deck21h<br>:8080coastline.dev49m

04 / triage · flow<br>Find the hog.<br>Live CPU and memory, in real megabytes, per server. An energy badge flags anything running hot, and when two projects grab the same port, you see it in red.

legacy-dashboard92.4% · 512 MBHigh<br>~/Development/legacy-dashboard<br>:3000node vite6d 2h<br>Port :3000 · legacy-dashboard + storefront

05 / focus · awareness<br>Only your project servers.<br>A process shows up only if it's listening on a real port from a project folder in your home directory. No system noise, no editor helpers. Grouped by project, sorted six ways, and searchable.

moss-atlas<br>tin-canary<br>~/Downloads/experiments

06 / docker · speed<br>Your Compose stack, in the same list.<br>Run docker compose up and the containers land right under the project that started them — Postgres, Redis, the lot. Same one-click stop, except p0rt sends docker stop: only the container goes down, never Docker itself.

checkout-api0.1% · 41 MB<br>~/Development/checkout-api<br>:3000node2h 4m<br>:5432postgres:16container2h 4m<br>:6379redis:7containerrestarting…

07 / keyboard · speed<br>All keyboard, no mouse.<br>Open p0rt from any app with a global shortcut — ⌘⌥P out of the box, or set your own in Settings. Then stay on the keys: ↑↓ to move, O to open, R to restart, K to kill. Your hands never leave the keyboard.

checkout-api0.1% · 41 MB<br>~/Development/checkout-api<br>:3000nodeORK<br>:5173vite1h 18m<br>↑↓navigate·⌘⌥Popen anywhere

why p0rt exists<br>Terminal is amazing. Opening it fifty times a day isn't.

Every check is a context switch, and every context switch costs attention, the most valuable resource a developer has. p0rt exists so checking your development environment takes one click instead of six commands. Spend your attention on building.<br>skip to the price ↓

WHAT DEVS SAY<br>Don't take our word for it.<br>I didn't realize how often I switched back to Terminal just to restart a server until I installed p0rt.<br>Andy · Full-stack Developer

One of those tiny utilities that quietly saves you dozens of clicks every day.<br>Daniela · iOS Engineer

everything it does<br>The whole list, no asterisks.<br>Detect<br>Port-first detection<br>Grouped by project<br>Docker containers, grouped<br>New-server menu-bar alert<br>Port-collision highlighting

Act<br>Open in browser<br>Copy localhost URL<br>Reveal in Finder<br>Restart a server<br>Graceful kill (SIGTERM)<br>Force kill (SIGKILL)<br>Stop all in a project

At a glance<br>Live CPU & memory (MB)<br>Energy-impact badge<br>Uptime<br>Process ID

Organize<br>Grouped or flat view<br>Sort by activity, port, CPU, memory, uptime, name<br>Live search<br>Hide, ignore ports & watch folders

Keyboard<br>Global hotkey (⌘⌥P)<br>Customizable shortcut<br>Arrow-key navigation<br>Open,...

server p0rt development docker port never

Related Articles