Verkada runs cameras and access control from a browser console with no recorder on site, and licenses each device on a recurring basis. SecureComm installs and services Verkada systems across Denver and Colorado, covering bandwidth and retention planning, door hardware, camera design, network work and the decision about which sites belong in the cloud.
Verkada is a cloud platform with cameras and doors attached. The camera is a network device with local storage, the recorder is a subscription, and the console is a browser page, which is why a two-person facilities team can watch four buildings from a laptop without a server room or a client install. The appeal is administrative as much as technical: one account, one device list, one place to add a camera or a cardholder. There is no backup appliance in a closet and no software version to keep current by hand.
That shape suits some sites and fights others. A cloud system moves cost from capital to recurring, moves video off the premises and turns the internet link into a piece of security infrastructure rather than an office utility. We look at upload capacity, the retention the organization actually needs and the rules it operates under before recommending it, and we say when a recorder on site is the better answer. The strongest case for cloud in this metro is usually a staff covering several buildings with no dedicated technician among them.
A console instead of a recorder
Cameras connect by Ethernet and draw power over the same cable, keep recent video on their own storage and send it to the vendor’s cloud; a switch, a UPS and a working internet link are the site-side infrastructure. Firmware arrives from the vendor rather than from a maintenance visit, and a failed camera is a swap and an address rather than a recorder change. Access control is administered in the same console, with doors, schedules, groups and credentials beside the camera list. The site still keeps a switch and enough power capacity for every camera, and those are the parts of the design an installer has to get right.
The door itself has not changed. Every opening still needs locking hardware that matches the frame, a power supply with battery backup, a request-to-exit device, a door position switch and free egress, and none of that is in the subscription. What the cloud controller removes is the server and the client software; what it adds is a dependence on the network path and a decision about how a door behaves when that path is down. That behavior differs by controller, so it is confirmed per opening, and it becomes a commissioning task: the person who installs the reader tests what happens when the network is unplugged.
Licensing, retention and the upload link
Licensing is per device and recurring, which makes camera count a permanent line in the operating budget rather than a one-time purchase. Retention is usually part of the license tier, so the honest comparison is total cost across the life the organization plans to keep the system, not the first invoice. Adding a camera later adds a license, adding retention may move every device to a different tier, and a site that expects to grow should model that before signing a multi-year term. We keep the vendor’s current quote beside our design so the customer can see which part of the cost is the platform and which part is the building.
Bandwidth is the second design input and the one most often discovered late. Cloud recording puts video on the upload path, and business internet is usually asymmetric, with far more capacity down than up. A link sized for point-of-sale and email will not carry a camera list chosen for coverage, and the symptom is not an outage but a gap in recorded video that nobody notices until it is needed. We measure the upload at each site, then set frame rate, resolution and camera count against it. Where the upload is short, local storage buys time but does not carry live viewing, and the customer should know that before the cameras arrive.
Privacy, retention and where cloud does not fit
Video in the cloud is video outside the building, which is a governance question before it is a technical one. Who can see which site, whether single sign-on and multi-factor are required, how long footage is kept, how a clip is exported, what the vendor’s staff can reach and under what policy are all answered in writing. Retention deserves particular care, because a policy that promises thirty days is worth nothing if the subscription keeps less or if nobody set the rule. A written data-handling summary kept with the system documentation is worth more than a promise made in a sales meeting.
Cloud fits a multi-site operator with a thin IT team, a building with no server room, or an organization that would rather pay monthly than replace a recorder every few years. It fits badly where the upload cannot carry the camera count, where recordings may not leave the premises, where retention runs to years, or where the camera estate is large enough that recurring licenses pass the cost of owned infrastructure. We price those cases both ways rather than argue a preference. For a small building with a compliant link, the subscription often costs less than the labor of looking after a server.
Compare Verkada
Services for Verkada systems
Related:Access control solutionsSecurity camera systemsIntegrated security systems
Frequently asked questions
What happens to Verkada video if the internet link fails?
Cameras keep recording to their own storage while the link is down and send their video when it returns, so footage is not lost, but live viewing and alerts are unavailable until the connection comes back. Doors are the more important question: whether a controller keeps granting access with cached credentials during an outage depends on the controller and its configuration, so we confirm that per opening rather than promise it.
How does Verkada licensing behave over a long term?
It is a subscription, per device, with retention tied to the tier, so the cost recurs for as long as the system is used and does not fall as the hardware ages. A five-year view usually separates two options that look close in year one. We build that comparison with the customer and confirm current terms with the vendor, because license structure changes and our numbers are only as good as the quote.
Can we run cloud cameras at one site and recorders at another?
Yes, and mixed estates are common. A warehouse with a heavy camera count and long retention may stay on a recorder, while a front office, a gate and a set of doors go to the cloud for remote administration. The boundary should follow bandwidth, retention and who needs access, not a preference for one brand. We design the split and document where each recording lives.
Last reviewed: