PRTG Network Monitor Review: Mind the Sensor Bill

PRTG Network Monitor does one job well: it watches everything on a network and tells you the second something breaks. For an MSP the harder questions sit underneath that. What does it cost to run across dozens of client sites? Can one install keep those clients cleanly separated? And after Paessler switched PRTG to subscription-only pricing in 2024, does the math still work?

Here is how PRTG holds up inside a managed services stack in 2026.

TL;DR: PRTG for MSPs

• What it is. Agentless, sensor-based network and infrastructure monitoring from Paessler, strong on auto-discovery and fast setup.
• Pricing. Free for 100 sensors, then paid tiers run from about $179/mo to about $1,492/mo, billed annually on 3-year terms.
• MSP fit. Role-based client views, free remote probes, and an MSP program, but the core is single-app and single-database, not true multi-tenancy.
• Ratings. 4.7 on G2, 4.6 on Capterra, 4.5 on Gartner Peer Insights, 4.0 on Trustpilot.
• The call. Solid for Windows-heavy SMB and single-site clients, weaker where you need per-tenant isolation and client billing built in.

What PRTG Network Monitor Is

PRTG is a network and infrastructure monitoring tool built around one unit: the sensor. A sensor is a single thing you measure, not a whole device. One server might use a sensor for CPU load, another for free disk, another for a specific service, another for each network interface. That granularity is why PRTG can watch almost anything, and also why sensor counts climb faster than people expect.

The breadth is the headline. Version 25.4 ships 321 sensor types covering SNMP, WMI, NetFlow, HTTP, ping, packet sniffing, and more. Most monitoring is agentless, so you point PRTG at a device over a standard protocol instead of pushing software onto every endpoint. The setup wizard runs auto-discovery, finds what is on the subnet, and assigns sensors with preset thresholds, which is a big reason reviewers keep calling deployment quick.

Day to day, techs work in a web console, with desktop apps for Windows and macOS and free iOS and Android apps for on-call. You get live dashboards, custom maps through the map designer, alerting over email, SMS, and push, plus scheduled reporting.

The maps are the feature techs tend to keep open, since you can drop real device status onto a floor plan or a network diagram and read the whole site at a glance. Alert thresholds come preset from auto-discovery, which is fine on day one and worth tuning later so a flapping interface does not page someone at 3am.

IT Pro's hands-on review of version 25.4 sums up the appeal for shops that want to monitor everything in one place, and it puts a useful number on the cost of that breadth. Their test rig, one firewall, a 52-port switch, a VMware host, three Hyper-V hosts, six Windows servers, two NAS units, and a printer, consumed over 700 sensors. That is a single small site. Now picture twenty client sites. If you are sizing a network monitoring layer across a client base, it helps to see where PRTG sits next to the rest of the field in this network management software comparison.

How PRTG Sensor Licensing Works

Sensors are the meter, and the meter is what you pay for. A rough planning rule is 5 to 10 sensors per device once you account for interfaces, services, and hardware health. The free edition gives you 100 sensors with full core features and no time limit, which covers roughly 10 to 20 devices. That tier is genuinely useful for a lab or a single tiny client, and it is one of the few free monitoring options that does not expire.

Above free, you buy a license tied to a sensor ceiling. Here are the published tiers and the approximate going rates. Treat the dollar figures as ballpark, since Paessler quotes in subscription terms and the exact numbers shift by region and term.

The product line splits three ways. PRTG Network Monitor is the self-hosted classic. PRTG Hosted Monitor is the same thing run by Paessler as SaaS, so you skip the server. PRTG Enterprise Monitor targets large, multi-site environments with multiple databases and a different licensing basis. For an MSP, the planning work is the same either way: estimate sensors per client, multiply by your client count, and check which ceiling you land in before the renewal conversation.

The thing to watch is sensor creep. Every new client device, every added interface, every extra service check nudges the count up. Cross a tier boundary and you jump to the next license. Reviewers across IT Pro, TechRadar, and the comparison sites all land on the same caution: PRTG is easy to start and easy to outgrow if you do not plan the sensor budget.

The 2024 Price Increase, Explained

On July 1, 2024, Paessler ended perpetual licenses and annual maintenance extensions and moved PRTG to subscription-only. That single change is the reason PRTG pricing became a live topic in MSP circles, and it is worth getting the numbers right rather than repeating the loudest version.

The Register reported the like-for-like jumps when the policy landed. The XL1 unlimited tier went from a roughly 3,900 euro per year maintenance extension to about 8,800 euro, near a 126% rise. PRTG 5000 moved from about 2,900 euro to 6,500 euro, near 124%. So on a clean comparison the increase roughly doubled, not tripled.

The "300%" figure that floats around community threads comes from a different comparison. Customers who had been paying only a small annual maintenance renewal against an old perpetual license saw their new full subscription cost balloon by far more than 126%, because they were comparing a maintenance sliver to a complete subscription. Both stories are real. The directional point for an MSP is simple: recurring per-sensor billing across a growing client base is now the model, and the renewal line will keep rising as you add clients. The r/networking thread that flagged the change drew a steady stream of long-time users weighing alternatives, with Zabbix and Nagios named most often as the escape hatch.

PRTG Multi-Tenancy: What MSPs Need to Know

This is the section that separates an MSP review from a generic one, because every consumer review skips it. The question is not "can PRTG monitor many clients," it is "can one PRTG cleanly isolate many clients." The answer has a marketing version and an architecture version, and MSPs need the second one.

