Prosumer video systems in a commercial building: where they fit and where they don't

There is a category of video system that deserves better than the way our industry usually talks about it.

It is well designed and inexpensive relative to what it does. The app is genuinely pleasant, which is not a small thing after years of recorder interfaces that looked drawn in 2006. IT teams like it because it behaves like network equipment rather than an appliance. Small businesses like it because it is the first camera system they have owned that they actually open. UniFi Protect is the best-known example, and the reason it is the archetype is that it is good.

None of that is the question. The question is fit. This category gets deployed one size beyond where it belongs more often than any other product class we see, and when it goes wrong it is almost never because the pictures were bad. What comes apart is administration, evidence handling, and what happens when you need help.

This article is written to be useful to someone who already owns one. Most of the time the right answer is not "replace it" — it is "work out which of those three your building needs, and close that gap."

What this category actually is

The defining trait is not price and it is not resolution. It is the design centre: these systems are built for one site, administered by one competent person, who looks at the app. Setup assumes a single owner. Remote access is a vendor relay rather than a project. Storage sits in one place with one retention behaviour. Users are a short list.

That is a coherent product, and it is coherent because things were deliberately left out. The omissions are the subject of this article.

The difference is not image quality

Commercial-grade and prosumer-grade cameras have been converging on sensors, encoding and low-light handling for years. You cannot reliably tell the two apart from a still frame at a well-lit door. Anyone selling you on image quality alone is selling on the dimension where the gap has mostly closed.

The gap that has not closed sits in three places: administration — who can see what, change it, delete it, and how you prove any of that a year later; evidence handling — what comes out of the system when somebody outside your building needs to rely on it; and the support model — what happens between the moment something breaks and the moment it works again. Those three are where the money went in a commercial platform, and all three are invisible in a demo. A demo shows you the picture.

Administration: one owner does not scale to an estate

The first structural limit appears the moment there is more than one of something — more than one site, or more than one kind of user.

Central administration. Across a few sites, "log into each one" is a mild irritation. At an estate it is the failure mode: the site nobody visits stops recording, and the discovery happens on the day the footage is needed. Commercial platforms answer this with a management layer above the sites showing, in one view, which cameras at which locations are healthy — the same argument that drives the cloud versus on-premise recording decision.

Role separation. A commercial building needs several kinds of access to one system: a property manager who reviews everything, a tenant who sees only their own cameras, a supervisor who can pull an export, a contractor who services the system without watching it. Prosumer systems offer coarser roles, because their design centre is one person who holds all of them. The consequence is not missing permissions — it is wide ones.

Administrative audit. The question that matters after an incident is rarely "what did the camera see". It is "who looked at it, who exported it, who changed the retention". A platform that logs those actions to a record you cannot quietly edit is doing something structurally different from one showing a recent-activity feed.

If one owner-operator does all of that personally, none of it is a deficiency. With a management company, tenants, contractors and staff turnover, it is the whole ballgame.

Evidence handling: the export is the product

Here is the shift that catches people. For most of a camera system's life, its output is a picture on a screen. On the one day that justifies the whole investment, its output is a file that leaves the building — to an insurer, to counsel, to a tribunal, to a party you are in a dispute with.

At that point someone has to be able to say what the file is. Not "here is a clip" but: this is the original as recorded, here is the period either side of it, here is who had access, and here is why nothing changed between the camera and this file. That is chain of custody, and it is a property of the system plus the process around it — never of the footage alone.

Prosumer platforms do export. What they are not built to produce is that surrounding record — and as surveillance evidence in BC sets out, the file is the easy part.

There is a second, quieter obligation. British Columbia's Personal Information Protection Act requires an organization to "protect personal information in its custody or under its control by making reasonable security arrangements to prevent unauthorized access, collection, use, disclosure, copying, modification or disposal or similar risks" (s.34). Surveillance video of identifiable people is personal information, so your account structure, export path and retention setting all sit inside that duty. Section 35 pushes from the other side: information used to make a decision that directly affects an individual must be kept at least a year so that individual has a reasonable opportunity to obtain access to it, and material must be destroyed or de-identified once the purpose is no longer served and retention is no longer necessary for legal or business purposes.

Read together, retention stops being a preference. It becomes something the system must be able to do on purpose: hold what must be held, release what must be released, and not quietly overwrite the one thing somebody is entitled to see. Retention that is whatever the drive allows is fine right up until the day it has to meet an obligation.

Support model: a forum is not a support contract

This is the least technical difference and the most consequential. Consumer and prosumer ecosystems are supported by a community. The documentation is often excellent and the forums genuinely expert — better, honestly, than some paid support desks. But the structure is: you search, you post, you wait, and eventually a stranger who does not work for the vendor and owes you nothing may solve it.

