Guardian is BRUTAL Optimizer's background automation engine. Instead of you opening the app and clicking buttons before every gaming session, Guardian runs quietly inside BRUTAL, checks your system every 3 minutes, and applies the right tweaks the moment it sees a game or emulator launch — then puts everything back the way it was when you finish playing. It starts for everyone; the deep optimization engines need Pro.
Plenty of "optimizers" install a mystery service that runs forever and never tells you what it touched. Guardian is the opposite, and on purpose. It is pure C# code running inside the BRUTAL app itself — there is no separate Windows service, no scheduled task, and no hidden PowerShell or VBS scripts. If BRUTAL is open (even minimized to the system tray), Guardian can run. If you close BRUTAL completely, Guardian stops too. Everything it does is written to a plain-text log you can read at any time.
BRUTAL_Guardian plus .ps1/.vbs launcher files. The current Guardian replaces all of that. On first launch BRUTAL automatically deletes those legacy leftovers — you don't have to do anything.Guardian runs on a simple timer. Once started, it fires its first cycle after about 5 seconds, then repeats every 3 minutes. Each cycle is one quick pass through a set of single-purpose checks (the "engines"). A cycle never overlaps with the previous one — if a cycle is somehow still finishing, the next tick is skipped, so Guardian can't pile work on top of itself.
The single most important thing Guardian does each cycle is detect whether you are actually gaming. It looks for known Android emulators (GameLoop, BlueStacks, LDPlayer, Nox, MEmu, MuMu) and for known native PC game processes. The aggressive optimizations only switch on when a real game is detected — an idle emulator window sitting on your desktop does not trigger them.
On every tier, Guardian detects the game — which is what lights up the FPS tile, the overlay and Smart Route's server detection — and can show the FPS overlay automatically. On Pro, when it confirms a game is running, a typical cycle will also:
DiagTrack, DiagSvc, DPS) for the session.For details on the chat/launcher tuning, see The Guardian engines explained.
This is the part most optimizers get wrong. Guardian's tweaks are session-scoped and reversible. When the game closes, the next cycle:
Guardian starts for everyone. Detection, app-update and junk checks, Defender status, scheduled auto-clean and idle service restore run on Free; the deep optimization engines need Pro. It auto-starts when the app launches, so for most people there's nothing to do — just leave BRUTAL running (minimized to the tray is fine) and play. If you ever want to start, stop, or trigger it by hand, open the Guardian page in the sidebar and use the buttons there. The full walkthrough is in Turning Guardian on/off and reading its log.
Does Guardian install a Windows service or scheduled task?
No. Guardian is C# code running inside the BRUTAL app itself. There's no separate service, no scheduled task, and no scripts. It only runs while BRUTAL is open (the tray counts as open). Older versions did use a scheduled task and PS1/VBS files; the current app deletes those automatically on first launch.
Will Guardian's changes survive a reboot or stick around after I stop a game?
No, and that's by design. Guardian's gaming tweaks are session-scoped. When the game closes it reverts the native optimizations, restarts any services it stopped, and restores demoted apps to Normal priority. Stopping Guardian or closing BRUTAL also reverts the session changes.
Is Guardian free?
Guardian starts for everyone. Detection, app-update and junk checks, Defender status, scheduled auto-clean and idle service restore run on Free; the deep optimization engines need Pro. The Free tier still gives you the whole manual toolbox; what Pro adds is the automatic tuning Guardian applies once a game is detected, including the deep native runtime tuning.
Does Guardian touch my system when I'm not gaming?
Only lightly. When no game is detected it reverts gaming tweaks and does slow-cadence housekeeping: app-update and reclaimable-space checks, a Defender status check and an optional scheduled safe junk clean (off by default) on every tier, plus a daily driver-update check and a low-RAM working-set trim on Pro. It never trims memory or cleans junk while you’re actually gaming.