What Verkada's own documentation says it does not do, or only does under conditions, written for IT and security teams running due diligence. Every constraint below carries the documentation behind it, the operational impact, and the workaround.
Every constraint below comes from Verkada's own current documentation or a dated government record, checked on August 6, 2026. Where Verkada documents nothing, this page says so rather than guessing. Spot AI sells a competing platform, so nothing here rests on an anonymous source or an aggregated user rating, and two claims that circulate about Verkada are corrected on this page: it is not proprietary-cameras-only, and it does publish per-device MSRPs.
Verkada does support cameras it did not sell you. Its documentation also states the conditions, and those conditions decide whether reuse is real on an estate assembled over a decade.
A constraint list is only useful next to an honest account of the product.
Cameras, access control, environmental sensors, alarms, and intercoms are administered together in Command. For a team that wants one console and one support relationship, that is a smaller operational surface than assembling four products.
Verkada's pricing page lists MSRPs and license terms, for example a CD22 indoor dome camera at $799 MSRP and a one-year Workplace license at $3,600. Most platforms in this category publish nothing, so a budget can be modelled without a sales cycle.
Command Connector is officially recognized as an ONVIF Profile S conformant client and also ingests RTSP feeds from cameras that are not conformant, so a legacy fleet can appear in the same console.
Each one is a consequence of how the platform is designed rather than a defect. What matters is whether it collides with your starting point.
Non-Verkada cameras reach Command through Command Connector, an on-premises appliance. Verkada's pricing page lists the CC300 at $4,499 MSRP for up to 10 channels at 5MP, the CC500 at $6,999 for up to 25 channels, and the CC700 at $9,999 for up to 50, each noting that additional channel licenses are required.
A 120-camera estate across six sites needs connector hardware per site plus channel licenses, sized on 5MP channel capacity rather than raw camera count. That spend lands before any AI value is delivered, and it recurs as sites and cameras are added.
Phase the rollout site by site, and size connectors against 5MP channel counts rather than camera counts. Model three years rather than one, because channel licenses and retention tiers both scale with the fleet.
Verkada documents specific conditions for third-party cameras: ONVIF cameras must state ONVIF Profile S compatibility, cameras must sit on the same Local Area Network with dynamic NAT and L3 translation not supported, RTSP streams must run 2MP to 4K at 5 to 20 FPS with a GOV length of 80, and Command supports I-frames and P-frames only, with B-frames not supported.
These conditions decide whether camera reuse is real. A camera behind a routed site-to-site link, one encoding B-frames, or one running outside the frame-rate window will not simply appear in Command. On an estate assembled over a decade, that is rarely the whole fleet.
Audit the fleet against the exact list before committing: manufacturer, ONVIF Profile S conformance, codec profile, frame rate, resolution, and network path per site. Any camera that fails the list belongs in the budget as a replacement.
Verkada's AI-Powered Deterrence documentation names the supported speakers as the BZ11 horn speaker and all Verkada Intercom models. Supported cameras include second-generation cameras or newer, CF81-E cameras, intercom cameras, and third-party cameras, so the camera side is open while the audio side is not. Each camera supports one Deterrence Area trigger, the partition must be armed, and deterrence terminates after 5 minutes of inactivity or 15 minutes after the initial trigger.
Deterrence is where a video platform stops being a record and starts changing what happens during an event. Verkada's documented path adds a Verkada speaker or intercom at every deterrence point, on top of cameras and connectors, and the one-trigger-per-camera rule shapes how zones get designed.
Prioritize deterrence points instead of covering every camera, and price BZ11 or intercom hardware per location. Where a site already runs a public address system or standard speakers, a platform that drives those avoids the line item entirely.
Verkada states that Command Connectors require access to many endpoints to ensure they can communicate with Command and all features will be accessible, and publishes the allowlist, including api.control.verkada.com, firmware.control.verkada.com and relay.control.verkada.com, plus wildcard verkada.com and amazonaws.com endpoints and time.cloudflare.com. The documentation covers which endpoints must be reachable, not what happens when they are not.
Sites on constrained or intermittent links, and security teams that need a written answer on degraded-mode behavior, will not find one in the public documentation. The cloud-managed model also shapes the data-residency conversation, because more video and metadata leaves each site than in an edge-first design.
Ask Verkada in writing what continues to function without cloud reachability, and for how long, by site type. Put the answer in the evaluation record next to your retention and residency requirements.
In August 2024 the Federal Trade Commission announced an order requiring Verkada to implement a comprehensive information security program with third-party audits, and barring misrepresentations about its privacy and security practices, after alleging it failed to use appropriate security. The FTC states that a 2021 incident let customer camera feeds be accessed, including about 150,000 live feeds in sensitive locations. Verkada also agreed to a $2.95 million penalty tied to CAN-SPAM allegations.
Verkada has spent the years since under a remediation program, which is a reasonable answer to give a security committee. It also means the history surfaces in every vendor security review, so the evaluation needs current documents rather than a general assurance.
Request the current SOC 2 report and evidence of the order's remediation and audit requirements, and confirm the deployment meets your own retention and data-residency policy. Treat it as a documentation exercise rather than a disqualification.
The same five constraints in one view, sized to paste into an evaluation document.
Swipe the table sideways to see every column.
Verkada data comes from Verkada's own public documentation and the Federal Trade Commission's August 2024 announcement, checked on August 6, 2026. Gaps are marked as not publicly specified.
If you are specifying a site from scratch, want cameras, doors, sensors, and alarms from one vendor, and have hardware budget inside the project, most of the constraints above stop applying, because you are buying the native experience rather than bridging into it. Verkada's published MSRPs also make that project easier to budget than most alternatives in this category.
Spot AI takes the opposite architectural route, which is why its constraint list looks different. It is camera agnostic: any ONVIF or RTSP IP camera works with full functionality, and legacy analog cameras come in through the Intelligent Video Recorder, so a mixed fleet does not split into a supported half and an unsupported half.
Deterrence runs on the cameras already installed. AI Security Guard detects in context, then deters in seconds with talk down, strobes, or horns through standard speakers, so there is no audio device to buy per location. Full-resolution video stays on the IVR in the building and only event metadata crosses the network, which keeps the data-residency conversation short and the bandwidth bill flat.
The useful question is not which platform has fewer constraints, but whose constraints collide with the cameras, network, and sites you already have.
None of that makes Spot AI the right answer for every buyer. It is a video AI platform rather than a full physical security catalog, access control and environmental sensors arrive through integrations, and Spot AI does not publish list pricing either. A constraint list earns its keep by lining each platform's shape up against your starting point, and that starting point is usually the cameras you already own.
A live pilot on your cameras answers in a week what a spec sheet cannot.
Customer-reported outcomes from named Spot AI customers.
A top five North American EV charging network reports an 80% reduction in incidents with autonomous deterrence and no human monitoring.
Unique Industries covers more than a million square feet with a three-person safety team, catching near misses and falls on the cameras already installed.
Don Franklin Family of Dealerships had incident footage on responding officers' phones within four minutes of an alarm, and reported five recoveries within the hour.
"With Spot AI, these facilities are more secure and better watched than the ones we staff traditionally, where we pay for a full-time person on-site."
Five, all documented: bringing existing cameras in requires Command Connector hardware from $4,499 plus channel licenses; third-party streams must meet documented conditions including same-LAN placement, 2MP to 4K, 5 to 20 FPS and no B-frames; automated audio deterrence works with the BZ11 horn speaker or Verkada Intercom models; Command Connectors must reach a published list of cloud endpoints with no documented degraded mode; and a 2024 FTC order remains part of any security review.
Yes, and the correction is worth making plainly: Verkada is not proprietary-cameras-only. Verkada states that Command Connector is an ONVIF Profile S conformant client and can also ingest RTSP feeds from cameras that are not conformant. The real constraint is the documented conditions those cameras must meet, and the connector hardware they run through.
The camera side is broad: Verkada lists second-generation cameras or newer, CF81-E cameras, intercom cameras, and third-party cameras as supported. The audio side is not. Supported speakers are named as the BZ11 horn speaker and all Verkada Intercom models, so automated audio deterrence depends on Verkada audio hardware at each deterrence point.
The FTC's 2024 order requires Verkada to run a comprehensive information security program with third-party audits and bars misrepresentations about its practices, following a 2021 breach in which customer camera feeds were accessed, including about 150,000 live feeds. Verkada also agreed to a $2.95 million penalty tied to CAN-SPAM allegations. For an evaluation, request the current SOC 2 report and the remediation evidence rather than reading the history either way.
It depends on the camera fleet and the data-residency requirement, but camera-agnostic edge-first platforms are the common answer for multi-site buyers keeping existing cameras. Spot AI works with any ONVIF IP camera and legacy analog through the IVR, keeps full-resolution video on site, and runs AI Security Guard across the fleet from one dashboard.
Book a quick demo and see how the latest in video AI drives higher productivity and keeps every site secure — around the clock.
Request a Demo
.png)
.png)
.png)
.svg)