MeshCentral Review for MSPs

MeshCentral shows up in nearly every r/sysadmin thread about ditching TeamViewer, and it earns the recommendation. The catch most reviews skip: MeshCentral does remote access well, but it is not a full RMM, and treating it like one is how MSPs get burned.

TL;DR: MeshCentral for MSPs

What MeshCentral Is

MeshCentral is a self-hosted remote access and device management platform. You run it on your own server, install a lightweight agent on each managed machine, and get a web console for remote desktop, terminal, file transfer, and Wake-on-LAN across every device you support. It is the open source piece that other tools, including Tactical RMM, lean on for their remote-access layer.

The project comes from Ylian Saint-Hilaire, a former Intel engineer who has maintained it since 2014 and still answers questions personally on the GitHub issue tracker. That matters for a self-hosted tool, because the bus factor on a one-maintainer project is a fair question. The code carries thousands of GitHub stars and active forks, so if maintenance ever stopped, the community has the means to carry it forward.

Under the hood it is a Node.js server backed by MongoDB or the file-based NeDB for smaller setups. Agents run on Windows, macOS, and Linux. One server on 8GB of RAM and 4 vCPUs handles roughly 1,500 agents in production, and clustered deployments with a replicated MongoDB back end push past 10,000. For most MSPs, a single modest VPS covers the whole client base.

MeshCentral Features

For a free tool, the feature set is broad, and most of it lands where MSPs need it.

Remote control covers full remote desktop, a terminal, and a file manager, all in the browser, with no client install for the technician. Sessions are encrypted end to end, and you can record them for compliance or training. Device management adds grouping by client or site, a software and hardware inventory, and granular user permissions so a junior tech sees only the machines they should. Wake-on-LAN and Intel AMT support give you out-of-band access to power on or recover a machine that is otherwise dark, which is rare in tools at this price.

There is two-factor authentication, SSO through several identity providers, and a documented API for automation. The mobile app lets you jump on a device from a phone. For the specific job of getting onto a remote machine and fixing it, MeshCentral does as much as paid remote-access tools that charge per seat.

What it does not include is the rest of the RMM job. There is no patch automation, no alerting engine to speak of, no PSA, no ticketing, and no billing. The next section is the one MSPs need to read before they build a stack around it.

Is MeshCentral Free? Pricing and Licensing

Yes, MeshCentral is free, and this is where it differs sharply from a lot of "open source" tools. It ships under the Apache 2.0 license, which is genuine open source. You can use it commercially, modify it, and run it for paying clients with no approval, no sponsorship tier, and no per-endpoint fee. There is no upsell waiting at scale.

Compare that with Tactical RMM, which is source-available under a custom license that requires written approval for commercial use. MeshCentral has no such asterisk. The software cost for an MSP running it is zero, full stop.

That makes the "meshcentral pricing" question short on the software side and longer on the operations side. Your real spend is the server and your time. A $20 to $30 per month VPS runs a small fleet comfortably, and busier shops land between $50 and $100 a month for more RAM and storage. There is no free hosted tier from the project itself, though managed-hosting services will run a MeshCentral instance for you if you would rather not touch a server. For an MSP weighing free remote access software against a per-seat commercial tool, the math is hard to argue with, as long as you account for the work in the next two sections.

What MeshCentral Is Not

This is the single biggest misread in the reviews ranking today. Plenty of write-ups call MeshCentral an open source RMM and stop there. It is remote monitoring and management in the literal sense of remote access and device oversight, but it is not the RMM an MSP means when they say RMM.

A full RMM automates patching across clients, runs scheduled scripts and monitoring with real alerting, and ties into a PSA for tickets and billing. MeshCentral does the remote-access and visibility part and leaves the rest to you. That is not a flaw. It is a scope. The mistake is signing a client onto MeshCentral and assuming patch compliance and ticketing come with it. They do not, and finding that out during an audit is a bad day.

So treat MeshCentral as one strong component, not a whole platform. You will pair it with a patch tool, a monitoring tool, and a PSA, and you will own the integration work between them. Tactical RMM bundles MeshCentral with patching and scripting for exactly this reason. If you only need remote access, MeshCentral alone is lighter and cheaper. If you need the full job done, MeshCentral is the start of a stack, not the end of one.

The Real Cost of Running MeshCentral

Free software still has a bill attached. Here is what total cost looks like for an MSP, compared with a per-seat commercial remote-access tool.

The hosting number is small and predictable. The lines that do not show on an invoice are setup, maintenance, and the tools you bolt on to fill the RMM gap. A senior tech spending a day standing up the server and another few hours a month keeping it patched is a real cost, and a missed backup on a box that touches every client machine is a risk you carry alone. Price the time honestly and MeshCentral is still cheap. Ignore it and the "free" label sets a trap.

What MSPs Like About It

Sentiment across r/MeshCentral, the Lawrence Systems forum, and GitHub is consistent. The wins that come up most:

• Truly free. Apache 2.0 means unlimited devices at zero license cost, with no per-seat creep and no commercial-use clause to negotiate.
• Control. Sessions and client data stay on infrastructure you own, which keeps a third party out of the chain of custody for sensitive remote sessions.
• Capable. Remote desktop, terminal, file transfer, and Intel AMT in one console match tools that charge real money per technician.

