Every dev server. One window.
Every project's dev servers in one place. Find any process in seconds, start exactly what you need, and open or share any port it detects. No more hunting through terminal tabs.
hangar
client-web2/3
- web
- api
- worker
$ pnpm dev
ready in 812 ms
listening on http://localhost:3000
compiled /products in 240 ms
lan · http://192.168.1.24:3000
What it does
The control room for localhost
Hangar exists because finding the right dev server across a dozen terminal windows got old. Everything lives in one place — find it, start it, in seconds.
Start what you need
Register a project and launch one process or all of them. ⌘K finds any of them in seconds. Nothing runs unless you ask.
Live resource usage
CPU, memory and output rate, sampled every two seconds. High CPU gets flagged before your fans do.
Metrics, synced to output
Click a spike on the chart and jump to the log line behind it. Select output and see when it happened.
Ports, detected
Hangar finds listening ports across the whole process tree. One click opens them in the browser you choose.
Share over LAN or Tailscale
Copy a link your phone can open. If the server is bound to loopback only, Hangar says so — and tells you the fix.
History, opt-in
Archive finished runs, replay their output, rewind their resource timeline. Off by default. Everything stays on your disk.
hangar
client-web2/3
- web
- api
- worker
$ pnpm dev
ready in 812 ms
listening on http://localhost:3000
How it works
From folder to running
- 1Add a projectPoint Hangar at a folder you already have — nothing is cloned or copied. It reads package.json, finds your scripts, and detects the package manager.
- 2Start what you needLaunch one process or the whole project. ⌘K searches every process, action, and archived run.
- 3Open it anywhereDetected ports open in your browser of choice — or copy a LAN or Tailscale link and open it on your phone.
Built for the ten servers you run anyway.
Free and open source under MIT. macOS builds ship with every release.