Verkada limitations: what Verkada cannot do

Verkada limitations: what Verkada cannot do

Verkada is a capable, well-funded cloud video security platform, and for many single-site and standardized deployments it works well. The honest limits show up at the edges of that model: full AI analytics and Verkada's AI-Powered Deterrence require Verkada's own cameras and audio hardware, the platform is cloud-managed, cost and lock-in scale with the hardware you add, and a documented 2021 breach plus a 2024 Federal Trade Commission (FTC) order sit in every serious security review. The FTC found that a threat actor accessed roughly 150,000 live camera feeds in March 2021, and Verkada later agreed to a $2.95 million penalty and a mandated information security program (Source: Federal Trade Commission). This guide lays out what Verkada cannot do today, each point tied to Verkada's own documentation or a government source, so you can decide with clear eyes.

The table below summarizes each documented limitation, its operational impact, and a practical workaround. Details and sources follow in the sections beneath it.

Where Verkada is genuinely strong

A fair limitations review starts with what Verkada does well, because those strengths are why it lands on so many shortlists. Verkada pairs its own cameras with a clean, cloud-based dashboard, so a security team gets a single pane of glass without standing up its own servers. Deployment is straightforward when you buy the full stack, brand recognition is high, and the hardware is well built. For a single site, a new build, or an organization that is happy to standardize on one vendor's cameras, that turnkey experience is a real advantage.

Verkada also earns credit for opening up. Its Command Connector now bridges non-Verkada cameras into the platform, which many buyers still do not realize. So the limitations below are not about missing features. They are about where the model gets expensive, dependent, or hard to reverse as you scale across many sites.

Full AI analytics and deterrence require Verkada hardware

Verkada supports third-party cameras, and this is the most misreported fact about the platform. Command Connector is officially recognized as an ONVIF Profile S conformant client, and it can also ingest feeds from RTSP cameras that are not ONVIF conformant. So a claim that Verkada only works with its own cameras is simply inaccurate.

The accurate constraint is narrower and more important. On third-party cameras, Verkada delivers many, not all, of the platform's benefits, and those cameras run with reduced analytics compared with Verkada's own edge-compute cameras. Verkada's AI-Powered Deterrence, in public beta, is the clearest example: it works with a defined set of Verkada audio devices, and the supported speakers are the BZ11 Horn Speaker and Verkada Intercom models. Per Verkada's materials, the deterrence experience also expects current-generation Verkada cameras.

Operational impact: if you want the full AI experience, including automated audio deterrence, on a mixed or existing camera fleet, you end up buying Verkada cameras and Verkada audio hardware for those zones. The camera compatibility is real, but the AI ceiling on non-Verkada cameras pushes serious deployments back toward Verkada hardware.

Workaround: use Command Connector to keep existing cameras for viewing and recording, and reserve Verkada camera-and-speaker spend for the specific entrances, lots, or docks where you need native analytics and deterrence. Map that hardware list before you sign, because it drives the real budget.

Cloud-managed architecture and connectivity dependency

Verkada is a cloud-managed platform, and Command Connector is designed to communicate with Verkada Command in the cloud. Verkada's own network guidance lists a set of cloud endpoints that must be reachable through the firewall for the connector to function. That cloud-first design is what makes the dashboard so easy to use from anywhere, and it is also the dependency to plan around.

Operational impact: remote viewing, alerting, and cloud features rely on connectivity to Verkada's services and on the upload bandwidth at each site. Verkada does not publish specific bandwidth thresholds for streaming, so those figures are best described as not publicly specified and confirmed in a pilot. For a bandwidth-constrained site, or one with strict data-residency rules about video leaving the building, the cloud-managed model deserves a close look.

Workaround: size each site's network and WAN for concurrent streaming, and validate retention and offline behavior during a proof of concept rather than assuming it. If keeping full-resolution video inside the facility is a hard requirement, weigh a hybrid edge-to-cloud architecture that sends only metadata across the network.

Hardware cost and platform lock-in

Because the richest features are tied to Verkada's own cameras, speakers, and Command Connector appliances, cost and lock-in tend to grow together over time. Each Command Connector supports a maximum of 20 RTSP channels, so large third-party fleets need multiple appliances, and every zone where you want native AI is another Verkada camera. As sites and refresh cycles add up, the path of least resistance is to keep buying Verkada hardware.

Operational impact: switching cost rises as the fleet standardizes on one vendor's hardware, and expansion decisions get anchored to that vendor's roadmap and price list. Verkada does not publish per-camera list pricing, so the exact figures are not publicly specified in its own documentation. For a documented look at the third-party ranges buyers report, see the pricing breakdown linked below.

Workaround: phase your rollout, keep existing cameras in service, and model the multi-year hardware commitment before you standardize. Our Verkada pricing guide for 2026 lays out the cost components buyers weigh, and the Spot AI vs Verkada comparison shows how a camera-agnostic model changes the math.

A data-security track record that shows up in procurement

For regulated buyers and committee evaluations, Verkada's security history is a documented consideration, not a rumor. In August 2024 the FTC announced an action requiring Verkada to build a comprehensive information security program after finding it had failed to use appropriate security, which allowed a threat actor in March 2021 to remotely access customer camera feeds. The FTC noted roughly 150,000 live feeds were exposed, including cameras in sensitive locations. Verkada agreed to a $2.95 million penalty tied to separate CAN-SPAM allegations, and the order bars future misrepresentations about its privacy and security practices while requiring third-party audits (Source: Federal Trade Commission).

