RMM software came out of the managed service provider world, and it shows. It is built around watching a lot of machines belonging to a lot of companies and fixing them with scripts. That heritage explains both what it is unusually good at and why its pricing is so hard to look up.

TL;DR

  • RMM means remote monitoring and management: agent-based visibility, alerting, patching and scripted remediation across many endpoints.
  • It overlaps device management but is not the same thing, and the overlap is where most bad shortlists come from.
  • Of the vendors checked, only one published a comparable rate, and it is volume-tiered in the direction people get backwards.
  • Two published nothing readable and one has no pricing page at all, so budgeting here means a sales cycle.
  • Pricing is usually per endpoint, which makes a stale agent on a decommissioned laptop a billing problem.
  • Nothing in this category buys, ships or recovers hardware, and RMM is the tool most often assumed to.

What RMM software actually does

An agent runs on each machine and reports back: disk health, patch level, running services, antivirus state, resource use. On top sits alerting, automated patching, and running a script across a selected group without touching machines individually.

The multi-tenant design distinguishes it. These tools assume separate client organisations with separate policies out of one console, billing and reporting split per client. If you run one company’s estate, you are using a product built for a different job.

That is not a reason to avoid it. The monitoring and scripting depth genuinely beats what device management tools offer, because it is the whole point rather than a feature. It does mean paying for tenancy separation you will never configure.

Where RMM software stops and device management starts

The honest line is about intent rather than feature lists, because the lists overlap heavily.

  • Monitoring tools are built to notice a problem and let you act on it. Strongest on alerting, patch reporting and scripted fixes at scale.
  • Device management tools are built to put a machine into a known state and keep it there. Strongest on enrolment, configuration profiles and compliance enforcement.
  • Asset tools are built to tell you what exists. Strongest on inventory, ownership and lifecycle records.
  • Resilience tools are built to survive someone removing them. Strongest on recovery and proving a machine was rendered unusable.

A practical test. If your recurring pain is “a machine drifted and nobody noticed”, you want monitoring. If it is “a new starter’s laptop took three days to be usable”, you want device management. Those two problems feel similar in a meeting and have different answers.

Mobile is the clearest dividing line. Monitoring tools are weak on phones and tablets, because an agent model fits a desktop operating system and not a modern mobile one. If much of your estate is handsets, device management is the category and monitoring is the add-on.

What RMM software costs, as far as anyone publishes

Checked on 30 October 2026 with a browser user agent, so bot blocking could be ruled out as a cause:

VendorWhat was publishedDetail
NinjaOneA volume-tiered rangeStated as low as $1.50 per month at 10,000 endpoints
NinjaOneThe other end of itRising to $3.75 at 50 or fewer endpoints
KaseyaNo pricing pageThe URL returns a 404 with and without a trailing slash
DattoA page with no priceReturns a success code and carries no figure at all
AteraNot readableDid not return a readable figure; the request was refused
ConnectWiseNot readableDid not return a readable figure on the path checked

One published range out of six, and it is worth reading carefully because the structure catches people out. The cheap figure requires the enormous endpoint count and the expensive one applies to small teams. That is the opposite of how most buyers skim a pricing page, and quoting the low number to a fifty-device company overstates the discount by two and a half times.

The same statement adds two qualifiers worth carrying into any budget: the rate varies by region and by which products you buy, and it applies to the commercial rather than the government instance. A single figure lifted out of that sentence is not a price.

Two rows above look identical to an automated check and are not. A page returning a success code with no figure passes a link audit, and a vendor refusing a programmatic request may show a full ladder to a human visitor. Neither is the same as publishing nothing.

The per-endpoint billing trap

Monitoring is almost always billed per endpoint, and an endpoint is a machine with an agent installed. That sounds the same as a device count and is not, because an agent outlives the machine it was installed on.

A laptop that was wiped and resold, or sits in a drawer, still has a console record, and unless somebody removes it you keep paying. Stale agents are the commonest reason a monitoring bill drifts from headcount, unnoticed because the invoice grows slowly.

