What a VMS Really Costs: Per-Camera Licensing Over Five Years

Ask an installer what a CCTV system costs and you will get a number for cameras, cable, containment, a recorder and labour. Ask what it costs over five years and the answer usually changes shape, because the largest single line stops being hardware and becomes software licensing.

Almost every established video management system is priced the same way: a licence per camera, per year, paid to the software vendor. It is such a settled convention that it rarely gets questioned during design. It should be, because the per-camera model does two things — one financial, one commercial — and the second matters more.

Where the per-camera model comes from

Per-device licensing is a hangover from the era when a VMS was a Windows application on a server in a comms room, sold through distribution, and the channel needed a simple unit to quote against. A camera is a countable thing. Counting them made pricing legible to everyone in the chain.

It survived the move to the cloud because it is extremely good for the vendor. Revenue grows automatically as the customer's estate grows, with no additional sales effort and very little additional cost to serve. An extra camera on an existing gateway consumes a few more megabits and some storage. It does not consume another licence's worth of engineering.

That gap — between what a marginal camera costs to support and what it costs to licence — is the whole economics of the category.

The arithmetic, worked through

Take a mid-market VMS at a commonly quoted list price of around £85 per device licence, and run it across three estate sizes. These are list prices at the time of writing and real-world discounting off list is normal, particularly through distribution, so treat the figures as the shape of the problem rather than a quotation:

Estate	Device licences	Five-year licence cost
Small commercial site	24 cameras	~£2,040
Multi-building campus	120 cameras	~£10,200
Distributed estate	280 cameras	~£23,800

Now set that against the hardware. A competent commercial fixed dome sits in the low hundreds of pounds. At 120 cameras you are plausibly looking at £30,000 to £45,000 of camera hardware — and £10,200 of software licensing on top, recurring, for software that is doing broadly the same job at camera 120 as it was at camera 12.

Two things about that table are worth dwelling on.

It is linear when the cost to serve is not. The work of adding the 280th camera to a running system is close to the work of adding the 30th. The licence cost is nine times higher.

It penalises exactly the projects you want. The estates worth winning are the large, multi-site, growing ones. Per-camera licensing makes those the most expensive to quote and the hardest to expand, because every phase two carries a new licence conversation with the client.

The part that does not appear on the quote

The financial argument is the easy one. The commercial argument is the one that decides who still has the customer in five years.

When an installer specifies a third-party VMS, a set of things transfer to the software vendor along with the licence. The renewal invoice, and the annual conversation that comes with it. The support relationship for anything software-shaped. The upgrade roadmap, and therefore the timing of the next capital ask. The login screen the client's security team looks at every day, carrying someone else's logo.

None of that is unfair — the vendor built the software. But the cumulative effect is that the installer, who did the survey, pulled the cable, commissioned the system and answers the phone when a camera drops, becomes the party the client thinks of second.

The licence belongs to the vendor. The renewal belongs to the vendor. Over enough cycles, so does the customer.

This is why the licensing model is a channel question and not just a cost question. It determines whether the recurring revenue from an estate accrues to the business that installed it or to the business that wrote the software.

What the alternative looks like

There is nothing technically necessary about per-camera pricing. The alternative is to licence the deployment rather than the devices: a price per site, or per instance, that does not move when a camera is added.

That changes three behaviours immediately.

Estate growth stops being a commercial event. An engineer adds a camera because the client needs coverage, not after a licence has been raised and approved.

Quoting gets simpler and more competitive at scale. The bigger the estate, the larger the gap between per-site and per-camera pricing — so the model is strongest precisely where the good work is.

The recurring revenue can sit with the installer. If the platform is white-labelled — the installer's brand, colours, domain and company on the login screen — then the client's service relationship, and the renewal, stay with the installer. The software company sits behind them rather than in front of them.

That last point is the one worth testing against your own book. Look at the estates you maintain, add up the third-party software licensing your clients pay annually, and ask who invoices it.

What to check before you believe any of this

Licensing arguments are easy to make and easy to overstate. Four questions cut through most of it, whichever vendor is answering:

Is the price per camera, per site, or per instance — and what happens when the estate doubles? Ask for the number at 2× the current camera count, in writing.

What happens at the end of the term? Some models are subscriptions where the software stops; some are perpetual licences with optional support; some are perpetual with mandatory upgrade plans that behave like subscriptions. These are very different risks to carry into a five-year contract.

Does it read the cameras already on the wall? A platform that ingests existing devices over ONVIF and RTSP can be trialled alongside the incumbent system with nothing removed. One that needs its own hardware is a rip-and-replace, and should be priced as one.

Whose name is in front of the client? If the answer is the software vendor's, understand that you are renting the customer relationship for the length of the contract.

Where we stand on this

DevSpark builds a video management platform that is licensed per site rather than per camera, and white-labelled — the installer's brand in front of the client, with us behind them. We are an ONVIF member, and the platform ingests existing cameras over ONVIF Profile S and Profile T and over RTSP, including H.264, H.265 and thermal devices, so it runs alongside whatever is in place today.

We keep a written record of every camera model we have actually put through the platform, with the measurements that prove it, including what we have not tested. If you are answering a specification and need to know where a particular device stands, ask us for it.

If you install and maintain CCTV estates and the per-camera renewal line is a conversation you would rather stop having, get in touch — we set the platform up free on one site so you can judge it against what you use now.