Learn / RMM basics

What is remote monitoring and management (RMM)?

Video guide: Use the RMM introduction and find the first-device guide

Documentation navigation recorded October 22, 2026. Public introductory navigation; no endpoint enrollment or product acceptance test.

Video transcript

Open the public What is RMM guide. Remote monitoring and management brings endpoint information and technician workflows together. A dashboard is useful only when its data is fresh, correctly scoped and backed by evidence of the work performed.

Open the first-device guide to see the initial operational sequence: find the workspace, sign in, choose the customer, prepare enrollment and verify later reporting. Each stage has its own failure modes; downloading an installer alone is not successful management.

Return to the introduction and choose the next Learn guide for your intended task. Use a permitted pilot endpoint, verify actual outcomes and retain recovery evidence. This is an introduction to the documentation, not a demonstration that every capability is configured or accepted.

RMM software puts a small agent on every computer and server you manage, then gives your team one console to watch their health, fix problems remotely, keep them updated and prove what was done. This guide explains the category in plain language, with no assumed background.

Definition

What RMM software does.

Remote monitoring and management grew out of a simple problem: an IT team responsible for hundreds or thousands of machines cannot walk to each one, and cannot notice a failing disk or a missing update by hand. The agent on each device reports its state continuously, and the platform turns those reports into work: alerts when something crosses a threshold, update deployments when patches are missing, remote sessions when a person needs to look, and records of all of it.

The practical test of any RMM is whether an issue keeps its context. A disk alert is only useful if it arrives attached to the device, the customer or department it belongs to, and the history of what was already tried, so the person picking it up can act instead of investigating from zero.

Who uses it

Built for MSPs. Useful for internal IT.

The category was shaped by managed service providers, but the mechanics serve any team responsible for machines it cannot physically reach every day.

Capability areas

The core capability areas.

Vendors bundle these differently, but a full RMM platform covers most of the following. Descriptions here are generic to the category, not a feature list for any one product.

Evaluation

What to evaluate in any RMM.

Feature checklists converge quickly in this category. The durable differences show up in four places.

Good to know

Common questions about RMM.

No. Remote desktop is one capability inside RMM. An RMM platform also watches device health continuously, deploys operating-system updates, runs scripts and keeps an inventory, whether or not anyone is connected to the screen.

The value shows up earlier than most teams expect. Even at fifty machines, checking update status or disk health by hand stops happening in practice. An RMM makes those checks continuous and turns misses into alerts.

RMM manages computers and servers through an installed agent with deep access to the operating system. MDM manages phones and tablets through the enrollment frameworks Apple and Google provide. Many platforms, ours included, do both from one console.

Usually not. Most RMM platforms report on the protection state of each device and integrate with security vendors rather than replacing them. Ask any vendor exactly where their monitoring ends and your security tooling begins.

It reports inventory and health readings on a schedule, raises alerts when a threshold is crossed, and carries out the actions a technician or policy sends it, such as installing an update or running a script.

Our approach

How Revolutionary RMM does this.

Revolutionary RMM is one workspace covering the capability areas above: monitoring, patching, remote control, automation, network monitoring, identity signals, service desk and documentation, built for MSPs and usable by internal teams as a single tenant. The design center is the context test from this guide: an issue keeps its device, customer and history from the first alert to the invoice.

We publish what is not built yet on our roadmap, and the platform page counts its capability areas from the product source code rather than marketing copy, so you can evaluate us the way this guide suggests evaluating anyone.

Evaluating RMM platforms?

Bring one workflow your team runs every week. Half an hour on a call, in the product, no slides.