The praise tends to grow the longer a shop runs it, especially once the per-seat invoices from the old tool stop arriving.

Where It Falls Short

The same community is candid about the rough edges.

• Built by engineers, for engineers. The web UI works, but some workflows take an extra click compared with a polished commercial product, and reporting is thin.
• You are the support and security team. No SLA, no phone line. Updates, backups, and hardening of a server that touches every client are your job now.
• Not a full RMM. No native patching, alerting, ticketing, or billing, so you will run and integrate other tools to cover the rest of the work.

None of these sink the tool for a technical shop. All of them matter if you expected a turnkey platform.

Self-Hosting Requirements and Setup

Standing up MeshCentral is approachable but not a one-click affair. The broad path:

1. Provision a clean Debian or Ubuntu VPS with a public IP, point a domain at it, and open the right ports for the agent and web traffic.
2. Install Node.js and MeshCentral, then let it pull a TLS certificate so sessions are encrypted and browsers stop complaining.
3. Create your admin account, build device groups for each client, and roll out the MeshCentral agent to your managed machines.

Plan on a few hours if you are comfortable on Linux, and most of a day if you are not. The documentation is detailed and the install is well trodden, but you still need to manage DNS, certificates, firewall rules, and updates. This is a self-hosted remote desktop in the real sense: the hosting, and the upkeep, are yours.

Security When You Self-Host

Self-hosting cuts both ways on security. The upside is real. Your remote sessions and device data never leave a server you control, which simplifies data-residency conversations and keeps a vendor out of your clients' machines.

The responsibility is just as real, and arguably heavier here than with most tools. A MeshCentral server holds remote-control access to every endpoint you manage, which makes it one of the highest-value targets in your whole operation. You own its patching, its firewall, its backups, and its access controls, and turning on two-factor for every account is not optional. Get it wrong and you have handed an attacker a single door into every client at once. The flip side of no vendor is no vendor security team, so budget the rigor you would sell to a client and apply it to this box first.

MeshCentral vs Tactical RMM vs Commercial Remote Access

Most MSPs are choosing between models, not just products. Here is how the common options line up for the remote-access job.

If you want a self-hosted tool that adds patching and scripting on top of MeshCentral, our look at the open source RMM landscape covers the trade-offs, and Tactical RMM is the usual pick. If you want a paid, hosted remote-access product with a support line, the commercial route makes sense, and the ConnectWise alternatives breakdown weighs the bigger names.

There is also the path of not stitching anything together. If the appeal of MeshCentral is escaping per-seat pricing and vendor lock-in, but you do not want to run a server or glue four tools into a stack, an AI-native all-in-one platform covers the same ground differently. OpenFrame brings remote access, RMM, and native PSA into one managed platform with no vendor lock-in, so you keep the independence without owning the upkeep. It is not the right call for every shop. The point is to match the tool to how your team really works, time and maintenance included.

Who MeshCentral Is For

MeshCentral fits a clear profile. You have Linux skills on the team, you want remote access without a per-seat bill, and you already have, or plan to add, separate tools for patching, monitoring, and tickets. You value owning the infrastructure that touches your clients, and you treat securing that server as a first-class job rather than an afterthought.

It is a poor fit if you expected one tool to replace a full RMM, if you need a vendor support number on a bad day, or if nobody on the team wants to maintain a server. Plenty of capable MSPs decide the upkeep is not worth the savings, and that is a fair call, not a failure.

The tool is genuinely good and genuinely free. Just be clear on what it is, a remote-access engine you host and secure, and what it is not, the whole RMM. Build around that and MeshCentral earns its place.

Frequently Asked Questions

Is MeshCentral free?
Yes. MeshCentral is free and open source under the Apache 2.0 license, with unlimited devices, no paid tier, and no per-seat fee. You can run it commercially for paying clients at no license cost. Your only spend is hosting and your own maintenance time.

Is MeshCentral a full RMM?
Not in the way MSPs usually mean. It handles remote desktop, terminal, file transfer, and device inventory, but it has no native patch automation, alerting engine, ticketing, or billing. Pair it with separate patching, monitoring, and PSA tools to cover the full job.

What is MeshCentral used for?
MSPs and IT teams use MeshCentral for self-hosted remote access and device management: connecting to Windows, macOS, and Linux machines for support, transferring files, running terminal commands, recording sessions, and waking or recovering devices through Wake-on-LAN and Intel AMT.

What operating systems does MeshCentral support?
The MeshCentral agent runs on Windows, macOS, and Linux, with a mobile app for technicians on the go. The server itself runs on Node.js, most commonly on a Debian or Ubuntu host, and stores data in MongoDB or the file-based NeDB for smaller deployments.

How much does it cost to run MeshCentral?
The software is free, so cost is hosting plus time. A $20 to $30 per month VPS covers a small fleet, and busier shops spend $50 to $100 a month. Factor in setup, ongoing maintenance, and the separate tools you add for patching and ticketing.

MeshCentral vs Tactical RMM, which should an MSP use?
Use MeshCentral if you only need self-hosted remote access. Use Tactical RMM if you want patching, scripting, and monitoring too, since it bundles MeshCentral for remote access under the hood. Many MSPs run Tactical RMM and get MeshCentral as part of the package.