SecuriThings vs MentatNOC for camera fleets

SecuriThings vs MentatNOC compares an enterprise IoT operations platform with a camera-only cloud platform. SecuriThings is built for mixed physical-security and IoT estates, the job searchers often call physical security management software. MentatNOC is built for camera fleet health, compliance, and proof, with deep support for Axis, Bosch, and Hanwha. Both connect to the customer’s network. SecuriThings’ published integration documentation puts a Horizon Connector virtual machine on that network. MentatNOC does not require an appliance, VM, or connector to install and maintain.

Claims about SecuriThings below come from its own published pages, plus that connector fact from its integration documentation. Where something is only knowable from a sales conversation, this page says to ask rather than inventing an answer.

Where they differ

What SecuriThings is

SecuriThings’ homepage headline is automated enterprise IoT device remediation. The audience it names is IT, physical security, and other IoT application owners. The pitch is one platform for a heterogeneous enterprise IoT environment, across manufacturers, management consoles, and IT or cyber platforms.

Its own physical-security software guide is explicit about device mix. The estate it describes includes surveillance cameras, access control, intrusion detection, and other connected IoT. A closing claim on that page is that the platform is designed to manage hundreds of thousands of devices across those classes. Camera brands appear as examples alongside access-control brands, which is the point: cameras are one device class in a broader program.

Day-to-day capabilities it publishes in its own words include real-time monitoring and alerting, automated firmware upgrades, password rotation, certificate management, compliance reporting, and integration with enterprise ticketing and SIEM tools. Customer quotes on the homepage talk about pushing firmware without a site visit, the cost of not knowing a device is down, and seeing status, password, firmware, and reporting work in one place.

That is a real product shape. Organizations consolidating cameras, access control, intrusion detection, and other IoT under one operations program are asking for exactly this.

What MentatNOC is

MentatNOC monitors the health, security, and compliance of camera fleets. It monitors device health, not video. The vendor list is deliberate and short: Axis, Bosch, and Hanwha. NDAA-restricted manufacturers are not supported.

The platform is three tiers, each including the one below it. Monitor watches every camera: availability, health, device-down and tamper alerts, automatic PSA ticketing, and uptime reporting. Manage acts on what Monitor finds: firmware push and rollback, password and credential rotation, certificate lifecycle, and account lifecycle, including break-glass access. Enterprise turns that record into proof: compliance reporting, audit-ready evidence exports, and point-in-time posture attestation mapped to the frameworks auditors actually ask about. MentatNOC helps you prove controls. It does not certify anyone.

Every change on the write side follows the same path, documented on the fleet actions page: requested and approved by different people, proven on a canary batch, rolled out in staged waves with health checks, rolled back automatically if a wave fails, and written to an append-only, hash-chained audit log. MentatNOC is a cloud platform. It connects to the customer’s network. There is no appliance, VM, or connector for the customer to install and maintain.

You buy it direct. We work with integrators, and the partner program is open to integrators, distributors, and MSSPs.

The comparison at a glance

	SecuriThings	MentatNOC
Built for	Mixed enterprise IoT	Camera fleets only
Device mix	Cameras, access, intrusion, other IoT	Cameras
Camera coverage	Multi-vendor, one class among many	Axis, Bosch, Hanwha
On the network	Connects; Horizon Connector VM you run	Connects; no appliance or VM
Pricing	Quote, unpublished list	Quote, per camera / month, 3 tiers
How you buy	Direct	Direct; we work with integrators
Video	Ask them	Device health, not video

A table this short hides the reasons the rows look that way. Those reasons are below.

Scope is the decision that drives the rest

If the mandate is one operations layer across every connected physical-security device, SecuriThings is built for that mandate. Breadth is the product. Camera-specific depth competes with access control, intrusion, and the rest of the IoT backlog for engineering time. That tradeoff is rational when the estate is genuinely mixed.

If the estate is cameras, or the camera portion of a mixed estate is the part that fails audits and generates truck rolls, a camera-only platform spends its depth there. Firmware follows how Axis, Bosch, and Hanwha actually publish releases. Credential rotation has to leave every consuming system still authenticating. Certificates are inventoried, watched for expiry, and rotated. Access control and intrusion devices are out of scope.