Paessler now markets multi-tenancy. PRTG Network Monitor and Hosted Monitor are described as single-application, single-database with multi-tenant access, and Enterprise Monitor as single-application with multiple databases. In practice that multi-tenancy is delivered through the roles and permissions system. You create user groups per client and scope them so each client sees only their own sensors, dashboards, and reports.

The architecture version is in Paessler's own knowledge base. Their multi-tenant guidance states that each PRTG installation needs its own database and configuration file, and it warns against forcing many clients into one core through API workarounds because you risk data corruption and crashes. Their recommended path for real separation is a separate instance or at least dedicated remote probes per customer, with MultiBoard stitching a central overview across those separate installs. Remote probes are free, which helps you reach client sites from a central core, but role-based visibility is a soft overlay on a shared core, not the hard tenant isolation you get from a platform designed multi-tenant from the start.

Paessler does run a dedicated MSP program with an OPEX subscription that scales with your client base, agentless monitoring, and those free remote probes. So PRTG is usable for MSPs. It is just not multi-tenant the way Auvik, Domotz, or NinjaOne are, where every client is a first-class tenant with isolation and per-client billing baked in. If per-tenant separation and clean client rollups are the deciding factors, weigh that against tools designed for it in this network performance management software breakdown.

What Real Reviews Say

PRTG scores well where the audience is general IT, and more mixed where the audience has lived with the licensing. On G2 it sits at 4.7 from around 209 reviews, with 88% at five stars. Capterra shows about 4.6 across 240-plus reviews, strong on customizable alerts and slightly lower on ease of use. Gartner Peer Insights lists roughly 4.5 from around 825 ratings. The recurring praise is consistent: quick to deploy, easy to maintain, broad coverage out of the box.

Trustpilot tells the other half of the story at about 4.0 across roughly 1,160 reviews, where licensing complaints surface more often. One reviewer captured the MSP-relevant tension neatly, writing that PRTG "feels like it was built to monitor a single site but is pitched as an enterprise-level network monitor." That single-site DNA is exactly what the multi-tenancy section gets at. Paessler counters with its own survey stat that over 95% of participants would recommend PRTG, which is worth knowing and worth labeling as vendor-sourced. The pattern across all four platforms is clear enough: people like using PRTG and watch the bill.

PRTG Pros and Cons for MSPs

The strengths are real. Auto-discovery and the setup wizard get a new client monitored in an afternoon, not a week. The agentless model means fewer things to install and patch on client endpoints. Coverage is wide enough that one tool can watch firewalls, switches, servers, VMs, and printers without bolting on extra modules, since every sensor type is included in the license. For a Windows-heavy SMB on a single site, that combination is hard to beat on time-to-value.

The friction is mostly commercial and structural. Per-sensor licensing turns into a budgeting exercise that never really stops, and the 2024 subscription shift made the recurring cost more visible. A practical example: a client that adds a new switch stack and a couple of VMs can quietly push you from PRTG 1000 into PRTG 2500, doubling that client's monitoring line without a single conversation about scope. Multiply that across a portfolio and the renewal becomes a moving target you have to forecast rather than set. Extended support beyond the first year can carry an added charge, which TechRadar flagged as a sore spot compared to tools with inclusive support. Deep customization trails open-source options like Zabbix. And the multi-tenancy gap means an MSP scaling past a handful of clients ends up managing multiple instances or probes and reconciling billing by hand. None of that disqualifies PRTG. It does mean the tool rewards a specific shape of MSP and punishes another.

PRTG vs the Alternatives MSPs Shortlist

When MSPs price PRTG against the field, the same names come up. Here is how the shortlist compares on what matters for a multi-client operation.

A few honest distinctions. Auvik and Domotz are purpose-built for MSPs, so multi-tenancy and per-client billing come standard, and Domotz in particular undercuts almost everyone on per-device cost. NinjaOne folds network monitoring into an RMM, which is great if you want endpoints, patching, and light network checks under one login, though its network depth trails a dedicated tool. Zabbix is the free, infinitely customizable option that the price-hike refugees keep naming, with the catch that you own all the setup and maintenance. If you are weighing the open-source route specifically, the trade-offs are laid out in this Zabbix alternative guide. LogicMonitor and Datadog reach higher into enterprise observability and price accordingly, which is usually overkill for an SMB-focused MSP.

Where PRTG Fits, and Where It Doesn't

PRTG fits the MSP whose clients are mostly single-site, Windows-leaning SMBs, where fast deployment and broad coverage beat deep customization, and where the client count is small enough that managing a core or two stays sane. In that shape, the free tier and the quick wins make it an easy yes.

It fits less well when you are scaling a portfolio that needs per-tenant isolation, per-client billing, and a single pane across many clients without manual reconciliation. At that point the per-sensor meter and the single-database core start working against you, and tools built multi-tenant from day one pull ahead.

There is also the bigger pattern worth naming. PRTG is one more per-seat, or in this case per-sensor, line on a stack that already has an RMM bill, a PSA bill, a documentation bill, and a security bill. The consolidation play is to fold monitoring into a platform that already runs the rest. That is the bet behind OpenFrame, the AI-native, all-in-one MSP and IT platform from Flamingo, with native PSA included rather than bolted on, priced without per-sensor lock-in. It is not the best tool for every job and it is not trying to be. It is the option for MSPs who would rather pay for one platform than meter ten.

Monitoring is not where MSPs lose money. The renewal stack around it is. Price PRTG on what it costs to run across your whole client base over a full three-year term, counting sensor growth and support, not what the first install costs this month, and the right call gets a lot clearer.