PRTG Network Monitor review for MSPs and IT teams
Covers every PRTG tier with its November 2026 list price and Paessler's device estimate, the 5 to 10 sensors per device planning rule, the MSP Edition and access-rights options for client separation, a PRTG vs Zabbix table, and a seven-tool shortlist for MSPs and in-house IT teams.
Updated: November 2026
PRTG Network Monitor watches everything on a network and alerts the moment something breaks, which keeps it on the shortlist for MSPs and in-house IT teams alike. The questions that decide the purchase sit underneath: what it costs across dozens of client sites or a growing company estate, how cleanly one install keeps client data apart, and whether the math still works after Paessler moved PRTG to subscription-only pricing in 2024. This review answers each one with Paessler's published prices as of November 2026.
TL;DR
- 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 $200 a month for PRTG 500 up to $1,642 for PRTG 10000, billed annually (Paessler, November 2026).
- MSP fit. Per-client access rights and free remote probes on one shared core, with the PRTG MSP Edition adding separate instances when clients need harder isolation.
- IT team fit. One install covers a single company estate well, and Enterprise Monitor takes over past about 1,000 devices or 10,000 sensors.
- Ratings. 4.7 on G2, 4.6 on Capterra, as of September 2026.
- The call. Solid for Windows-heavy SMB clients and single-estate IT teams, weaker where you need per-tenant isolation.
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.
Who makes PRTG and what changed since 2024
PRTG comes from Paessler GmbH, founded in Nuremberg, Germany, in 1997. It is proprietary software, so the Freeware edition costs nothing up to 100 sensors but the code stays closed; teams that need an open-source license can compare it with Zabbix or Checkmk Community in the table further down. San Francisco software investor Turn/River Capital made a strategic investment in Paessler on May 23, 2024, a few weeks before the subscription change covered below, and Jason Teichman became CEO in September 2025.
The product family has grown to five editions. Network Monitor, Hosted Monitor and Enterprise Monitor are covered in the licensing section, the PRTG MSP Edition supports a separate database per client instance, and the PRTG OT Edition extends monitoring to industrial networks.
Two 2026 changes matter for buyers. Paessler bought UVnetworks in May 2026, adding UVexplorer's network topology, inventory and configuration backup, and Paessler PRTG UVexplorer now brings integrations with Hudu, IT Glue, Jira and Asset Panda. On the product side, the PRTG release notes for stable version 26.3.124 (September 16, 2026) list an experimental MCP server in the PRTG API v2 that lets AI assistants query a PRTG instance, while the AI Chatbot Max on the New UI welcome page has been unavailable since version 26.3.122. Beyond UVexplorer, integrations run through PRTG's open API, and ServiceNow and HaloPSA/HaloITSM each publish their own PRTG connector.
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 subscription tied to a sensor ceiling. Paessler publishes the monthly prices below, billed annually, on its PRTG pricing page (read November 3, 2026), along with a rough device count for each tier. Each license key runs on one PRTG server, and licenses can't be combined, so two 500-sensor installs are two subscriptions rather than one PRTG 1000.
| Tier | Sensor limit | Price per month, billed annually | Paessler device estimate |
|---|---|---|---|
| Freeware | 100 | $0 | About 10 |
| PRTG 500 | 500 | $200 | About 50 |
| PRTG 1000 | 1,000 | $358 | About 100 |
| PRTG 2500 | 2,500 | $742 | About 250 |
| PRTG 5000 | 5,000 | $1,300 | About 500 |
| PRTG 10000 | 10,000 | $1,642 | About 1,000 |
| Enterprise Monitor | 10,000+ | Quote | 1,000+ |
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 check out. 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 and IT teams need to know
For an MSP, multi-tenancy is the question that decides a PRTG purchase: monitoring many clients from one install is straightforward, and keeping each one cleanly isolated takes planning. Paessler's product pages and its knowledge base each answer part of it, and both matter. An in-house IT team running one company estate needs per-department access rights more than tenant isolation, so the same tools apply with lower stakes.
Paessler describes PRTG as multi-tenant by design. On a standard install, that runs through access rights per client group: you create a group per client and scope it so each client sees only their own devices, sensors, dashboards and reports, while your technicians keep one view across the portfolio. For clients that need more separation, the PRTG MSP Edition supports separate databases per instance, and Enterprise Monitor runs multiple databases under one application.
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. Access rights on a shared core control what each client sees, and separate instances are what isolate the data itself.
Paessler has run a dedicated MSP program since March 2025, with discounts that scale with sensor volume, NFR licenses for testing in client environments, and, by Paessler's count, 170-plus MSPs running client monitoring on PRTG. Auvik and Domotz take a different route, treating every client as a first-class tenant with isolation and per-client billing built 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 and IT teams
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. TechRadar flagged support costs as a sore spot; under the current subscriptions, Paessler includes updates and email support in the price, and Enterprise Monitor adds high-priority 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 suits a specific shape of MSP or IT team better than others.
PRTG vs the alternatives MSPs shortlist
When MSPs and IT teams price PRTG against the field, the same names come up. Here is how the shortlist compares on licensing, tenancy and deployment.
| Tool | Pricing model | Multi-tenant | Agentless | Built for MSPs | Best for |
|---|---|---|---|---|---|
| PRTG | Per-sensor subscription | Client access rights; MSP Edition for separate instances | Yes (SNMP/WMI) | Partial (MSP program) | Windows-heavy SMB, single-site clients |
| Auvik | Per-device | Yes, native | Yes | Yes | Network topology mapping, config backup |
| Domotz | Per-site ($35/site/mo, unlimited devices) | Yes, native | Yes | Yes | Low-cost remote network monitoring |
| NinjaOne | Per-device | Yes | Agent-based | Yes | Endpoints plus light network in one tool |
| Zabbix | Free, open-source (AGPLv3) | Self-built | Agent and agentless | No (DIY) | Deep customization, in-house skills |
| LogicMonitor | Per Hybrid Unit (from $16/mo) | Yes | Yes | Partial | Enterprise and hybrid observability |
| Checkmk | Free Community; paid from €190/mo | Ultimate edition | Agent and agentless | No | Broad monitoring if you self-manage |
A few distinctions. Auvik and Domotz are purpose-built for MSPs, so multi-tenancy and per-client billing come standard, and Domotz prices per site with unlimited devices, which keeps device-dense clients affordable. 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.
PRTG vs Zabbix
Zabbix is one of the two alternatives named most often in the r/networking thread on the 2024 price change, and the two tools split on license, setup effort and who carries support. Zabbix has shipped under the AGPLv3 since version 7.0, so the software costs nothing at any scale, while PRTG meters every sensor above the free 100.
| Factor | PRTG | Zabbix |
|---|---|---|
| License | Proprietary; Freeware to 100 sensors | Open source, AGPLv3 since 7.0 |
| Software cost | $200 to $1,642 a month, billed annually | Free at any scale |
| Hosted option | PRTG Hosted Monitor | Zabbix Cloud, from $50 a month |
| Setup | Auto-discovery with preset thresholds | Templates and tuning you maintain |
| Client separation | Access rights per client group; MSP Edition | Proxies and permissions, no native multi-tenancy |
| Support | Updates and email support included | Optional plans from $325 a month |
PRTG gets a site monitored faster, because auto-discovery assigns sensors with preset thresholds and the core installs on one Windows server. Zabbix asks for more up front, including a database, templates and a front end you maintain, and pays that back with deeper customization and no sensor ceiling. For an MSP the trade is engineering hours on Zabbix against the sensor bill on PRTG; for an in-house IT team it is whether anyone on staff wants to own a Zabbix server. Licensing, support plans and multi-tenancy workarounds are covered in our Zabbix review.
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.
PRTG is also one more metered line on a stack that already carries an RMM bill, a PSA bill, a documentation bill and a security bill. OpenFrame, from Flamingo (the company that publishes this blog), is open, AI-native infrastructure for IT and security that covers large areas of that stack, including RMM, remote access, patching, PSA and documentation, with agents working inline: Fae resolves support requests and Mingo runs IT ops. It costs $1 per device a month with 10M AI tokens included, and PRTG can keep the network sensors while OpenFrame runs the endpoint and service side; a 14-day free trial shows whether that split trims the rest of the bill.
For MSPs and IT teams alike, the renewal stack around monitoring is where the budget goes. Price PRTG on what it costs to run across your whole client base or estate over a full three-year term, counting sensor growth and support, rather than what the first install costs this month, and the right call gets a lot clearer.

Content Marketing Lead
Ohayo! I run content, SEO, social, and community at Flamingo. Before IT, I worked as a correspondent for Ukraine's Public Broadcasting Company and have a Master's in journalism.
Related Content
Frequently Asked Questions
/blog/prtg-network-monitor-review
Still deciding?
Ask Mingo answers from our docs and customer stories.