Every process. The full picture.
List, Tree or Apps views. Searchable columns, live values and an inspector that stays out of your way.
See what’s running. Understand what’s slowing you down. Give your important apps room to breathe.
A native Windows task manager and configurable background governor. Built in Rust. Put to work by you.
From a busy processor to a runaway build,
go from “what’s happening?” to “I’ve got this.”
List, Tree or Apps views. Searchable columns, live values and an inspector that stays out of your way.
CPU, memory, GPU, disk and network. A shared timeline with real timestamps and explicit sampling gaps.
A background governor with staged CPU protection, memory guard and per-app budgets. You choose when it acts.
Processes has Process Explorer's Find handle or DLL, the magnifier at the end of its toolbar: every process with a file, registry key or other object open, or a DLL loaded, whose name contains the text (three characters or more). Processes are searched one at a time with this window's own rights and the Handles view's limits, and hits arrive as each is done; Stop ends the search, and it stops by itself at 1,000 hits or after a minute. The window says how many processes could not be opened and in how many names were not all read, so that no hits never claims more than was searched. Clicking a hit shows the process in the inspector, unless it has exited since. lsass.exe and lsaiso.exe are never opened.
The Memory map names what a process keeps in its private memory: its heaps (the default one marked), each thread's stack and TEB, and its PEB, with the 32-bit copies of a 32-bit process marked as such, and totals the memory of its heaps and stacks. Stacks and TEBs come from the threads' own records and the default heap from the PEB; other heaps, which the PEB does not list completely on every Windows build, are known by the signature in their header. Only those pointers and signatures are read, never other memory, and only from processes that allow reading their memory; the others still get the full map, with a note that these names are missing. Large blocks a heap allocates on their own are not named.
The process inspector has System Informer's Windows list: the process's top-level windows on this desktop with their title and class, visible ones first, hidden ones on request, and "Not responding" on a visible window that has stopped answering. Switch to restores a minimized window and brings it to the front without keeping it on top, and says when Windows keeps the focus elsewhere or the window has closed. Each window must belong to one of the process's threads, so a newer process with the same PID never inherits the list, and nothing is sent to the windows while they are listed, so a hung one cannot stall it. Titles often name documents, mails or web pages: they are shown, never logged.
One application. A view for every question.
Explore the real interface, screen by screen.
Swipe to explore every view
The processes workspace in RustWTM v0.34.0. Actual application render with example data.
Background work should know its place.
When sustained load crosses your thresholds, the governor can lower priority, enable efficiency mode and apply CPU caps in stages. Your foreground app and its children stay protected by default.
Dry-run records automatic decisions. Review Events and tune your configuration before enabling enforcement.
Match processes by name or path. Add sustained CPU, memory or GPU conditions, and define per-app budgets.
The governor rolls its process adjustments back after recovery. Shared Windows power-plan settings have their own restore behavior.
Dry-run affects automatic enforcement. Manual GUI and CLI actions still execute and may require administrator rights.
Read the configuration guideAutomatic decisions are logged, without applying process changes.
An explanation of the service. This website does not monitor or change your PC.
See what’s listening and which program owns it. Inspect per-process traffic and connection details; elevated tracing unlocks deeper network visibility.
Explore the docsLocal Docker statistics, health, Compose projects and bounded logs. Read-only monitoring, with no remote daemon exposure required.
Explore the docsShare CPU and memory budgets across an app and its child processes. Track long-term per-app usage and investigate suspected resource leaks.
Explore the docsStartup apps, Windows services, users and disk analysis. Read supported hardware sensors with the optional provider; cooling control varies by device.
Explore the docsList, inspect and control processes from the CLI. Export JSON or connect an MCP client over standard input/output; control is an explicit opt-in.
Explore the docsThe local service accepts control from elevated administrators. Core Windows processes, critical processes and RustWTM itself are protected.
Explore the docsGive background workers an app budget. Find the process holding a development port, and monitor your local Docker stack alongside Windows.
Foreground protection keeps configured governor actions away from the app you’re using. Game mode can adjust background priority and restore it afterward.
Inspect wait chains, loaded modules, usage history and diagnostic events. Understand a hung app before choosing a manual action.
wtm list --sort mem -n 20
wtm ports --known
wtm history --hours 24Commands run locally after installing RustWTM. These examples are not executed by this website.
Free. Open source. Ready for Windows.
An early-release project. Test protection settings with your workloads. Sensor and cooling support depends on your hardware.
Yes. RustWTM is open source under the MIT license, including for commercial use. You can inspect, modify and contribute to its source on GitHub.
Windows 10 version 1809 or later and Windows 11, on x64 systems. The current release provides an x64 MSI installer and an x64 portable ZIP. An ARM64 package is not published.
Automatic enforcement starts off in dry-run mode: decisions are recorded without applying automatic process changes. Manual commands from the GUI or CLI still execute. Review Events before switching to enforcing mode.
Read-only monitoring can run as a regular user. Installing the service and performing privileged actions requires administrator rights. Per-process network and file tracing use the service or an elevated window. Some protected processes remain inaccessible.
An optional setting can route Ctrl+Shift+Esc and other Task Manager entry points to RustWTM. It requires administrator rights and a protected installed copy. Turn it off to restore Windows Task Manager; portable and development copies cannot enable it.
It monitors a supported local Docker Engine context through a Windows named pipe. Container statistics, health, ports and bounded logs are read-only. It does not start, stop, restart or modify containers, and does not support remote contexts.
The desktop interface and notifications are available in 27 languages, including English, Türkçe, Deutsch, Español, 日本語 and 简体中文. The default follows Windows, with English as a fallback. Choose a language in Settings → This window.