Methodology
How a product earns its verdict
No stars, no points out of ten, no averaged user scores. Every product is judged against the same six questions a buyer would ask, and ends up with one of three plain-language labels.
Why we do not use scores
A score of 8.7 suggests a precision that software evaluation does not have, and a star row looks like the opinion of many customers when it is really the opinion of one writer. Monitoring tools are also unusually situational: the product that is right for a 40-device office with one admin is often wrong for a 2,000-device estate with a network team. So instead of scoring, we answer the same six questions for every product and then say, in words, whom it suits.
The rubric
Six questions, asked of every product
Cost you can forecast
Can a buyer turn a device list into a three-year cost without a sales call?
We read the vendor’s published pricing pages and licence documentation, note which unit is counted (sensor, device, endpoint, service, node), and model the bill at roughly 50, 250 and 1,000 devices. Where figures are not public we describe the model and say so.
Time to first useful alert
How long from sign-up to an alert that a human would act on?
We follow the vendor’s own getting-started path — the same trial or public demo any buyer can start — and time it against the vendor’s documentation and widely reported admin experience: discovery, credentials, first dashboards, and — the part that counts — the first alert that is neither noise nor missing context.
Trial you can learn from
Does the trial let you test what you would actually pay for?
Trial length, feature limits, whether a card or a sales call is required, and whether trial data carries over if you buy.
Hidden costs
What does the quote leave out?
Add-on modules, server and database requirements, collectors or probes per site, training, and the staff hours needed to keep the platform itself healthy.
Lock-in and exit
If the renewal price jumps, how painful is leaving?
Export formats for devices, templates and history; API access; contract terms we can see; whether configuration lives only in the vendor’s cloud.
Support you can reach
Who answers when monitoring itself breaks?
Support channels included at each tier, documentation quality, community size, and for open-source tools whether commercial support exists at all.
Verdict labels
What the three labels mean
Each review carries exactly one label. It is an editorial judgement by ISABELLE, CLAUDINE, CATHERINE, JEANNE ALARY after working through the six questions — not a rating, not a user score, and never something a vendor can buy.
We would put it into a buyer’s trial round for its category without reservation. Currently: 3 of 11 products.
Strong in a specific situation we name; a poor default outside it. Currently: 4 of 11 products.
No licence fee. Either a do-it-yourself alternative we cost every commercial quote against, or a free tool you will use alongside any purchase — you pay in staff time instead. Currently: 4 of 11 products.
A label is always relative to the category the product is reviewed in and to the buyer we describe in the review. “Situational” is not a polite way of saying “bad”: SolarWinds NPM, for example, is a strong platform for a large organisation with a network team, and a heavy one for anybody else. Each review explains its label in a single sentence on the review card, then in full in the text.
Where the facts come from
- Pricing and licensing: the vendor’s own pricing pages, licence documentation and published data sheets. When a vendor quotes only on request we describe the model — per sensor, per device, per endpoint, per service — and do not invent a figure. Any number we do give is marked “at the time of writing”.
- Trials: the vendor’s standard trial as offered to any buyer, started from the vendor’s own website. We note its length, what it requires at sign-up, and what it limits.
- Behaviour and effort: working through the vendor’s own trial or public demo where one is offered, and the vendor’s public documentation and widely reported admin experience where it is not. Reviews say which applies.
- Screenshots: taken from the vendor’s own site or a freely licensed source, with the source printed under the image. Illustrations are labelled as illustrations.
How commercial relationships are handled
No vendor pays us anything: at the moment no link on the site is an affiliate link, and every product link goes directly to the vendor’s own website (see the affiliate disclosure). Tables are ordered by verdict and then editorially. Open-source products sit on every relevant shortlist as the baseline.
Keeping pages current
Every review, guide and comparison shows the date it was last updated. We re-check pricing models and trial terms for the whole catalogue periodically and whenever a reader or vendor reports a change. If you find something wrong, email editor@netops24.icu with a link to the source; corrections are made on the page itself rather than in a hidden changelog.
What we do not cover
We do not review tools whose main purpose is probing networks you do not own, and we do not link to files of any kind. The IP and share scanners and the packet analyzer on ourdiscovery and troubleshooting page are covered only as ways to count and diagnose your own infrastructure before and during a purchase. Everything on this site assumes you are monitoring, sweeping or capturing on networks you own or are authorized to manage.