Radar Dev Monitor · Tomita Tech

What it does

Every dev server, in one place.

The panel

A panel, not a menu.

Click the radar icon and a real panel opens, one card per running server, not a flat list of text. Each card shows the framework, project name, localhost:PORT, how long it’s been running, and live memory and CPU.

One card per server, name, tool, address, and running-since at a glance.
Live memory & CPU updated while the panel is open.
Click a row to open it in your browser; right-click for more.
Orphaned servers wear a badge so forgotten processes can’t hide.

Server panelLive cards · 1600 × 1200

Tree-aware kill

Stop the whole server, not just the child.

npm run dev, its server, and the oddly-named workers it spawns all belong to one thing. Radar Dev Monitor groups them and stops them together, gracefully first, forcefully only if it has to.

Graceful by default, SIGTERM first, with exits confirmed at the kernel.
Escalates only if needed, SIGKILL for anything that won’t stop.
Stop All clears every server at once, concurrently.
⌥-click to force-kill when you want it gone immediately.

Stopping a serverTree kill · 1600 × 1200

Featherweight

Lighter than the servers it watches.

A resource monitor that wastes resources is self-defeating. Radar Dev Monitor asks macOS directly for what it needs, it never shells out to lsof or ps, and never spawns a process to watch your processes.

0.05% idle CPU and about 16 MB of memory.
Zero process spawns while monitoring, pure native syscalls.
Suspends on sleep and screen lock, rescans the moment you’re back.
Menu-bar only, no Dock icon, no window to manage.

FootprintActivity Monitor · 1600 × 1200

Under the hood

How native detection works.

Step 01

Ask macOS directly

One syscall lists every process; a cheap name pre-filter keeps only the candidates worth inspecting. No shelling out, no spawning, the work is done in microseconds.

Step 02

Find the listeners

For each candidate, Radar reads its open sockets and keeps the ones in LISTEN state, that’s the port. The command line names the framework; the working directory names the project.

Step 03

Group the tree

Parent and child processes are stitched back into one logical server, so npm run dev and its workers show up once, with honest, combined memory totals.

The details

Specifications.

Requirements

macOS 26 (Tahoe) or later

Compatibility

Apple Silicon & Intel Macs

Detects

Next.js, Vite, Astro, Remix, Convex, webpack, Bun, Deno, Rails, Django, PHP & custom

Footprint

~16 MB memory · 0.05% idle CPU

Privacy

Collects nothing · no telemetry

Notifications

Forgotten-server & memory-threshold alerts

Buy once. Yours for good.

No subscription, no account tax. A single purchase covers up to five of your devices, with free point updates as Radar Dev Monitor grows.

Radar Dev Monitor

$12One-time

Lifetime license, no subscription
Install on up to five devices
Free point updates
30-day money-back guarantee

Buy Radar Dev Monitor

Secure checkout · instant download

Questions

Good to know.

Out of the box: Next.js, Vite, Astro, Remix, Convex, webpack-dev-server, Bun, Deno, Rails, Django/uvicorn and the PHP built-in server. You can edit those profiles or add your own, and switch on a catch-all that surfaces anything else listening on localhost.

No, that’s the whole point. It asks macOS directly for process and socket information instead of shelling out, so it sits at around 0.05% idle CPU and 16 MB of memory, and spawns no processes while monitoring. It even suspends entirely while your Mac sleeps.

Yes. Radar Dev Monitor groups a server with the parent that launched it and the workers it spawned, then stops the whole tree, a graceful SIGTERM first, with exits confirmed at the kernel, escalating to SIGKILL only for anything that refuses. ⌥-click force-kills immediately.

No. The app collects nothing and has no telemetry. It reads process information locally on your machine and only reaches the network to check for updates and validate your license.

Yes. It can notify you when a server has been running longer than a threshold you set (8 hours by default) or when one crosses a memory limit, so the 4 GB server you forgot about last night doesn’t stay forgotten.

macOS 26 (Tahoe) and later, on both Apple Silicon and Intel Macs. Updates are delivered automatically, signed and notarized by Apple.