Operational impact: security, IT, and legal reviewers raise this history unprompted, especially for schools, healthcare, and other sensitive sites. It rarely ends a deal on its own, but it does add diligence steps and questions that slow procurement.

Workaround: ask for Verkada's current SOC 2 report and the specific remediations and audit attestations tied to the FTC order, and document data-residency and access controls as part of your evaluation. A vendor that keeps full-resolution video on-site and sends only metadata to the cloud gives your reviewers a smaller attack surface to sign off on.

When Verkada is still the right fit

None of this means Verkada is the wrong choice everywhere. It remains a strong option in several clear cases:

1. Single-site or new-build projects where standardizing on one vendor's cameras is acceptable and even preferred.
2. Smaller teams and public-sector buyers who want one turnkey vendor for hardware, software, and support.
3. Organizations already on a camera refresh cycle, where buying new cameras is happening anyway and the all-in-one experience is worth the premium.

The limitations bite hardest in the opposite profile: many sites, a large base of existing or mixed-brand cameras, tight bandwidth or data-residency rules, and a mandate to add real-time deterrence without a hardware overhaul.

How Spot AI addresses the gaps

Spot AI is built for that harder profile, and the contrast with Verkada is architecture and cost, not whether Verkada has features. Spot AI is camera-agnostic: it works with the cameras a business already owns, any ONVIF IP camera across roughly 100 brands with full functionality, and legacy analog cameras through the Intelligent Video Recorder (IVR). There is no rip-and-replace, and most sites go live in days.

On architecture, Spot AI uses a hybrid edge-to-cloud design. Full-resolution video stays inside the facility, and only metadata crosses the network, which keeps deployments PCI-clean and light on bandwidth. On deterrence, the AI Security Guard runs active deterrence, including AI Talk Down, on existing cameras with standard speakers, so you do not need a proprietary horn or intercom to call a person out and de-escalate in real time. Spot AI maintains NDAA-compliant practices and SOC 2. The table below compares the two on the criteria that drive multi-site decisions, using documented capabilities and marking gaps as not publicly specified.

The practical result is that customers report keeping their existing cameras while still getting real-time detection and deterrence. One property group standardized its video program across existing and newly acquired sites without swapping out the cameras that were already installed. A top-five North American electric-vehicle charging network reports reducing copper-theft incidents by about 80 percent using autonomous deterrence, with no human monitoring, on its existing camera footprint. And a national self-storage operator reports that once Spot AI was in place at a previously targeted facility, the perimeter break-ins stopped.

The biggest benefit of Spot AI is how easy it is to look up incidents, see the footage, and then share it and collaborate.

Ben Grady, Manager of IT and Database Administration, Nashville Rescue Mission

Even at a fraction of the fully loaded cost of added staffing, technology that works on existing cameras changes the buying decision. For context, the median annual wage for security guards was $38,370 in May 2024, and the field is projected to see little or no employment growth through 2034 amid persistent turnover (Source: U.S. Bureau of Labor Statistics). That labor math is part of why teams look for deterrence they can run on the cameras they already own.

If you are weighing Verkada against a camera-agnostic model, the fastest way to see the difference is a short pilot on your own cameras. Book a demo to see how Spot AI turns existing cameras into AI coworkers that detect, deter, and document in real time. To keep researching first, compare the options in our Verkada alternatives for 2026 roundup, the broader best video management software for 2026 guide, and the enterprise video security buyer's guide.

Frequently asked questions

What are the main limitations of Verkada?

The core limits are that full AI and AI-Powered Deterrence require Verkada's own cameras and audio hardware, the platform is cloud-managed, and cost and lock-in grow as you standardize on Verkada hardware. A 2021 breach and a 2024 FTC order also remain part of any security review. Third-party cameras are supported, but with reduced analytics.

Does Verkada work with third-party or existing cameras?

Yes. Verkada's Command Connector is an ONVIF Profile S conformant client and can also ingest RTSP camera feeds, so it supports many non-Verkada cameras. The tradeoff is that those cameras run with reduced analytics, and each Command Connector supports a maximum of 20 RTSP channels.

Does Verkada's AI deterrence work on any camera?

No. Verkada's AI-Powered Deterrence is in public beta and works with a defined set of Verkada audio devices, specifically the BZ11 Horn Speaker and Verkada Intercom models, and it expects current-generation Verkada cameras. Automated audio deterrence therefore depends on buying Verkada hardware.

Is Verkada secure after the 2021 breach and the FTC order?

The FTC's 2024 action requires Verkada to run a comprehensive information security program with third-party audits and bars misrepresentations about its practices, following a 2021 incident that exposed about 150,000 live feeds. Verkada also paid a $2.95 million penalty tied to CAN-SPAM allegations. Buyers should request the current SOC 2 report and the order's remediation attestations.

What is the best alternative to Verkada for multi-site operations?

It depends on your camera fleet and data-residency needs, but camera-agnostic, edge-first platforms are the common answer for multi-site buyers who want to keep existing cameras. Spot AI works with any ONVIF IP camera and legacy analog through the IVR, keeps full-resolution video on-site, and runs active deterrence on standard speakers. Compare options in the Verkada alternatives guide linked above.

About the author

Joshua Foster is an IT Systems Engineer at Spot AI, where he focuses on designing and securing scalable enterprise networks, managing cloud-integrated infrastructure, and automating system workflows to enhance operational efficiency. He is passionate about cross-functional collaboration and takes pride in delivering robust technical solutions that empower both the Spot AI team and its customers.