RMM is quoted per endpoint per month almost everywhere, and that apparent simplicity hides most of what decides the bill. The rate is a function of volume, the volume is a function of a count nobody agrees how to take, and the modules that make the platform useful are frequently outside the number. This page sets out what the published figures cover and what reliably arrives beside them.
The per-endpoint figure and the curve under it
Three vendors here publish a rate. NinjaOne states it starts as low as $1.50 USD per month at 10,000 endpoints, increasing to $3.75 USD at 50 or fewer endpoints, and adds that pricing varies by region and products purchased. SuperOps prices its 100-endpoint minimum at $1.50 each, $150 a month. Level publishes a flat $2 per device per month for every device on the account with the first ten free. Two of the three are volume-tiered and one is deliberately not, and that difference is the first thing to establish about any quote. A tiered price is a bet on your growth: good if you are growing into it, bad if it was set at a count you have since lost. A flat price is a bet against complexity, and it costs more at scale in exchange for never needing a negotiation.
What counts as an endpoint, and when it starts counting
Servers, workstations, virtual machines and mobile devices are priced alike by some vendors and separately by others, and a machine that was powered off all month may still be billable. The question to settle in writing is how the count is taken: peak during the month, average, or a snapshot on a billing date. Level publishes that billing is based on your peak device count during the month, which is the least generous of the three and is at least stated. The related trap is discovery. Turning on network discovery finds machines nobody knew about, which is the point of it, and at several vendors those machines become billable the moment an agent lands. That is defensible and it is worth knowing before the first invoice rather than after.
What sits outside the number
Backup, endpoint security, documentation, PSA and, at some vendors, third-party application patching are separate lines. A per-endpoint figure covering monitoring and OS patching is a partial answer to what an MSP platform costs, and the gap is normally larger than the difference between two vendors' headline rates. Remote access is the other one that surprises people, because it feels like part of an RMM and is sold separately often enough to matter: Splashtop publishes a Solo remote-access plan at $6 a month billed annually, priced per user rather than per endpoint, which is a different axis again. Ask for one figure covering the whole configuration you would deploy, at the count you expect at renewal. It is the only number that compares across vendors, and vendors resist producing it precisely because it compares.
Questions people ask about rmm pricing
How is RMM priced?
Per endpoint per month, usually on a volume curve. NinjaOne publishes $1.50 at 10,000 endpoints rising to $3.75 at 50 or fewer; SuperOps $1.50 at a 100-endpoint minimum; Level a flat $2 with ten devices free.
What counts as an endpoint?
It varies. Servers, virtual machines and mobiles are priced alike by some vendors and separately by others, and a powered-off machine can still be billable. Settle in writing whether the count is peak, average or a snapshot.
Why is my renewal higher than my first year?
Usually a term discount ending, a volume tier that no longer applies after client churn, or modules added during the year. Ask for the year-two figure at quote time.
Is remote access included in RMM pricing?
Often but not always, and standalone remote access is priced per user rather than per endpoint: Splashtop publishes a Solo plan at $6 a month billed annually. Check which axis your quote uses.