Review

Traditional VMS review 2026: scored against its own documentation

A structured review of the on-premises video management system category for IT, security and facilities teams running their own recording servers: what it does well, where the constraints sit and who should look elsewhere. This page is about a category rather than a company, so every line describes traits common to on-premises VMS products.

Updated August 24, 2026
10 min read
By Joshua Foster, IT Systems Engineer
Traditional VMS review: A structured review of the on-premises video management system category for IT, security and facilities teams running their own recording servers: what it does well
3.2
out of 5
The verdict in 30 seconds

A traditional video management system is the most dependable thing in this whole comparison at the job it was designed for. It records every camera to storage in the building on infrastructure you own, holds retention for as long as the policy says, and does it with no cloud dependency at all. The category's other quiet strength is device support, and two products on this hub show the scale: Milestone lists more than 16,500 devices on its Supported Device List for XProtect, and Genetec publishes its own, with analog reachable through encoders and licensing usually per channel. It scores lowest on what the recording is for, because analytics are typically separate modules or partner add-ons rather than detections that ship, and because response at the moment of an incident depends on somebody being in front of a monitor. Choose a traditional VMS when dependable recording under your own control is the requirement. Look elsewhere when the footage has to raise the events worth seeing rather than wait to be searched.

Recording reliability and retention control
4.5
The category's core job: every camera recorded locally, retention sized to the policy, on storage the organisation owns and can audit.
Published device support
4.0
Milestone publishes more than 16,500 devices on its Supported Device List for XProtect, and Genetec publishes a supported device list of its own for Security Center.
Data residency and cloud independence
4.0
None by design: the system runs on infrastructure you own, which is why estates with a data-residency obligation chose it in the first place.
Shipped AI detections
2.0
Recording, retention and playback. Motion alerting is standard and deeper analytics are typically separate modules or partner add-ons rather than shipped detections.
Response at the moment of an incident
1.5
Not part of the category. The documented response is a person watching a monitor or reading a motion alert.
How this was scored

Five criteria, each scored against what on-premises video management products commonly document, reviewed on August 24, 2026. Traditional VMS is a category rather than a company, so there is no single vendor's documentation behind these scores: where a line rests on a published document it names one, such as Milestone's Supported Device List for XProtect or Genetec's supported device list for Security Center. Spot AI competes with products in this category, so no score here rests on an anonymous source, an aggregated user rating or a private benchmark. Check each line against your own product's release notes and licence terms before you plan around it. This is not a paid placement.

The on-premises pattern, and the point where it stops

Every box here describes traits common to on-premises video management products rather than one vendor's documentation. Capture and retention are the category's strength. What happens after capture is where the gap sits.

How a frame is captured and kept
Cameras
A long supported list
Milestone lists more than 16,500 devices for XProtect; Genetec publishes its own list, usually licensed per channel
Analog channels
Through encoders
Older runs stay in service on a hybrid recorder rather than being recabled
Recording server
Local storage, per building
Sized to the retention policy, on infrastructure the organisation owns and refreshes
What happens next, and what the category leaves out
The client
Scrub, review, export
Answers what happened once somebody knows where to look and has time to look
Analytics
Separate modules
Typically add-ons or partner products with their own licensing and their own server
On site at 03:00
A motion alert on a monitor
Response depends on somebody being there to read it; on-site deterrence is not part of the category
This diagram describes the pattern common to on-premises video management products rather than any one vendor's documentation, as reviewed on August 24, 2026. Check your own product's release notes and licence terms before planning around any line of it.

What Traditional VMS is, and who it is built for

A traditional video management system is a recorder with a client on top. Cameras stream to recording servers or an NVR in each building, video is written to local storage sized to the retention policy, and an operator opens a client application to play it back, scrub a timeline and export a clip. Licensing is usually per channel, analog reaches the system through encoders or a hybrid recorder, and administration happens per site.

That architecture is not a compromise. It is the reason a large share of hospitals, schools, utilities and manufacturers chose it: video never leaves the building, storage is auditable, the estate keeps working when the internet does not, and an internal team can inspect the whole system without a vendor in the room. An evaluation that treats on-premises recording as a legacy default has misread why it is there.

The category's other genuine strength is breadth of hardware support, and the documents are public. Milestone publishes a Supported Device List for XProtect carrying more than 16,500 devices, updated as new devices and firmware versions are evaluated, and Genetec publishes a supported device list for Security Center, so procurement can check a real inventory against a real document before anything is bought. What these products generally do not ship is a set of named detections: analytics arrive as separate modules or partner add-ons, priced and deployed on their own, and on-site deterrence is not part of the category at all.

  • Recording servers or an NVR in each building, writing full-resolution video to storage the organisation owns.
  • Retention sized to the policy rather than to a plan tier, with capacity a purchasing decision rather than a subscription line.
  • Supported device lists published per product, such as Milestone's 16,500-plus for XProtect, so a fleet can be checked model by model.
  • Analog channels reachable through encoders or a hybrid recorder, so older runs stay in service.
  • No cloud dependency by design: the system runs, records and plays back on infrastructure you control.
