Nevtech VMS is deployed and recording today, on real cameras at real sites, for people whose jobs depend on the footage being there. None of them have signed off on a public quote yet, so this page has none.
We are collecting named references now, one customer at a time, with written permission from the person and their organisation. When the first one clears, it appears here, in full, with the deployment it came from. Until then, the honest answer is the one above.
The fastest way to fill this page would be to write the quotes ourselves. Plenty of vendors do. We would rather ship an empty section than a fictional one, because a customer who catches an invented testimonial is right to assume the coverage numbers are invented too.
A reference is published only after the customer has read the exact wording, approved it in writing, and confirmed what we may say about their deployment. That process is underway; it is not finished.
If you want to hear from someone already running the platform before you buy, ask. We will go and ask a customer whether they will take the call. A direct conversation with an operator is worth more than a card on a web page anyway, and we would rather earn the introduction than fake the card.
Marketing quotes usually say a vendor was "a pleasure to work with," which tells a buyer nothing. Every reference on this page will answer four questions instead, because those are the ones an operator evaluating a VMS actually asks.
The person's real name, their job title, and their organisation. A security director signing off on retention policy and an integrator maintaining sites for other people have different problems; you should know which one you are reading.
Camera count, number of sites, camera makes, how they connect (direct, site gateway, cellular, or the on-camera Axis app), and the retention window. A quote from a single-building site does not transfer to a multi-campus estate, and we will not let it pretend to.
What the site ran before, what problem drove the switch, and what measurably differs now. If the answer is "we stopped discovering recording gaps after the fact," we want the sentence that says exactly that, not an adjective.
Every deployment has a rough edge. Where a customer is willing to name theirs, it stays in the quote. A reference with no downside in it has been through too many rounds of editing to be worth reading.
There is no form here, and no tracking pixel behind it. Email us. A person reads it, writes it up, and sends the exact wording back to you for approval before anything is published.
Your name, role and organisation; roughly what you run (cameras, sites, retention); what the system replaced; and what is better or worse now. Blunt is useful. Nothing you send is published until you have seen the final wording and said yes in writing.
Some organisations cannot name themselves in a supplier's marketing. That is fine: we can publish a role and a sector instead of a name, or hold the reference privately and only use it for direct buyer-to-buyer calls you agree to take. You can withdraw it at any point and it comes down.
A live demo on real cameras is a harder test than a testimonial, and it is available now. We will show live view, playback, the coverage timeline that admits its gaps, and answer the questions a reference call would have answered.
This page carries no customer testimonials, logos or case studies at present. That is a statement of fact, not modesty: the platform is in production on customer sites, and named public references are still going through the permission process. Anything published here later will be a real customer's own words, used with their written consent, alongside the deployment it describes.