Transparency
How we research
Our value depends on being trusted. This page explains exactly how pages are produced and what our scores mean.
- 1
Requirements before products
Every category starts with the requirements that actually separate the options: supported platforms, deployment model, compliance evidence, scale limits and the work each tool leaves for your team.
- 2
Vendor documentation, not vendor marketing
Capability claims are checked against public documentation, release notes, support policies and independent audits. Where a claim cannot be verified, the page says so.
- 3
Pricing recorded with a date
Published list pricing is recorded with the date it was checked. Quote-only pricing is labelled as such rather than estimated.
- 4
A named wrong buyer
Each review states who should not buy the product. A tool that fits 200 devices often fails at 20,000, and the reverse is just as true.
- 5
AI drafts, human decisions
AI tools help with research summaries and first drafts. A person reviews every page before it is published and checks prices, plan limits and other product data against the sources listed on the page. Each article says how it was written and who reviewed it.
- 6
Editorial independence
Vendors cannot buy rankings, scores, verdicts or shortlist positions, and they never see or approve a page before it is published. They can send corrections through the contact page, judged on evidence like anyone else. If we earn money from a link or a sponsorship, the page discloses it where it applies, and it does not change the research.
What the score means
Scores run from 0 to 5 and weigh capability depth, administrative effort, platform coverage, transparency of pricing and support quality. A score is only comparable inside its own category: a 4.2 for a small-business tool and a 4.2 for an enterprise platform describe different things.
Found something out of date or wrong? Tell us and we will correct it with a visible update date.