What to do:

  • Decide whether your real pain is noticing problems or standardising machines, and shortlist the matching category.
  • Count endpoints that would carry an agent, excluding phones and tablets, since those usually need a different tool.
  • Get the rate quoted at your own endpoint count, because volume tiering moves it substantially.
  • Agree a quarterly process for removing agents from decommissioned machines before you sign.
  • Ask how billing responds when the count falls, not only when it rises.

A worked example at 220 endpoints

An accountancy firm with 220 Windows laptops, 40 company phones and two internal IT staff. The pain is patching: machines fall behind and nobody finds out until something breaks.

Monitoring is the right category, because the problem is visibility rather than configuration. But 220 endpoints sits near the expensive end of the published range, so budget from the small-fleet rate rather than the headline.

The 40 phones are a separate purchase whatever happens, because agent-based monitoring does not serve them well. So the realistic answer is two tools, and a shortlist built from one headline figure would have missed that entirely.

The half it does not touch

An agent reports on a machine that exists, is powered on and is connected. It does not source the laptop, get it across a border to a new starter, hold a spare where you have no office, or recover it from somebody who left. This is the category most often assumed to cover that work, because it is the one with the asset list in it.

Disclosure: RemoAsset is our own product, owned by the same people who publish this site. It handles that physical side: procurement, international shipping, tracking, retrieval and wiping. It belongs here as the adjacent problem rather than as an alternative to anything above.

Its limits deserve the same plainness. RemoAsset is not an MDM, so it enrols devices but does not monitor or configure them, and you would run a management tool alongside it. It is also not a certified ITAD, meaning it wipes machines but is not the answer where certified destruction and documentation are required. And its coverage is not every country, so check the market list against your own first.

The verdict

RMM software is the right answer to a visibility problem across a lot of desktop machines, and the monitoring and scripting depth is better than the device management tools offer because it is the entire design rather than a feature. For managed service providers it is not really optional.

Go in knowing that one vendor in six publishes a rate you can compare, that the rate is volume-tiered against the small buyer, and that your endpoint count will drift upward unless somebody prunes it. You can read the published range yourself at the NinjaOne pricing page, including the qualifiers that go with it.

Checklist:

  • Category chosen against the actual recurring pain, not the feature list.
  • Endpoint count established, excluding phones and tablets.
  • Rate quoted at your own count rather than taken from a headline.
  • Quarterly agent-pruning process agreed before signing.
  • Billing behaviour on a falling count confirmed in writing.
  • Owner identified for buying, shipping and recovering the hardware.

What is RMM software?

Remote monitoring and management. An agent on each machine reports disk health, patch level, services and resource use, and the console adds alerting, automated patching and the ability to run scripts across groups of machines. It grew out of the managed service provider world, so it assumes you are managing several separate client organisations from one place.

How is it different from device management?

Intent, not feature lists, since those overlap heavily. Monitoring exists to notice a problem and let you act on it. Device management exists to put a machine into a known state and keep it there. A useful test: if your pain is that a machine drifted and nobody noticed, you want monitoring; if it is that a new starter waited three days for a usable laptop, you want device management.

How much does it cost per endpoint?

Only one of the six vendors checked published a comparable rate, as a volume-tiered range. Read it carefully, because the cheap end requires an enormous endpoint count and the expensive end applies to small fleets, which is the reverse of how most people skim a pricing page. The same statement also notes that rates vary by region and by which products you buy.

Does it manage phones and tablets?

Poorly, and this is the clearest line in the category. An agent model suits a desktop operating system and does not fit a modern mobile one, so monitoring tools are consistently weak here. If a meaningful share of your estate is handsets, device management is your primary category and monitoring is the addition rather than the other way round.

Why does my endpoint count keep growing?

Because an agent outlives the machine. A laptop that was wiped, resold or left in a drawer still has a console record, and unless somebody removes it deliberately you keep paying for it. Stale agents are the most common reason a monitoring bill drifts away from headcount, and it goes unnoticed because the invoice grows slowly rather than jumping.

Does it handle buying and shipping laptops?

No, and this is the category most often assumed to, because it is the one holding an asset list. An agent reports on a machine that already exists and is connected. Sourcing hardware, shipping across borders, holding spares, recovering devices from leavers and certified disposal all remain separate problems, so decide who owns them before you sign anything.