Your machine is part of your development environment.

A dev server can spawn a parent Node process, a compiler, and several workers. RamBeacon's application grouping shows the family's aggregate memory and CPU, while Dev Servers lists the listening ports and inferred stack so you can identify the project before stopping anything.

• Application-family grouping
• Listening-port inventory
• Approval-bound stop

Browser processes, Electron helpers, Node APIs and Mongo tooling can dominate memory without looking related in a flat table. Grouping and the process relationship forest make the family visible, and the memory investigation view helps you find sustained growth.

• Parent-child evidence
• Memory-growth signals
• Watchlist thresholds

Metro, Gradle, Dart, adb and emulator processes are all part of a mobile workflow. RamBeacon identifies listening dev ports and groups by project folder evidence. It does not claim to debug your app; it helps you see what the toolchain is doing to the machine.

• Metro / Gradle / adb visibility
• Project-folder grouping
• Port-conflict hints

Extension hosts, language servers and terminal children are frequent contributors to memory pressure. Process details show the parent-child relationship and classification evidence, so you can distinguish the editor from a runaway extension helper.

• Extension-host families
• Identity-bound actions
• Protected-process policy

RamBeacon observes Windows processes and ports exposed by Docker Desktop and WSL. It does not inspect container internals, read Docker configuration, or modify WSL distributions. Those limits are stated in the app rather than hidden behind a claimed integration.

• Windows-side process visibility
• No container-internal claims
• Honest unavailable states

Model runtimes and local inference servers can hold significant memory for long periods. Track their process families and compare resource history. Optional AI explanations in RamBeacon use minimized metadata and cannot execute system actions.

• Long-running process tracking
• Optional AI annotations
• No model authority

node_modules, .next, dist, coverage and caches accumulate across projects. Developer Cleanup scans folders you explicitly select, detects known artifacts, and lets you review a storage map before moving approved targets to the Recycle Bin.

• Known-artifact rules
• 2D / 3D storage map
• Recycle Bin only

MongoDB, Redis, Postgres and local queues appear as ordinary Windows processes. RamBeacon can show their resource history and relationships, but it does not connect to their databases, run queries, or manage their data.

• Resource history
• Startup impact review
• No database access