RMM · The fundamentals

RMM vs MDM

Both manage devices remotely, and the acronyms differ by one letter, so they get confused constantly. They solve different problems in different ways. This page explains what each one does, how they differ, and how to tell whether you need one, the other, or both.

The short answer

RMM (remote monitoring and management) operates computers and servers. MDM (mobile device management) governs phones, tablets, and device policy.

An RMM installs an agent on each machine so technicians can monitor it, patch it, run scripts, and take remote control. An MDM enrolls a device through the operating system's own management framework so IT can push settings and apps, enforce security policy, and wipe the device if it is lost. Teams with both computers and mobile devices usually run both. New to the first half? Start with What is RMM?

Side by side

RMM vs MDM comparison

These are descriptions of the two categories as they are generally understood, not of any single product. Individual tools blur the lines, so check what a specific vendor actually supports.

Attribute	RMM	MDM
What it manages	Workstations, laptops, and servers, usually on Windows, macOS, and Linux. Network gear is often monitored agentlessly over SNMP.	Phones and tablets first. Most MDM tools also apply policy to laptops through the management framework built into modern desktop operating systems.
Enrollment model	Install an agent. A technician, a script, or a deployment tool puts a background service on each machine, and the agent connects out to the RMM server.	Enroll the device. The device is registered with the MDM server through the operating system's own management protocol, by the user, by IT, or automatically at first boot for company-purchased hardware.
How it acts on the device	The agent runs with administrative privileges, so it can do nearly anything an administrator could do at the keyboard.	The operating system carries out a defined set of management commands and profiles. The MDM can only do what the OS vendor exposes.
Typical capabilities	Health monitoring and alerting, OS and third-party patching, scripting and automation, remote desktop and terminal, hardware and software inventory.	Configuration profiles (Wi-Fi, VPN, email, restrictions), passcode and encryption enforcement, app deployment, compliance checks, remote lock and remote wipe.
Who buys it	MSPs managing client fleets, and internal IT teams responsible for employee computers and servers.	Organizations with company phones and tablets, bring-your-own-device programs, or zero-touch laptop provisioning. MSPs often resell it alongside their RMM.

What it manages

RMM

Workstations, laptops, and servers, usually on Windows, macOS, and Linux. Network gear is often monitored agentlessly over SNMP.

MDM

Phones and tablets first. Most MDM tools also apply policy to laptops through the management framework built into modern desktop operating systems.

Enrollment model

RMM

Install an agent. A technician, a script, or a deployment tool puts a background service on each machine, and the agent connects out to the RMM server.

MDM

Enroll the device. The device is registered with the MDM server through the operating system's own management protocol, by the user, by IT, or automatically at first boot for company-purchased hardware.

How it acts on the device

RMM

The agent runs with administrative privileges, so it can do nearly anything an administrator could do at the keyboard.

MDM

The operating system carries out a defined set of management commands and profiles. The MDM can only do what the OS vendor exposes.

Typical capabilities

RMM

Health monitoring and alerting, OS and third-party patching, scripting and automation, remote desktop and terminal, hardware and software inventory.

MDM

Configuration profiles (Wi-Fi, VPN, email, restrictions), passcode and encryption enforcement, app deployment, compliance checks, remote lock and remote wipe.

Who buys it

RMM

MSPs managing client fleets, and internal IT teams responsible for employee computers and servers.

MDM

Organizations with company phones and tablets, bring-your-own-device programs, or zero-touch laptop provisioning. MSPs often resell it alongside their RMM.

The real difference

Agent versus enrollment

Almost every other difference follows from how each tool gets onto the device. An RMM agent is ordinary software running as a privileged system service. Because it has administrator rights, it can read anything, change anything, and run any script you send it. That is why RMM is so capable at operations, and also why it only works on operating systems that allow such a service: desktops and servers.

An MDM has no such freedom. It speaks a management protocol defined by the operating system vendor, and the device will only do what that protocol allows. The result is narrower but more predictable: a well-defined set of policies and commands that work the same way on every enrolled device, including ones the company does not own. Personal phones in a bring-your-own-device program can be enrolled so that only the work data is managed.

Laptops are where the two overlap. Modern desktop operating systems accept both an MDM enrollment and an RMM agent, and plenty of teams use the pair together: MDM for provisioning and baseline policy, RMM for monitoring, patching, and support.

Which do you need

When you need RMM, MDM, or both

Start from the devices you are responsible for and the problems you are actually trying to solve.

You need an RMM when

Your fleet is mostly computers and servers, and the job is keeping them running.
You need to know about a full disk or a stopped service before the user calls.
You patch operating systems and third-party applications on a schedule.
Technicians need remote desktop, a remote terminal, and scripts that run across many machines at once.

You need an MDM when

You issue company phones or tablets, or let staff reach company data from personal ones.
A lost device has to be locked or wiped remotely.
You must prove that devices are encrypted and passcode protected.
You want new hardware to configure itself out of the box, with no technician touching it.

You need both when

You manage laptops and servers as well as phones and tablets, which describes most organizations past a few dozen people.
You want MDM to enforce baseline policy on laptops and an RMM to monitor, patch, and support them day to day.
You are an MSP whose clients expect one provider to cover every device they own.

The answer also depends on who you are. For MSPs, the RMM is the core of the business and MDM is an additional service clients ask for. For internal IT teams, the split usually follows the hardware: the RMM covers the computers and servers, and the MDM covers whatever goes in a pocket.

Where Breeze fits

Breeze is an RMM, not an MDM

This page is published by the team behind Breeze, so here is the plain version. Breeze is an open source RMM with a built-in PSA. Its agent manages Windows, macOS, and Linux computers and servers. It does not enroll or manage phones and tablets, and it does not push mobile configuration profiles or wipe mobile devices. If you need those things, you need an MDM next to it.

The two work together in a couple of specific ways. Breeze's management posture view detects which management tools, MDM included, are present on each endpoint, so you can see which machines are covered and which are not. The Breeze agent is code signed and notarized, so you can roll it out to laptops through an MDM you already run. One thing to avoid confusing: the Breeze iPhone app is for technicians to work the fleet from their own phone. It is not mobile device management.

See the full feature list for what the RMM side covers, and the pricing page for how self-hosted and cloud options are priced.

Frequently asked questions

Quick answers to the questions people ask most often about RMM and MDM.

What is the difference between RMM and MDM?

RMM (remote monitoring and management) uses an agent installed on computers and servers to monitor health, apply patches, run scripts, and give technicians remote control. MDM (mobile device management) enrolls phones, tablets, and increasingly laptops through the operating system's built-in management framework to push configuration profiles, deploy apps, enforce security policy, and remotely lock or wipe a device. RMM is about operating machines day to day. MDM is about device policy and lifecycle.

Can an RMM replace an MDM?

Usually not. RMM agents are built for desktop and server operating systems, and phones and tablets do not allow that kind of privileged background agent. Managing them properly requires enrollment through the operating system's management framework, which is what an MDM does. If you have no mobile devices to manage and no need for zero-touch provisioning, an RMM alone can be enough.

Can an MDM replace an RMM?

For some laptop-only fleets with light support needs, an MDM can cover the basics: configuration, OS updates, and app deployment. It will not give you what RMM is built for: continuous health monitoring and alerting, third-party patching with verification, scripting across the fleet, server management, and integrated remote desktop and terminal access. MSPs and IT teams that support users day to day generally need the RMM.

Does Breeze include MDM?

No. Breeze is an RMM with a built-in PSA. Its agent manages Windows, macOS, and Linux computers and servers. It does not enroll or manage phones and tablets, so if you need mobile device management you will run an MDM alongside it. Breeze does detect which management tools, including MDM, are present on each endpoint, and its signed agent can be deployed through an MDM you already use. The Breeze iPhone app is a tool for technicians, not a way to manage phones.

What is UEM, and how does it relate to RMM and MDM?

UEM stands for unified endpoint management. It is the name for products that try to manage every device type (phones, tablets, laptops, desktops) from one console, and most UEM products grew out of MDM. UEM tools tend to be strong on policy and enrollment and lighter on the monitoring, scripting, and remote support that RMM provides, so the two categories still coexist in many environments.

Need the RMM half?

Breeze is open source and free to self-host at any device count, or you can start on Breeze Cloud at $4 a device a month from November 16, or $99 a month for each 250 devices on the beta plan if you start by November 15. Keep the MDM you have for phones and tablets.

Start Cloud Beta Deploy for Free