Skip to content

WestPoint · Verkada Command

It simplifies a lot and it ties you down a lot. Both are true.

Verkada does not sell only software: it sells the camera and the system together, managed from a web page and with no recorder at the site. That removes half a list of classic problems and puts others in their place. Here are the two sides.

The recorder that is not there.

It is the underlying change, and everything else comes out of it.

In a normal installation the video goes to a recorder that lives at the site: the one that fills up, the one nobody updates, the one nobody looks at until it fails and, when things go really wrong, the one they take away with the recordings inside.

Verkada takes it away. Each camera records inside itself and what goes up continuously is thumbnails and data about what it has seen, enough to open the timeline of any camera at any site. The piece you ask for is fetched from the camera at that moment.

It solves the problem of anyone with twenty shops or eight schools and nobody technical in them: no twenty recorders to maintain, no twenty networks to open, and the day somebody leaves the company their access to all twenty is removed at once.

And the other side, which arrives just as fast: the system and the hardware go together. The cameras are theirs, the software is theirs and the way in is their web page. There is no way to keep just half of it.

How it is built.

Five things, and here not one of them can be swapped for another.

  • The camera is the recorder: it carries its memory inside. The days it keeps depend on the model and on the quality, and it is the first number you have to ask for in writing — it is not the same across the range and it decides what you get back when somebody reports late.
  • The cloud is the console and the index: users, permissions, alerts, search and a log of who has looked at what. Keeping full video beyond what fits in the camera is cloud archiving, and it is paid for separately. If somebody says «everything is stored in the cloud», ask how much, from which cameras and at what price.
  • Scaling means adding cameras, not sizing servers: there is no CPU or drive calculation. What you do have to work out is each site's network and the switch's power ports, which is where the unforeseen bills turn up.
  • Redundancy: each camera is independent, so no fault switches off the installation. And the other way round — if somebody rips out the camera that was recording precisely that, it is lost: there is no second copy at the site. At a critical point you solve it with two cameras or with cloud archiving.
  • Access control, alarms and intercoms are from the same house and live in the same console: a forced door brings its video with nothing to integrate. There is an API for pulling events out and a connector device for bringing in IP cameras you already have — which models get in, with which functions and under which licence is a question for the manufacturer, and you have to have the answer before you sign.

The five questions about the cloud.

Not one of them is really technical. All five are contract questions, and they get answered before you buy or they never get answered.

Where the recordings live and who can get in. The video, in the camera; the index, the users and the permissions, at the supplier — which by design has an administration route into your system. That calls for minimum permissions, mandatory two-factor, an access log you can see, and in writing who at the manufacturer can see what. There have been incidents like that in this industry, and trust does not prevent them.

What happens when the line goes down. Recording carries on, because it records in the camera. What you lose is the console: no live view from outside, no alerts, no search. For most installations that is fine; for a control room watching live, it is not.

The cost of uploading video. Continuously it uploads little. The usage appears when somebody watches and it multiplies by each person watching at the same time: a shop with a tight line works right up to the day of the incident, which is when three people open six cameras.

RGPD and international transfers. A supplier from outside the EU: you have to be able to explain to a supervisory authority which region the data is stored in, which processor contract and which safeguards cover the transfer, and what analysis was done beforehand. You ask for it in writing for your contract and your region. And then there is the part that gets forgotten: telling the staff, and making the record of processing activities say what really happens.

And the dependency. The day you want to leave, the cameras do not go with you: they cannot be reused with another system. The recording is got out by exporting while the licence is alive, and when it expires there is no local way in to see what is inside. It is not a hidden defect, it is the model — what you cannot do is find it out in year five.

The licence, which here is half the decision.

Per camera and per term: the camera comes with a licence of several years that includes the console, updates, support and the equipment warranty while it is alive. It is easy to budget for and it has one consequence worth saying out loud — when the term ends, it gets renewed. It is not optional maintenance: it is what keeps the system standing.

As you grow the cost is linear. What gets neglected is the calendar: if the cameras came in batches, the renewals fall in different years. In any proposal with this model we put in writing the term, what it includes and the cost of the following years; comparing this with a perpetual licence by looking only at the first year is the most common way of getting it wrong, in both directions.

Who it fits, and who it does not.

It is the platform that most clearly either fits or does not. There is almost never a middle ground.

It fits if…

