Radar Dev Monitor · Local Dev Server Manager for Mac

What it does

Less tracking down. More building.

Your running projects

Know what’s running at a glance.

Keep your running projects in view as you move between tasks. Radar puts detected dev servers in one menu bar panel, with a separate card that makes each project easy to recognize.

Recognize each server, see its project, framework, and when it started.
Keep the essentials in view, choose a menu bar icon, server count, or count with total memory.

Three glowing servers and project folders organized on individual shelves within one amber frame.

Fits your workflow

Start your server. Radar finds it.

Keep working in your terminal, editor, or coding assistant. Radar discovers supported servers already running on your Mac, so there’s no special launch command to remember or new place to start your projects.

Recognizes familiar tools, including Next.js, Vite, Astro, Convex, Expo, and more.
Make room for your own stack, add custom detection profiles with matching rules, names, colors, and icons.
Find what’s outside the presets, optionally show other local TCP listeners and turn an unrecognized service into a custom profile.

An amber radar sweep discovers servers beside terminal, code, and development tool symbols.

Clean up

Done with a project? Stop its server.

A server can leave more running than the command you typed. Radar groups related launchers and workers into one server, so you can clear the processes behind a finished project from a single card.

Give it a clean shutdown, Radar asks the server to stop gracefully and escalates if it won’t exit.
Check before stopping, Radar refreshes which processes belong to the server and checks their identities before stopping them.
Finish a session in one action, use Stop All for a single cleanup across your monitored servers.
Handle a stubborn process, Option-click Stop to force it to quit.

One stop control connects to a parent server and three related worker processes.

Addresses and answers

Find the right port. Know what’s behind it.

A project can have a preview, an API, and supporting services on different ports. Server Details brings its addresses and process information together, so you can find the destination you need and understand what’s running behind it.

Choose your destination, inspect all detected listening addresses, select a port, and choose HTTP or HTTPS.
Keep the URL handy, open it in your browser or copy it into the tools you’re using.
Follow the process, see its executable, command, detection reason, and observed parent chain.
Get to the source, reveal the project folder in Finder when you need its files.

A server exposes ports 3000, 4321, and 8080, with port 4321 highlighted alongside browser and folder symbols.

Memory, CPU, and response

See what your servers are using.

When a project feels slow, inspect its live resource use and recent history. See which server is busy, how its memory use is changing, and check whether its selected address is responding.

See the whole server’s footprint, memory and CPU include the related processes grouped into its card.
Spot changes over time, short memory and CPU charts help you see rising usage or a burst of activity.
Check for a response, optionally enable an HTTP readiness check for the selected address and see its response status.

A server beside an amber memory history chart, a teal CPU chart, and a response check indicator.

A timely reminder

Catch the server you forgot about.

Yesterday’s prototype can keep running long after you’ve moved on. Let Radar bring long-running or memory-hungry servers back to your attention, with notifications you can tune to the way you work.

Choose when it’s been long enough, set a running-time threshold for forgotten-server alerts.
Get a heads-up on memory, choose the usage threshold that triggers an alert and how often it repeats.
Pause reminders on your terms, snooze a project for an hour or resume its alerts when you’re ready.
Go straight to the panel, click a notification to review your servers and decide what to stop.

A still-running server beside an amber clock, notification bell, and snooze symbol.

Your project, your rules

Keep the services you mean to keep.

A shared development service may need to stay running all day. An experiment may not belong in your everyday view. Decide which projects stay protected and which ones Radar should show, with choices remembered for each folder.

Protect a project from Stop All, leave it running during a cleanup and stop it individually whenever you choose.
Ignore and restore, hide a project from monitoring, then bring it back from the panel’s Ignored menu.
Set it once, project preferences stay with the folder across app and server restarts.

An amber shield protects one running project while another sits behind a frosted panel marked with a hidden-eye symbol.

The details

Specifications.

Requirements: macOS 26 or later
Compatibility: Apple Silicon and Intel Macs
Built-in detection: Astro, Convex, Next.js, Remix, Nuxt, SvelteKit, Expo, Vite, webpack, Bun, Deno, Rails, Django/uvicorn, PHP, Python HTTP, and Node servers
Networking: Local TCP listeners · IPv4 and IPv6
Scan cadence: Every 2 seconds with the panel open · 5, 15, 30, or 60 seconds in the background
Sleep and wake: Scanning pauses during sleep and refreshes after wake
Startup: Optional launch at login
Recent history: Up to 120 samples per server from the last 30 minutes

Questions

Good to know.

What does Background mean?

The server’s original parent process is no longer attached. This can be intentional, including when a coding tool starts a persistent dev server. It does not mean the server was abandoned. Server Details shows the parent chain Radar observed, when available, and identifies historical information.

Does the readiness check tell me my app is healthy?

It tells you whether the selected address returns an HTTP response and shows its status code. It does not test application behavior or diagnose errors. Checks are off by default. When enabled, they use a HEAD request at most once every 30 seconds, do not follow redirects, and do not bypass TLS errors.

Does Radar upload my project or process information?

Monitoring happens locally on your Mac, and the app has no telemetry. Project preferences are saved locally; recent resource history stays in memory. Enabling readiness checks sends requests to the server address you select. Opening a URL uses your browser as usual.

Can I use it to start servers or monitor a remote machine?

Radar focuses on finding and managing servers already running on your Mac. Start them in your existing development tools. Remote machine monitoring and hosting are outside its scope.

Get Radar Dev Monitor

Your next project deserves a clean start.

Keep track of the servers you need and clear the ones you’re done with. Coming soon for Mac, with pricing announced at launch.

Explore all Radar Apps