// PRODUCT REVIEWS · BETA TESTING · HANS STUDY

Product reviews and beta testing

Manufacturers and software vendors send products here to be used the way an integrator or an operator would use them, and written up the way a practitioner would write them up. Hardware, software, and services in networking, physical security, and OT. Independent, unpaid, and published with the failures left in.

Most product reviews in this industry are written by people who have never installed the product, paid for by the people who make it, or both. Integrators and IT staff have learned to skip them. What they read instead is a practitioner's account of a product on a real network, with a real VMS behind it, a hardening baseline applied, and the version numbers written down. That is what gets produced here, on the same terms as the consulting: no products sold, no margin, no commission, and an opinion with a reason.

Reviews publish as articles on this site, as videos on the StudyByt3s channel, or both. Beta testing produces a private findings report for the vendor and, if both sides want it, a public review once the product ships.

What fits

Cameras, access control, and intercom

IP cameras, encoders, controllers, readers, credentials, and the panels behind them. Tested on a real VMS and a real network, not a bench switch and a laptop.

Network hardware

Switches, access points, firewalls, network adapters, optics, and PoE. Judged on what they do under a camera load and a hardening baseline, and on how the management plane behaves.

VMS, PSIM, and security software

Video management, access control software, analytics, and the tools that sit beside them. Deployment, integration, Active Directory, service accounts, and what the upgrade path looks like.

Security and compliance tools

Vulnerability scanners, configuration auditors, email security, logging, and the SaaS aimed at small and medium organizations working toward CPCSC, CMMC, or ISO 27001.

Cabling, test, and field tools

Terminations, testers, labelers, and the gear that lives in the site bag. Reviewed by someone who has pulled the cable and crimped the end.

Products still in beta

Pre-release hardware or software that needs a practitioner to break it before customers do. Private findings under NDA, with a public review later if both sides want one.

What a review looks like

Every review follows the same shape, so a reader can compare 2 products without re-learning the format. What the product is and who it is for. The test environment, with versions. The setup and first-day experience, which is where most products lose an integrator. What worked under load. What did not, with what was tried. Where it fits, and who should not buy it. Previous reviews:

Beta testing

A beta test is a different deliverable. The output is private: a findings report covering install friction, documentation gaps, behaviour under a realistic load, how the product behaves on a hardened host or a segmented network, security observations, and the questions an integrator would ask before putting it in a quote. Findings are numbered, reproducible, and ranked by what would stop a deployment. NDAs are fine. Nothing is published unless the vendor agrees, and a public review after general availability is a separate decision.

Vendors use this when the product is going into environments the developers have not seen: a municipal camera network, a plant floor, a Windows domain with a tiering model, a Genetec deployment with Defender exclusions that have to be exactly right. Those are the environments this practice works in.

The test environment

A working lab built around the platforms listed on the about page: Genetec Security Center as the reference VMS, Windows Server and workstation baselines, Cisco and Aruba switching, IP cameras from the major manufacturers, and the firewalls and tooling that go with them. Products are tested against a hardening baseline, not a default install, because that is where they will live. Where a product needs scale that a lab cannot provide, it can be observed in a live environment when the owner of that environment agrees, and that agreement is noted in the review.

Terms

These are the terms that make a review worth anything, and they are not negotiable per product.

01

Nothing is paid

No fee, no sponsorship, no affiliate links, no placement. The independence policy that covers the consulting covers the reviews. A vendor cannot buy a review, and cannot buy a better one.

02

You see the draft for facts, not for approval

Before a review publishes, the vendor gets the draft to check facts: model numbers, versions, specifications, and anything that reads as a misunderstanding of the product. Opinion and conclusions are not up for negotiation, and the review publishes either way.

03

The failures stay in

If a product did not work, the review says so, with what was tried and the versions involved. If it worked, the review says that, with the same detail. Readers trust the second because of the first.

04

Loaned units go back, kept units are disclosed

Hardware is returned at the end of the review unless the vendor asks otherwise. Anything kept is stated in the review. Software licences are time-limited review licences where the vendor offers them.

05

Security findings go to you first

A security flaw found during a review is reported to the vendor privately with the detail needed to reproduce it. Publication waits for a fix or for a window agreed in writing. The review will say that a finding was reported and resolved.

06

Quotes yes, badges no

A vendor may quote the published review with attribution and a link. No "reviewed by" badges, no "endorsed by" language, and no implied partnership. The review is the record.

07

Fit comes first

Not every product gets reviewed. Products outside networking, physical security, OT, and the tooling around them are declined, and so are products where a fair test is not possible with the time or the environment available.

08

No clients, no customer sites

Reviews are done in the lab or in environments where the owner has agreed. No client is named, and no customer of the vendor is described in a way that identifies them.

What a vendor gets

  • A practitioner's read on the product, from someone who designs, hardens, and troubleshoots the systems it will sit in.
  • A published review read by integrators, IT and security staff, and public-sector and critical-infrastructure buyers in Canada and the United States.
  • A private findings list that goes beyond the published text: the bugs, the documentation gaps, and the install friction a reader does not need but a product manager does.
  • A current summary of who reads this site and watches the channel, on request, so the decision to send a product is made on numbers rather than on a pitch.

What is not on offer

  • Paid placements, sponsored episodes, or sponsored articles.
  • Affiliate links or revenue on anything reviewed.
  • A guaranteed outcome, a draft the vendor can edit, or a review that gets pulled on request.
  • Marketing copy, white papers, or "independent" content written to a vendor brief.
  • Reviews of products outside networking, physical security, OT, and the tooling around them.

How to send a product

Email review@hans.study with the product and what it is for, the stage it is at (shipping or beta), what you want (a public review, private beta findings, or both), whether the unit is a loan or a keep, and whether an NDA is involved. A link to the documentation helps more than a brochure. If the product fits, you get a reply with what the review would cover and the shipping details. If it does not fit, you get a reply saying so.

Related

The independence policy is the full statement of what this practice does and does not take money for. The media page covers interviews and podcast guesting. The recommended products page lists what gets specified in designs, with no margin on any of it.