You have many similar sites and few technical people: retail, schools, clinics, offices. If you want video, doors and alarms on the same screen with no integration project. If you value a new employee knowing how to use it in ten minutes. And if the installation is new, because then hardware tied to the system costs less to accept.

It does not fit if…

You already have good, recent cameras you do not want to throw away and the connector does not cover what is there. If the specification requires that the recordings do not leave your premises, or that the supplier has no administration route. If you watch live and a line failure is unacceptable. Or if house policy is not to depend on a single supplier for hardware and software: here that cannot be met.

Analytics: what comes with it, what you can add and where the ceiling is.

It comes with plenty of it, and well sorted: search for people and vehicles, filters by colour or by clothing, number plates on the models that carry it, alerts by zone, occupancy and heat maps. It runs in the camera and in their cloud, so there is nothing to set up — and that is what makes people use it instead of leaving it switched off, which is the fate of half the analytics ever sold.

What you add is limited by the same design that makes it comfortable: the functions are the manufacturer's and there is no way to put a detector of your own inside their camera. If your case is «alert me when this machine does this», the answer will be the closest function in the catalogue.

The ceiling: it is search and alert analytics, not understanding. It is very good at finding the person in the red T-shirt among six hours of recording; it does not say whether what they are doing is working or is a problem. For many installations that is enough; for a plant, a loading bay or a site, it is not.

And the recommendation, with its warning: in the same house there is IRIS Neural, the NVMS from Infinity Neural, the other company in the group — our own product, and we say so before recommending it. In many installations they live together: the VMS governs cameras and recording, IRIS brings the understanding of the scene. Here we have to be honest about the how: their cameras do not hand over an open stream to any system, so living together is solved with cameras of our own at the points that have to be understood, or by checking beforehand what access to the video your licence allows.

What we do.

With a platform like this half the trade disappears and the other half weighs more.

  • The design, which here is nearly everything: with no recorder to size, what decides whether the system is any use is where each camera goes, with which lens and what can be seen from there at eleven at night. The model is chosen for what it has to see and for the days it keeps.
  • The sizing that is left: each site's network, the switch ports and power, the upload available for when somebody has to watch, and days of recording in the camera according to how long somebody takes to report a problem at that installation.
  • The contract part, which in this model is technical work: terms, what the licence includes, the storage region, the processor contract and the cost of the following years, in a table you can take to a committee.
  • The implementation: registering the sites, permissions by profile, two-factor with no exceptions, alerts that reach somebody with a name, and a camera-by-camera check by day and by night. And the migration: what gets reused with the connector and what does not, and exporting from the old system whatever has to be kept before switching it off.
  • The maintenance, which changes in content: fields of view, cleaning, cameras that have stopped seeing properly, permissions nobody needs, licences that expire and the log of who has looked at what. And giving warning of the renewal in good time.

Who operates it after we leave.

It is the platform that needs a technician least in order to work, and the one that most needs somebody who is really in charge of the permissions.

  • IT, and it is best that it takes this on: accounts, two-factor, sign-in through the company directory, each site's network and reviewing the access log. With no servers and no drives, IT's work here is identity and network.
  • Security, and more than on other platforms: day-to-day use is a web page and it is learned in a morning. Watch, search, bookmark, share a video with a link that expires, deal with an alert. This part stays entirely with the security team, and it is the platform's biggest argument.
  • The real border is not technical, it is governance: who can see what. When giving access is that easy, the system ends up with twenty people seeing everything and nobody remembers why. That review belongs to whoever answers for the data, not to whoever administers it.
  • What it demands of the integrator is fewer hands and more judgement. Nobody calls us because a drive has filled up; they call us when it has to be extended, when a camera stops seeing what it used to see, when a renewal has to be negotiated or when the system has to be explained to an inspection.
  • Training: half a morning for whoever watches and searches, and a session with IT and with whoever answers for data protection on permissions, the access log and what can be done with the recordings. The second one nearly always gets skipped and it is the one that prevents the serious problems.
  • Documentation: a sheet for each camera with what it sees and the days it keeps, a map of sites and profiles, a table of licences with their renewal, where the data is stored and under what legal cover, and the export procedure. All in the customer's name, including the administrator account.

Get started

Does tying the hardware to the system fit you?

That is the Verkada question and the customer answers it, not us. If you tell us how many sites you have, which cameras are installed, how many people are going to watch and what your data policy requires of you, we will tell you whether this makes your life simpler or whether in your case the price of the convenience is too high.