A version of this question lands in our inbox almost every week:
“We’re refreshing cameras. Should we go Verkada or Avigilon?”
It’s a fair question. Both vendors sell into the SMB and mid-market space, both have credible roadmaps, and both will do a good job covering a 25-person law firm or a 4-location healthcare practice. The honest answer is that the right one depends on a small number of variables — most of which have nothing to do with image quality.
This post is what we tell clients on the first scoping call. It’s deliberately not a feature-by-feature spec sheet (every vendor’s website does that better than I can), and it isn’t an opinion piece — Blue Cap IT deploys both platforms across MD, DC, VA, DE, PA, and NC, and we get paid the same either way.
The buyer landscape: who each is built for
Verkada was built cloud-first, sells direct or through partners, and pitches itself as the “we replaced the DVR” platform. Their value proposition is that everything — cameras, access control, alarms, environmental sensors — runs from one cloud dashboard with no on-prem servers, no port forwarding, and no DVR-in-a-closet to babysit. The buyer they win is the IT director who is tired of managing recording infrastructure or the multi-site owner who wants visibility from a phone.
Avigilon (now part of Motorola Solutions) was built around enterprise-grade analytics on its own appliance. Their historical strength is high-density camera deployments, sophisticated VMS (video management software) features like Appearance Search, and the kind of integrations that municipal, education, and large enterprise buyers care about. The buyer they win is the security director at a 200-camera facility who needs deep search across years of footage, or the integrator who wants to mix camera brands.
For an SMB in our footprint — let’s say 8 to 50 cameras across one to four locations — both platforms will do the job. The decision is mostly about how you want to operate it after install day.
The five-year cost reality
This is where most comparisons go sideways. Verkada’s all-in pricing (camera + cloud license) looks high on day one because there is no separate NVR purchase. Avigilon’s appliance-based pricing looks low on day one because the recurring cost is hidden in your maintenance contracts and your future appliance refresh.
The honest five-year math for a typical 12-camera SMB deployment we’ve quoted recently:
A Verkada deployment runs higher in years one through three because the licensing is bundled with the cameras, billed annually. By year five, the math narrows considerably — you’ve avoided an appliance refresh, you’ve avoided a few hundred hours of someone (you, your MSP, or a cousin who knows IT) keeping a recording server alive, and you haven’t had a “the NVR’s hard drive failed and we lost two weeks of footage” incident.
An Avigilon deployment is cheaper through year three if everything goes right and you’ve already got the IT muscle to maintain the appliance. By year five, your appliance is approaching end-of-life, your VMS has had three major version upgrades, and the savings have been spent.
The TCO conversation is rarely the deciding factor. The operational conversation is.
Cloud-first vs. on-prem: what actually changes day-to-day
Three operational differences matter more than the price line on a quote.
Where the recording lives. Verkada records to local storage on the camera itself, then mirrors to the cloud on a configurable schedule. Avigilon records to an on-prem appliance. If your internet drops, both still record locally. But if your appliance dies, Avigilon stops. If a Verkada camera dies, you lose only that camera, and the cloud copy survives.
How upgrades happen. Verkada pushes firmware automatically. Avigilon firmware is a project — scheduled, tested, rolled out by someone in IT. For an SMB without dedicated security IT staff, “automatic” wins almost every time.
Where you watch the feed. Verkada is browser plus phone, full-featured on both. Avigilon’s strength has historically been a thick-client Windows app with rich features; their cloud and mobile experience has improved but lags. If your buyer is a non-technical owner who wants to glance at a phone from a soccer field, that matters.
Where Avigilon still wins
I’d recommend Avigilon (or pause the Verkada conversation) in three specific situations:
If you have an existing camera fleet from another vendor that you’re not ready to throw away, Avigilon’s VMS will absorb mixed brands more gracefully than Verkada will. Verkada is a closed ecosystem — their platform requires their cameras.
If your buyer needs sophisticated post-event search at scale — searching for “person in red shirt” across two years of footage, license plate recognition with database integration, or multi-camera follow — Avigilon’s analytics still have a depth advantage for the high-end use case. Most SMBs don’t need this. Some do.
If your client has a regulatory or contractual requirement that recordings cannot leave their premises, Avigilon’s on-prem default is the easier story. Verkada can be configured for local-only, but the platform’s design assumption is cloud.
A decision framework
When a client asks us this question, we narrow it down with five questions:
How many cameras and how many locations? Under 50 cameras across under 5 locations, Verkada’s operational simplicity almost always wins. Above that, the conversation gets more nuanced.
Do you have IT staff who will own the camera platform? If yes, Avigilon is workable. If no, Verkada — because the platform expects nobody is babysitting it.
Do you have an existing camera investment to preserve? If yes, Avigilon. If no, the field is open.
Will the primary user be a technical operator or a business owner? Technical operator can use either. Business owner — Verkada’s interface wins by a mile.
Are there contractual or compliance reasons recordings must stay on-prem? If yes, default to Avigilon and make Verkada justify itself.
Most SMB conversations land on Verkada through this framework. Most enterprise conversations land on Avigilon. The interesting middle is the mid-market organization with 50–150 cameras and a one-person IT team — that’s where the conversation actually has to happen.
What we’re seeing in the field
In the last 18 months across the Blue Cap IT footprint, we’ve deployed roughly four Verkada systems for every one Avigilon system. That ratio reflects the SMB skew of our client base, not a general superiority — it’s just where most of our buyers fit on the framework above. The Verkada deployments we’ve done are typically 8–30 cameras with access control. The Avigilon deployments are typically larger sites where someone in-house already knows the platform.
Either way, the failure mode we never want to repeat is the one that motivates this whole category: a four-year-old DVR sitting in a closet, recording to drives nobody has checked in eighteen months, accessed via a port-forward that the previous IT person set up and never documented. Whatever you choose this year, the goal is to be done with that.
Talk to Blue Cap IT about Verkada or Avigilon
If you’re refreshing cameras for an SMB in MD, DC, VA, DE, PA, or NC and want a 20-minute scoping conversation that produces an honest comparison quote — not a sales pitch — reach out. We deploy and support both platforms. We’ll tell you which one fits your situation and quote it accordingly.