A structured review of Verkada's cloud video security platform for IT, security and operations buyers: what it does well, where the constraints sit and who should look elsewhere. Every score traces to something Verkada publishes.
Verkada is one of the most complete single-vendor platforms in physical security: cameras, access control, sensors, alarms and intercoms in one cloud console, with on-camera analytics on second-generation hardware and newer. It scores lower on the questions that matter to a team with an existing camera fleet, because bridging third-party cameras is a hardware purchase with documented stream conditions and automated audio deterrence works with Verkada audio devices. Choose Verkada for a build you specify end to end. Look elsewhere when the cameras you already own have to do the work.
Five criteria, each scored from Verkada's own current documentation as of August 6, 2026, plus dated public records where a criterion depends on one. Spot AI competes with Verkada, so no score here rests on an anonymous source, an aggregated user rating or a private benchmark: each one sits next to the documented fact behind it. Anything Verkada does not document is recorded as not publicly specified rather than assumed. This is not a paid placement, and Verkada had no input into it.
One console covers cameras, access control, sensors, alarms and intercoms. Two documented gates decide how much of that reaches hardware Verkada did not sell you.
Verkada sells a cloud-managed physical security platform. Cameras, access control, environmental sensors, alarms and intercoms are administered together in Command, its browser console, and analytics run on the camera itself on second-generation hardware and newer. The design target is a team that wants one vendor, one console and one support relationship across every site.
It serves that target well, and the hardware is documented in detail. Onboard retention runs from 30 to 90 days up to 30 to 365 days depending on model, analytics are stated to run on the camera on second-generation hardware and newer, and the supported audio devices for automated deterrence are named rather than implied. For a team specifying an estate end to end, that is a design that can be reviewed before anything is ordered.
The platform also reaches past its own hardware. Since February 2025 Verkada has stated that Command Connector is officially recognized as an ONVIF Profile S conformant client and can ingest feeds from RTSP-compatible cameras that are not ONVIF Profile S conformant, which brings a legacy fleet into the same console.
Verkada is strongest as a single-vendor platform for a build you control end to end, and weakest as a way to add AI to cameras somebody else installed.
Both columns are documented. Nothing here comes from an anonymous review.
Both columns describe documented behavior. Verkada's column was checked against its own documentation on August 6, 2026.
Swipe the table sideways to see every column.
Verkada data comes from Verkada's own public documentation as checked on August 6, 2026. Gaps are marked as not publicly specified.
The honest split, stated the way a shortlist call would state it.
If you are choosing cameras, doors and sensors from scratch, want one vendor and one console and have the hardware budget, Verkada is a strong answer. Specifying the estate end to end also means the on-camera analytics and the automated deterrence both land on hardware that supports them, which is where the third-party path gets complicated.
If your cameras come from four manufacturers, some are analog, and the ones you own must run full AI, the Command Connector path adds hardware, channel licenses and documented stream conditions that part of your fleet may not meet. That is the case a camera-agnostic platform is designed for.
Spot AI connects to any ONVIF or RTSP IP camera and brings legacy analog in through the Intelligent Video Recorder, runs AI Security Guard across the whole fleet and deters with talk down, strobes and horns through standard speakers. Full-resolution video stays in the building, and only event metadata goes to the cloud.
The one-to-one comparison goes deeper on architecture and capability, and the limitations page walks through each documented constraint with its workaround. Both are worth reading before a shortlist call, because most of the distance between these two platforms is structural rather than a feature either side lacks.
The cheapest way to settle it is to run both on your own cameras. Spot AI needs no camera purchase to pilot, so the test is a week of live feeds instead of a procurement cycle.
See what the AI catches on your live feeds before any hardware decision.
Customer-reported outcomes from named Spot AI customers.
Silver Bay Seafoods replaced fragmented legacy camera systems across 22 locations, including remote Alaska facilities, and lifted operational efficiency 15%.
Liberty-Perry School District resolves incidents in about five minutes, after evaluating ten systems before choosing Spot AI.
Cambridge City cut footage search from two hours to 30 seconds after consolidating seven municipal locations on one platform.
"The biggest benefit of Spot AI is how easy it is to look up incidents, see the footage, and then share it and collaborate."
Yes, for the right profile. Verkada is a mature single-vendor cloud platform that consolidates cameras, access control, sensors, alarms and intercoms in one console, with on-camera analytics on second-generation hardware and newer. It fits best when a team standardizes on Verkada hardware. Buyers keeping a large mixed camera fleet should price the Command Connector path carefully first.
Yes. Verkada states that Command Connector is officially recognized as an ONVIF Profile S conformant client and can ingest feeds from RTSP-compatible cameras that are not ONVIF Profile S conformant. Documented conditions apply, including the same LAN with no dynamic NAT or L3 translation, 2MP to 4K, 5 to 20 FPS and no B-frame support.
Dependency rather than missing features. Automated audio deterrence works with the BZ11 horn speaker and Verkada Intercom models, bridging existing cameras adds Command Connector hardware from $4,499 plus channel licenses, and Command Connectors must reach a published list of cloud endpoints. A 2024 FTC order also stays part of any security review.
Verkada is cloud managed, and the retention sits on the camera itself: onboard retention runs from 30 to 90 days up to 30 to 365 days depending on the model. That means an evidence policy can be checked against the camera list rather than against a plan tier, and it is why the design does not need a separate recorder at every site. Check the window published for each model you own before you write the retention policy.
It depends on your starting point. If keeping existing cameras and running full AI on all of them matters most, a camera-agnostic platform such as Spot AI fits: 15+ pre-trained Video AI Agents run across the fleet already installed, AI Security Guard handles detection and deterrence on those same cameras, and Iris builds anything the shipped set does not cover in natural conversation. The alternatives roundup compares seven options side by side.