RMM · The fundamentals
RMM stands for remote monitoring and management: software that MSPs and IT teams use to monitor, manage, patch, and support computers remotely, from one central console. This guide explains what an RMM actually does, who uses one, how it fits with a PSA, and what to look for when you evaluate one.
Definition
RMM stands for remote monitoring and management. An RMM platform is software that lets a small team of technicians watch and control a large fleet of computers (workstations, servers, and often network devices) without physically touching any of them. A lightweight agent on each device reports its state back to a central console; from that console, technicians see alerts, push patches, run scripts, and open remote sessions.
The term comes from the managed services industry. An MSP might be responsible for thousands of devices spread across dozens of client offices; visiting each machine is impossible, so the RMM is the tool that makes the business model work. Internal IT departments adopted the same software for the same reason: employee laptops are scattered across offices and home networks, and the team managing them is small.
You will see "RMM software," "RMM tool," and "RMM platform" used interchangeably. They all describe the same category, and this page uses them the same way.
Core capabilities
Every RMM is built around the same core loop: an agent on each device, continuous monitoring, and remote tools to fix what the monitoring finds. Six capabilities make up the job.
A small background service installed on every managed device. It reports the machine's state back to the central console and carries out instructions: run this script, install this patch, open a remote session. Everything else an RMM does flows through the agent.
The agent continuously watches CPU, memory, disk space, running services, and event logs. When something crosses a threshold (a disk filling up, a backup service that stopped), the RMM raises an alert so a technician knows before the user calls.
Operating system and third-party application updates, applied on a schedule across the whole fleet instead of machine by machine. A good RMM shows you what is patched, what is pending, and what failed, per device and per client.
Run a script on one machine or a thousand at once: PowerShell, Bash, or whatever the platform supports. Automations chain this together, so routine fixes (clear a cache, restart a service, free up disk space) happen without a human touching each device.
Remote desktop and terminal access into any managed machine, from the same console. When monitoring and automation are not enough, a technician connects directly and works the problem as if sitting at the device.
A live record of every managed device: hardware specs, installed software and versions, serial numbers, and warranty status. Inventory is what turns "how many machines still run that vulnerable app?" from a week of legwork into a query.
Who uses it
Two groups, one problem: more machines than people to manage them.
MSPs manage IT for many client businesses at once. The RMM is their central nervous system: every client's devices in one console, organized by site, with monitoring policies and patch schedules applied per client. The economics of an MSP depend on one technician handling hundreds of endpoints, and the RMM is what makes that ratio possible.
How MSPs use Breeze →A three-person IT team supporting a few hundred employees faces the same math as an MSP, just inside one company. Remote and hybrid work made the walk-over-and-fix-it model obsolete: the laptop with the problem is in someone's kitchen. An RMM gives internal teams the same visibility and reach across every employee device, wherever it is.
How internal IT uses Breeze →RMM vs PSA
RMM is often mentioned alongside PSA, and the two are easy to confuse. The split is simple: the RMM manages the machines, the PSA manages the business. PSA stands for professional services automation, and it covers tickets, time tracking, quotes, contracts, and invoicing: the paperwork side of running an IT service operation.
The two work as a pair. The RMM detects a failing disk and raises an alert; the PSA turns that alert into a ticket, tracks the technician's time fixing it, and bills the client for the work. Historically these were separate products from separate vendors, wired together with integrations. Some modern platforms combine them: Breeze, for example, ships RMM and PSA in one system, so tickets, quotes, and invoices live next to the devices they refer to.
Where it's heading
Traditional RMM automation is rule-based: if X happens, run script Y. That handles the predictable failures, but everything else still lands on a technician who reads the alert, investigates, and decides what to do. The newest shift in the category is AI that does that investigation itself: correlating signals across the fleet, working out what is actually wrong, and taking or proposing the fix under governance rules a human sets.
This matters because monitoring was never the hard part; acting on the monitoring was. If you are evaluating platforms in 2026, it is worth understanding this shift before you buy. Our guide to AI RMM defines the category and lays out what to demand from any vendor claiming it, including the approval gates and audit trails that make AI on a fleet safe.
Open source vs commercial
Most RMM platforms are commercial and closed source, priced per device or per technician and hosted by the vendor. A smaller set of platforms are open source: the code is public, you can audit exactly what the agent does on your machines, and you can self-host the whole platform with no licensing fees. That trade matters more for RMM than for most software, because the agent runs with administrative privileges on every device you manage.
Commercial platforms buy you vendor-run infrastructure and support SLAs; open source buys you auditability, no per-device fees, and freedom from lock-in, at the cost of running the server yourself. Our open source RMM guide compares the leading projects and covers what self-hosting actually involves.
Evaluation
The category is crowded and the demos all look alike. Four things separate platforms in practice.
Platform coverage
Does it manage all the operating systems in your fleet (Windows, macOS, Linux), and does every capability (monitoring, patching, remote access) work on each of them, or only on Windows?
Depth of the core four
Monitoring, patching, scripting, and remote access are the job. Demo each one against your real environment, not the vendor's demo tenant.
Automation, not just alerts
An RMM that only tells you something broke still leaves all the work to your team. Look for automation that resolves routine issues on its own, and increasingly, for AI that can investigate and act under governance.
Pricing model and lock-in
Understand what you pay as the fleet grows, what happens at contract renewal, and how hard it is to leave. Per-device pricing scales linearly with your fleet; self-hosted open source mostly does not.
When you are ready to look at specific platforms, our comparison pages put Breeze side by side with the major commercial and open source options, and the pricing page shows how the models differ in practice.
Quick answers to the questions people ask most often about RMM.
RMM stands for remote monitoring and management. It refers to software that MSPs (managed service providers) and internal IT teams use to monitor, manage, patch, and support a fleet of computers from a central console, without physically visiting each device. "RMM software," "RMM tool," and "RMM platform" all mean the same thing.
No. RMM (remote monitoring and management) deeply manages servers and workstations: monitoring, patching, scripting, and full remote control, typically on Windows, macOS, and Linux. MDM (mobile device management) manages device policy on phones and tablets: enrollment, app deployment, configuration profiles, and remote wipe. The categories overlap at the edges, and many teams run both: an RMM for computers and servers, an MDM for mobile devices.
An RMM agent is a small background service installed on each managed device. It reports the machine's health and inventory back to the central RMM server and executes instructions sent from the console: running scripts, installing patches, or opening a remote access session. Because the agent runs with administrative privileges, it is worth knowing exactly what it does, which is one argument for open source RMM platforms where the agent code can be audited.
Commercial RMM is usually priced per device (a monthly fee for each managed endpoint), per technician, or as a flat platform fee, often with annual contracts and minimums. Costs scale with fleet size under per-device models, which is why pricing becomes a bigger factor as you grow. Open source RMM platforms take a different approach: Breeze, for example, is AGPL-3.0 licensed and free to self-host with no per-device fees, so your cost is the server you run it on. See the Breeze pricing page for how its cloud and managed tiers work.
No. RMM grew up in the MSP industry, but internal IT departments use the same software to manage employee workstations and servers across offices and remote workers. Any team responsible for more machines than it can walk to benefits from the same core loop: monitor everything, patch on schedule, automate the routine fixes, and remote in for the rest.
About Breeze
This guide is published by the team behind Breeze, an open source RMM with 64 modules, a built-in PSA, and an AI operator that works the fleet under a risk engine you control. It is AGPL-3.0 licensed: self-host it for free with no per-device fees, or use the managed cloud beta. We build an RMM, so read the vendor-neutral sections above with that in mind.