Key takeaway

A traditional VMS is strongest at capturing and keeping video under your own control, and thinnest at telling anybody which of that video was worth watching.

Traditional VMS pros and cons

Both columns are documented. Nothing here comes from an anonymous review.

What Traditional VMS does well
It does the fundamental job better than anything else on a shortlist, and the fundamental job is not glamorous: capture every camera, every hour, and still have the footage weeks later when somebody finally asks. Recording servers write full-resolution video to local storage sized to the retention policy, capacity is a purchasing decision rather than a plan tier, and no window expires because a subscription changed. Estates burned by retention shrinking under them defend this architecture hardest.
Device support is the category's quiet superpower and the documents are public. Milestone's Supported Device List for XProtect carries more than 16,500 devices and is updated as new devices and firmware versions are evaluated; Genetec maintains its own for Security Center. On a fleet assembled over ten years from four vendors, that list is the single most useful artifact in the whole evaluation, and it belongs in the evaluation before any demo.
Data residency is answered by the architecture rather than by a contract clause. The system runs on infrastructure you own, video never has to leave the building and an internal security team can audit the storage, the access log and the network path without a vendor in the room. For a hospital, a school district, a utility or a defence supplier, that is often not a preference but a condition of purchase.
It keeps working when the connection does not. A recording server on the local network does not care about an outage at the carrier, so a site with a poor uplink loses nothing at all and playback on site is unaffected. A cloud-managed or hybrid architecture has a degraded mode under those conditions; this one does not have the failure mode at all.
Analog is a solved problem rather than a migration. Older channels reach the system through encoders or a hybrid recorder, which means the half of an estate that nobody has recabled stays in service and keeps recording alongside the newer IP cameras. That is the practical reason many of these systems have been running for a decade without a rip and replace.
The commercial model is capital rather than recurring, and for some organisations that is the right shape. Perpetual licences per channel plus servers and storage sit in a capital budget with a known refresh cycle, and an integrator relationship carries the deployment and the support, which is a named accountable party at 03:00.
What to check before you buy
The system waits to be asked. It answers what happened once somebody knows roughly where to look and has time to scrub, which is why investigations in these estates are routinely measured in hours rather than minutes.
Analytics are typically a separate purchase. Motion alerting is standard across the category and deeper detection generally arrives as an add-on module or a partner product with its own licensing, its own server requirement and its own integration project, so the shipped feature set is recording, retention and playback.
Response at the moment of an incident is not part of the category. The documented answer is a person watching a monitor or reading a motion alert, so what happens on site at 03:00 depends on somebody being there to read it and to decide what to do next.
Administration does not scale by itself. One building with one recording server is manageable; twenty buildings means twenty upgrade windows, twenty storage calculations and a user list per site, and multi-site views depend on what the specific product supports.
The cost is real and it is periodic. Recording servers reach end of support and need a capital refresh, storage grows with resolution and retention, and per-channel licences plus annual maintenance renew on a date somebody in finance already has. A year-one comparison flatters this architecture and a five-year one does not.
Because this is a category rather than a company, every line above has to be checked against your own product. Release notes, licence terms and the supported hardware list for your specific version are the documents that decide what is actually true on your estate, and they vary more between products than the category description suggests.

Spot AI vs Traditional VMS on the criteria buyers actually weigh

The Spot AI column describes documented behavior. The category column describes traits common to on-premises VMS products rather than any single vendor's documentation, so check it against the product you actually run.

Criterion
Spot AI
Traditional VMS
Platform model
Agent-first video AI, hybrid edge to cloud
On-premises video management on servers or an NVR in each building. This column describes traits common to on-premises VMS products rather than any single vendor's documentation
Works with existing cameras
YesAny ONVIF or RTSP IP camera, plus legacy analog through the IVR
YesThe category's real strength: an established VMS reads a long list of IP cameras, usually licensed per channel, with analog reachable through encoders
Runs with no cloud connection at all
HybridFull-resolution video stays on the Intelligent Video Recorder in the building; event metadata goes to the cloud
YesRecording, playback and administration all run on the local network, so a site with no uplink loses nothing
Where full-resolution video lives
On site on the Intelligent Video Recorder; only event metadata leaves the building
On recording servers or an NVR in each building, sized to the retention the policy asks for and on storage the organisation owns
Pre-trained agents
15+Vehicle break-in, fire, intrusion, PPE, forklift near-miss, falls, hazard-zone crowding
ModulesAnalytics are typically separate modules or partner add-ons rather than detections shipped with the recorder
Active deterrence hardware
AI Talk Down, strobes and horns through standard speakers on existing cameras
Not part of the category. The documented response is a person watching a monitor or reading a motion alert

Swipe the table sideways to see every column.

