Open vs. proprietary mobile surveillance platforms

When a vendor says open, they could mean any of these, and the difference is material.

Open cameras (portable video)

The cameras publish standard streams — RTSP for transport, ideally ONVIF for discovery, configuration and control — so any compliant VMS can record and manage them. This is what lets a trailer feed a video system you already own. It is the most useful form of openness for an enterprise with an incumbent VMS.

Open hardware (any camera on the mast)

The trailer's mast, mounts, network and power budget will accept cameras from any manufacturer. Useful for integrators with strong camera preferences or specialised sensor requirements. Ask about the power budget specifically — a mast that physically fits six cameras may not have the watts to run them.

Open software (third-party cameras in the vendor's VMS)

The vendor's own platform will ingest cameras it did not make. Relevant if you want one console across trailers and existing fixed cameras from another brand.

A vendor can be open in one sense and closed in another. A trailer whose cameras stream RTSP but whose mast only takes the vendor's cameras is open on video and closed on hardware. Establish which you need before asking the question, because “are you open?” will get a yes from almost everyone.

Closed ecosystems are not a failure of engineering ethics. They are a legitimate design choice with real advantages, and the industry's largest deployments run on them.

It works out of the box

Cameras, analytics, power and software validated together means far fewer integration failures. A trailer that arrives configured and recording is worth a great deal on a site that needs coverage this week.

One party is accountable

When video stops, there is nobody to argue with about whose component failed. On an open stack, a camera vendor, a VMS vendor and a trailer manufacturer can each reasonably point at the others.

Analytics tuned to known hardware

Detection models trained against specific sensors, lenses and mounting heights generally outperform generic models. This is a real technical advantage, not marketing.

Simpler operations

One console, one permission model, one place to pull evidence, one support number. For a small security team this can matter more than any individual feature.

If your organization has no existing VMS, no in-house video engineering, and no expectation of changing platforms, a closed ecosystem is very likely the right answer and openness is a feature you will pay for and never use.

Openness pays in specific situations, and it is worth being precise about which.

You already run a VMS

If your team watches Genetec or Milestone all day, off-grid sites appearing in a second console is a genuine operational cost — missed alarms, split evidence workflows, duplicate training.

You are an integrator or dealer

Standardising many customers on one platform is the business model. Hardware that only works on the manufacturer's platform undermines it.

You need a sensor the platform vendor does not make

Specialised thermal, radiometric, acoustic or gas sensing, or an LPR engine with specific regional plate support. Closed ecosystems limit you to the vendor's catalogue.

The hardware will outlive the software decision

A trailer is a five-to-ten year asset; platform decisions turn over faster. This is the core argument, and the one to quantify.

Procurement requires it

Public-sector and critical-infrastructure buyers increasingly require open standards and documented exit paths as a condition of award.

From our review of public materials as of September 2026. Read “Not publicly specified” as unverified rather than absent — several of these providers sell a managed service where the platform question simply does not arise in their marketing.

Two things are worth drawing out of that table. First, open architecture is not one vendor's differentiator — at least two providers take an explicitly open position, and they do it differently: one supplies no software at all and integrates with yours, the other supplies software but publishes standard streams so you are not obliged to use it. Second, the providers that do not publish a position are mostly service-led, where the platform is part of what you are buying rather than a component you select.

Name a customer running this on the VMS I use.

Claimed compatibility and deployed compatibility are different things. A vendor who has actually done it with Genetec can say so; one who has only read the spec will hedge.

Which ONVIF profiles, specifically?

Profile S covers streaming, Profile T adds advanced video including H.265, Profile G covers recording and retrieval. 'ONVIF compliant' without a profile is not an answer.

Does streaming to a third-party VMS affect warranty or support?

Get this in writing. Some vendors technically permit it while declining to support anything downstream of it, which is functionally a closed system.

Do your analytics still work if video is recorded elsewhere?

The one that catches people. Edge AI frequently depends on the vendor's cloud for model updates, alerting or search, even when the raw stream is portable. You may find the video is open and the intelligence is not.

Quantify the hedge. Take the fleet size you expect in three years, multiply by the unit cost, and treat that as the price of changing platforms if the hardware is not portable. Then ask how likely a platform change actually is for your organization — historically, honestly, not aspirationally.

If the answer is “we have run the same VMS for eight years and have no plans to change”, buy the closed platform that fits best and stop worrying about it. If the answer is “we have changed twice and are mid-consolidation after an acquisition”, the hedge is worth paying for. Both are defensible; guessing is not.