Open source
macOS app
Open source · MIT

Start it once. It keeps running.

A control room for your development servers, local or remote. They keep running after the terminal — or the coding agent — that started them. Drive it from the app or the CLI, watch every one live, and open or share any port it detects.

Apple silicon. Anything past your LAN — publishing a port, or pairing another Mac — goes over Tailscale.

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

One window. Every machine.

Hangar exists because a dev server should not die with the terminal that started it — and because finding the right one across a dozen windows got old. Everything runs in one place, and stays running.

Outlives the command

A server keeps running after the tab closes, the script ends, or a coding agent moves on. The CLI can wait until the port is genuinely listening, so an agent gets a real port instead of racing a log file.

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.

Your other Macs, one window

Pair a remote Mac over Tailscale — the connection is plain HTTP, so it wants a private network — and its projects join the same sidebar. Start something on the machine under your desk from the laptop on your lap.

Metrics, synced to output

CPU, memory and output rate every two seconds. Click a spike on the chart and jump to the log line behind it.

Ports, detected

Hangar finds listening ports across the whole process tree and keeps every one in a single list. One click opens them in the browser you choose.

Share it, or publish it

A LAN link, your own devices over Tailscale, or a public link anyone can open. Scan the QR from your phone. The Tailscale routes work even when the server only listens on localhost.

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

  1. 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.
  2. 2Start what you needLaunch one process or the whole project, from the app or the CLI — the same sessions either way. ⌘K searches every process, action, and archived run.
  3. 3Open it anywhereDetected ports open in your browser of choice — or share one: a LAN link, your own devices over Tailscale, or a public link anyone can open.

Built for the ten servers you run anyway.

Free and open source under MIT. macOS builds ship with every release, and the CLI is on npm.