The category column summarises traits common to on-premises video management products, reviewed on August 24, 2026, rather than one vendor's public documentation. Where a line rests on a named document, the document is named.

Who should choose Traditional VMS, and who should look elsewhere

The honest split, stated the way a shortlist call would state it.

Choose Traditional VMS
Dependable recording under your own control

If the requirement is that every camera records reliably, that retention meets a policy somebody will audit and that video never leaves the building, this category answers it and has answered it for years. Estates with a data-residency condition, a poor uplink or an internal team that wants to inspect the storage themselves have a genuinely strong reason to stay exactly where they are.

Look elsewhere
Footage that has to raise what matters by itself

If the problem is that nobody has time to watch, that investigations take half a day each or that safety and operations now want answers from the same cameras, the recorder is not the constraint and buying a newer one will not move it. That is a case for detections that ship with the platform and a search that starts from a sentence rather than a timestamp.

The Spot AI alternative
AI coworkers across security, safety and operations

Spot AI ships 15+ pre-trained Video AI Agents spanning vehicle break-in, fire, intrusion, personal protective equipment, forklift near-miss, falls and hazard-zone crowding, so a mixed estate gets shipped coverage on both sides. Iris builds anything else in natural conversation in about eight minutes, full-resolution video stays on the Intelligent Video Recorder in the building and the platform is SOC 2 Type II, NDAA-compliant and HIPAA-aligned.

If you are comparing the two directly

The two are less opposed than a shortlist makes them look. Spot AI keeps the same on-site recording model, with full-resolution video on the Intelligent Video Recorder and only event metadata leaving the building, so the data-residency argument that anchors a traditional VMS survives intact. What changes is what the footage is asked to do: pre-trained agents watching the same feeds, plain-English search over the archive, and something that fires on site rather than waiting for a person to read an alert.

The cheapest way to settle it is a site running both at once for a fortnight. The existing servers keep recording throughout, so nothing is at risk and the comparison happens on identical footage. Pick the site with the messiest camera mix rather than the newest, because a fleet assembled over ten years is the real test.

Key takeaway

Model three years both ways against the same camera count and the same retention obligation, and put the server refresh and storage growth in the on-premises column explicitly. A perpetual licence looks cheapest right up until the hardware cycle lands.

Test it on your own cameras

See what the AI catches on your live feeds before any platform decision.

Request a demo

Proof points from Spot AI customers

Customer-reported outcomes from named Spot AI customers.

5 min

Liberty-Perry School District resolves an incident in about five minutes, after evaluating ten systems before choosing Spot AI.

Liberty-Perry School District, education
30 sec

Cambridge City cut footage search from two hours to 30 seconds after consolidating seven municipal locations on one platform.

Cambridge City, municipal government
22

Silver Bay Seafoods replaced fragmented legacy camera systems across 22 locations, including remote Alaska facilities, and lifted operational efficiency 15%.

Silver Bay Seafoods, seafood processing

"The biggest benefit of Spot AI is how easy it is to look up incidents, see the footage, and then share it and collaborate."

Ben Grady
Manager of IT and Database Administration, Nashville Rescue Mission

Frequently asked questions

Is a traditional VMS still a good choice in 2026?

Yes, for the job it was designed for. The category scores 3.2 out of 5 here, carried by dependable local recording, retention control on storage you own, supported device lists in the thousands and no cloud dependency at all. It fits an estate whose requirement is reliable capture under its own control. Teams whose problem is that nobody has time to watch the footage should look at what ships with the platform rather than at the recorder.

Does a traditional VMS work with existing cameras?

Yes, and it is the category's strongest suit. Milestone publishes more than 16,500 devices on its Supported Device List for XProtect and Genetec publishes a supported device list for Security Center, licensing is usually per channel, and analog channels reach the system through encoders or a hybrid recorder. Check your own product's list for your specific version rather than the category description, because breadth varies between products more than the summary suggests.

What analytics come with a traditional VMS?

Motion alerting is standard across the category, and anything deeper is typically a separate module or a partner add-on with its own licensing, its own server requirement and its own integration project. Some products publish a license plate recognition module of their own. What the category does not generally do is ship a set of named detections with the recorder, and on-site deterrence is not part of it at all.

What does a traditional VMS cost?

The shape is consistent: perpetual licences per channel plus recording servers, storage and an annual maintenance agreement, with a capital refresh when the servers reach end of support. Model three to five years rather than one, because the maintenance renewal and the hardware cycle are what actually move the number, and both land outside the licence line.

What is the best alternative to a traditional VMS in 2026?

It depends on which part is failing. If retention and residency are working and only the searching is painful, an alternative has to keep video in the building to be a real replacement. A camera-agnostic platform such as Spot AI does that: full-resolution video on the Intelligent Video Recorder on site, any ONVIF or RTSP camera connecting as it is, analog through the recorder, and 15+ pre-trained Video AI Agents across security, safety and operations. The alternatives roundup compares five platforms side by side.