Commercial support is a different structure. Someone answers. There is a response commitment, an escalation path, and a person whose job it is to own the fault until it closes. You are buying the answer, not the search.

Neither is better in the abstract. What matters is 06:00 on a Monday when nothing is recording and the person who set it up left in March. "We would search the forums" is acceptable for a two-camera shop and unacceptable for a building with tenants and a contractual security obligation.

Where prosumer video genuinely fits

A small single site. One building, one owner, a modest camera count, no tenants and no downstream obligations. This is the design centre, and the system does it well.

An owner-operator who will actually look at the app. The app being good is why the system stays maintained. A system somebody opens weekly gets its faults noticed; a "better" system nobody opens rots quietly.

A building with in-house IT already running that vendor's networking. If your team administers the switches, access points and firewall from the same console, adding video is a small increment owned by people who touch it daily.

A budget where the honest alternative is nothing. A prosumer system that exists beats a commercial system that never got approved. Coverage you have is worth more than coverage you were quoted.

Where it does not fit

Multi-site estates. Central administration and role separation are structural requirements, not preferences, and they are the two things this category deliberately leaves out.

Sites with a formal evidence-export requirement. If a lease, an insurer, a franchise agreement or a regulator specifies how footage is produced, the export path must meet that specification and be demonstrable in advance.

Buildings where video may end up in a proceeding. Not "might be interesting later" — buildings where disputes are normal: liability claims, employment matters, tenancy disputes. Somebody has to be able to speak to how the material was produced.

Anywhere requiring a monitored response. If the expectation is that something happens when an event occurs — a station receiving the signal, verifying it, dispatching an attendance — you are buying a monitored service with the obligations and listings that go with it, not a camera system with notifications.

Anywhere retention or export capability has to meet an obligation. The distinction is between "we keep about a month" and "we are required to keep this, produce it in this form, and prove we did."

If you already own one

Most buildings in the awkward middle do not need a replacement. They need three things closed.

Fix remote access first. If viewing from a phone was made to work by opening a port on your firewall, that is the highest-value correction on this page, and it is not expensive — see the port your installer opened.

Decide retention on purpose and write it down. Days of history, which cameras, who authorizes an early deletion, who is told when recording stops. Then confirm the system is achieving it.

Name the export path before you need it. Who produces a file, in what form, preserving the original, and who can explain it. Rehearse it once — an export first attempted under pressure produces a trimmed clip nobody can vouch for.

Two questions then decide whether you also need a different platform. Does anyone outside your organization rely on this system — an insurer, a tenant, a client, a regulator? And would a fault going unnoticed for a month be a nuisance or a serious problem? Two yeses point at a commercial platform. Two nos mean you already have the right system, and the money belongs in coverage instead.

If you do move later, the cameras decide how painful it is: cameras speaking open standards can generally be adopted by another platform, cameras bound to one ecosystem cannot, and the cabling carries over either way. See the open-platform VMS question and where your video lives. One caution, because "it supports ONVIF" is not a single fact: ONVIF deprecated Profile Q on April 1, 2022, because its specification "requires a Profile Q conformant device to allow anonymous access to all ONVIF commands during the setup process in the factory default state." Existing declarations of conformance remain valid indefinitely, so ask which profiles, and what they let you do.

Frequently asked questions

Is a prosumer system less secure than a commercial one?

Not inherently, and this category is often patched more diligently than the mid-range appliances it replaced. The difference is administrative: wider roles, weaker separation between who watches and who administers, a thinner record of who did what. Those matter more as the number of people with access grows.

Our IT team already runs this vendor's networking. Isn't that the whole argument?

It is the strongest single reason to choose this category, and it answers the support question — someone in-house owns it. It does not answer the evidence and retention questions, which are about obligations rather than competence.

The right size is a real question, not a sales question

We design, install and support commercial platforms, and we also work in buildings where the existing prosumer system is exactly right and the advice is to leave it alone and fix the three things around it. Both are real answers.

For a straight assessment of what is in your building now — what it covers, what it would produce on a bad day, and whether it is one size out either way — book a systems consult.

Sources

• Personal Information Protection Act, SBC 2003, c. 63, s.34 (protection of personal information — reasonable security arrangements), s.35 (retention and destruction) — https://www.bclaws.gov.bc.ca/civix/document/id/complete/statreg/03063_01
• ONVIF, Profile Q page (Profile Q deprecated April 1, 2022; existing declarations of conformance remain valid) — https://www.onvif.org/profiles/profile-q/