The cost shows up when the estate and the product shape do not match.

What actually has to live on your network

Both products need a path to the cameras. The operational difference is whether you also stand up and own a connector.

SecuriThings’ published integration documentation describes a Horizon Connector that runs on a virtual machine inside the customer network, with reachability to the video management system, the cameras, and the vendor cloud service. That VM is customer infrastructure. Someone provides it, patches its operating system, backs it up, monitors it, and moves it when the host is refreshed, for as long as the platform runs.

MentatNOC is a cloud platform that still connects to the customer’s network. It does not add an appliance, VM, or connector to that network, so there is no customer-hosted component in anyone’s patch schedule or hardware refresh.

A connector VM is a normal enterprise ask. It is also a standing line item: compute, OS patching, backup, monitoring, and host refreshes. Count that work when you compare the two, because it will not show up as a vendor SKU.

Camera coverage versus camera depth

SecuriThings publishes multi-vendor support as a core feature and treats cameras as one hardware family in a mixed estate. That is the correct design if procurement keeps adding device types.

MentatNOC publishes the opposite constraint. Three camera manufacturers, supported deeply, and a refusal to onboard NDAA-restricted brands. If a site is Axis, Bosch, and Hanwha, that constraint is a filter. If a site is a long tail of every camera that ever shipped, it is a miss, and you should treat it as one.

The practical test is not a logo slide. Ask each vendor to take a camera that is online and not recording, a firmware track that is current for one product and stale for another in the same family, and a certificate that expires in days, and show what the platform does. How to run that evaluation, with a test for each criterion, is in how to evaluate camera health monitoring software.

Overlap on the work, divergence on the object

The work lists look similar from a distance: watch devices, alert, update firmware, rotate credentials, renew certificates, produce reports. SecuriThings describes that work across IoT. MentatNOC describes that work for cameras, with staged changes and an evidence trail built for cameras.

That overlap is why aggregator alternatives pages are mostly noise. They match category keywords and miss the object. A platform built to manage access control and cameras together, and a platform built to stage an AXIS OS wave with automatic rollback, are not substitutes.

On MentatNOC, the write path is the same for firmware, credentials, and certificates: approval, canary, staged waves, health verification, rollback, evidence. There is no faster unofficial path for urgent changes. If you need to see that path rather than read about it, the live platform demo runs a staged firmware rollout against a 500-camera fleet, including the audit trail it leaves.

Pricing, without inventing numbers

Neither company publishes list prices. MentatNOC prices per camera per month across three tiers, Monitor, Manage, and Enterprise. Each tier includes the one below it. A 24/7 human NOC service is available as an attach on any tier, and it is the only separately priced item on the menu.

SecuriThings also quotes. How that quote is assembled, and which costs sit off the quote, is covered in SecuriThings pricing: what to know before you buy.

Stated plainly, since neither company publishes numbers: for a camera fleet, MentatNOC comes in at a fraction of the cost. That is a vendor claim on a vendor site, and you should not take it on faith. Get both quotes for the same fleet at the capability level you actually need, add what you would run yourself in each case, and compare totals.

When SecuriThings is the right call

Buy SecuriThings when the estate is mixed on purpose: cameras, access control, intrusion detection, and other IoT under one operations mandate, with one vendor relationship behind it. Their own materials are written for that buyer. A camera-only product does not compete for that mandate and should not pretend to.

Buy MentatNOC when cameras are the estate, or when cameras are the slice of a broader program that keeps failing quietly. The fit is Axis, Bosch, and Hanwha fleets that need continuous health, controlled changes, and evidence, on a cloud platform that connects to the network without a connector to maintain. Shopping after SecuriThings specifically is covered in SecuriThings alternatives for camera fleets.

Seeing it against the fleet you actually run

A comparison page cannot tell you which product matches your sites. Bring the awkward cases into both evaluations: the camera that answers on the network and records nothing, the rack with more than one vendor in it, last quarter’s auditor request. Run that list in a live platform demo, and keep the same list for any other vendor.

Already have an integrator? Keep them. MentatNOC sells direct and works with integrators, and the platform fits around how yours already services the fleet.