Plenty of service providers start by installing the regular edition separately at each client — it works, right up until it doesn't. The MSP edition exists for the moment “separately, five times” becomes the problem itself. Here is the honest difference, and the signs that say which side of the line your shop is on.
The two editions share the same engine — agents, patch management, software deployment, inventory and remote control. What the MSP edition adds is the layer a service provider lives in: customers as separate containers, remote offices per client, technician scopes per client, and per-customer reporting from one server and one login. The regular edition is an excellent tool for managing one organisation. This page is about recognising when your business stopped being one organisation.
Running the regular edition at each client means N servers to patch, N consoles to log into, N databases to back up and N upgrade weekends. At two clients that is a nuisance; at eight it is a part-time job that produces no billable value. Worse, there is no single screen that answers “which of my clients is in trouble right now?” — the question an MSP owner asks every morning. The cost is not the licences; it is the fragmentation.
You need the MSP edition when: you maintain three or more separate client installations; a technician's day involves logging into multiple consoles; monthly reporting means exporting and stitching spreadsheets; a client asked “show me only my data” and it took manual effort; or a staff change meant hunting down access across several servers. Any two of those together means the regular-edition-per-client model is already costing more than the switch will.
Honesty cuts both ways. If you are an in-house IT admin, the regular edition is your product — the MSP customer layer solves a problem you do not have. If you serve exactly one external client long-term, a single regular install at their site can be simpler and keeps their data physically theirs. And if a large client contractually requires a dedicated, isolated installation, give them one — the MSP console is for your shared book of business, not a loophole around a client's isolation requirement.
Both editions are licensed commercially by ManageEngine, and MSP pricing is structured for providers managing endpoints across customers. Packs, technician counts and prices change, so this page prints none. Get written quotes for your actual numbers — total endpoints across clients, technician seats, expected growth this year — from ManageEngine or a reseller, for both models if you are undecided. Count your current hidden cost too: hours spent hopping consoles and stitching reports are part of the regular model's real price.
See Endpoint Central MSP running live — customers, offices and agents on one screen, step by step.
▶️ Watch Full VideoNo. The endpoint management engine — agents, patching, software deployment, inventory, remote control — is the same family. The MSP edition adds the multi-customer layer on top: customer containers, per-client technician scope and per-client reporting from one server.
Probably not yet. Two installs are manageable, and switching has a migration cost. The switch starts paying when a third or fourth client arrives, or when reporting and console-hopping already eat noticeable hours every month.
Yes, and sometimes they should. If a contract requires isolation, run a dedicated regular-edition install for that client and keep your other clients on the MSP console. The two models can coexist in one business.