Guardian RMMPer device

Install it and it already knows

Guardian RMM discovers what is actually running on every machine, builds the checks itself, and attaches an action that can fix each one. Then it asks your permission before it does.

found on this host — web-03
ext4 / 412 GB → check disk_root + action vacuum_journal
TLS expires in 54 days → check cert_expiry + action renew
link up · 1 Gb/s → check link_state
SMART healthy → check smart_status
58 detection plugins · a check per real resource

“web-03 is out of disk, sort it out”

Ask for what you want in plain language. Guardian Plus plans the work, shows you the plan, and executes it step by step — the objective, each task, its risk level and the exact command before it runs.

the plan
$ du -xh /var --max-depth=2 | sort -rh | head -20
find what is using the space · risk: none
$ journalctl --disk-usage
check journal size · risk: none
$ journalctl --vacuum-size=200M
vacuum journal to 200M · risk: low · needs approval
$ df -h /
verify space recovered

Three ways to be in control

Approve every step. It stops and asks before anything that carries risk. The default, and where most people stay.

Approve the plan once. Read the whole plan, approve it once, then let it work through the list.

Unattended. For work you scheduled and already trust. The destructive floor still applies.

Get on the box

A real shell — a genuine PTY on the far end, not a command runner — and full remote desktop for Windows, macOS and Linux. No SSH client, no VPN, no RDP gateway, and no inbound firewall rule on the endpoint.

A real terminal

Browser-based terminal and remote management — a genuine PTY, no SSH client or VPN needed. Every session audit-logged: operator, host, mode, start and stop.

Remote desktop

Windows, macOS and Linux in the browser, with multi-monitor and consent prompts. Works through the same outbound socket as everything else.

Credentials never shown

Pulled from Guardian Vault and injected server-side. The plaintext never reaches the browser — a technician connects without ever being shown the password.

The things you can’t install on

Switches, firewalls, printers, appliances, anything embedded. Promote one agent on that network to a collector and it watches the rest from the outside. What that does and doesn’t get you, since the difference matters:

A collector can
Those need the agent installed
Tell you whether it is up, and page you when it is not
Read CPU, memory, disk or process detail from inside
Watch ports, HTTP endpoints, SSH and NRPE
Inventory its hardware or installed software
Poll it over SNMP and receive its traps
Run a script or push a file to it
Scan it for vulnerabilities from the network
Open a terminal or remote desktop session on it
Map what it is plugged into, via LLDP and CDP

Security that lives where the alert does

Vulnerability scanning, endpoint protection and containment run in the same console as the monitoring — so the alert, the CVE and the isolate button are one click apart.

Vulnerability scanning

Findings enriched with CVSS, exploit-prediction scoring and the CISA known-exploited list, tracked across rescans so you can see what you actually fixed. Agents scan themselves in depth; agentless targets are scanned across the network, which is shallower.

Endpoint protection

Run Bitdefender GravityZone from this console — deploy agents, triage detections, quarantine and blocklist, with per-client credentials. Requires your own GravityZone tenant; isolation and blocklisting need its EDR module.

Isolation you can rehearse

Before cutting a machine off, see the exact firewall rules, the preflight checks and the rollback path. Apply it and it reverts itself unless you confirm. Most tools isolate blind.

Alerts that don’t lie to you at 3 am

A rebooted server used to mean forty emails. A host whose network flaps used to mean a hundred. Guardian RMM was built by people who got those pages at 3 am, and it suppresses the noise on purpose — and every suppression is recorded with its reason, so you can always answer the harder question: why didn’t this page anyone?

Flap damping

A host bouncing up and down gets damped, then announced once with its real outage duration.

Recovery bursts held back

When a box comes back, its checks do not each mail you their own recovery notice.

Silence detection

A check that simply stops reporting is treated as a problem, not as passing.

Quiet hours and rate limits

Per tenant, with critical alerts able to break through. Six ways to be told: email, SMS, Slack, Microsoft Teams, Discord and webhooks, with time-delayed escalation.

Runs where you run

Windows — server and desktop, 64-bit, MSI servicemacOS — Intel and Apple Silicon, monitors with nobody logged inLinux — Ubuntu 22 / 24, Rocky 9 / 10, CentOS Stream 9, SUSE 16Nagios plugins + NagiosQL importOS patching by category with reboot policy

Deployments are sized to your estate. Tell us how many endpoints you manage and where they sit, and we will tell you what that looks like.

Put it on one machine and watch

Install the agent on a single server. Within minutes it will have found what runs on it, built the checks, and told you something you didn’t know.

Read next

The alert-noise playbook

flap damping, recovery bursts, silence detection, quiet hours — and a checklist for your own monitoring. Read it

How many seams are you paying for?

ten yes/no questions, two minutes, your three most expensive seams. Open