Video Management Systems: How to Select a Platform That Can Grow

When you need a VMS rather than a recorder

A standalone network video recorder works well for a single small site. A video management system (VMS) becomes the better choice when you have many cameras, several sites, multiple operators with different permissions, or integrations with access control, alarms and other systems.

Requirements that come from operators

• Number of cameras now and expected growth, and the number of sites.
• Who uses the system: security officers, managers, investigators, facility teams.
• Live monitoring needs: video walls, maps, alarm queues.
• Investigation needs: timeline search, motion search, metadata search and bookmarks.
• Evidence handling: export formats, watermarking or signatures, and audit trails.
• Integrations: access control, intercoms, alarm panels, licence plate recognition, point-of-sale.
• Clients: desktop, web and mobile access.
• Retention by camera and site.

Camera compatibility and open standards

ONVIF profiles standardize common functions: Profile S for streaming, Profile G for edge recording, Profile T for advanced streaming, Profile M for metadata and analytics, and Profiles A, C and D for access control. Check the conformant products list for your camera models, but remember that advanced features often rely on a vendor's native driver. Test the exact features you need, such as analytics events or two-way audio, with the models you own.

Architecture

• Deployment model: on-premises, cloud-managed or hybrid, where recording stays local and management or selected video moves to the cloud.
• Resilience: failover recording servers and a redundant management server for larger systems.
• Storage: live and archive tiers with retention controls per camera.
• Multi-site: central management and search across sites without backhauling every stream.
• Bandwidth: edge recording, lower-resolution streams over wide-area links and scheduled archiving.
• Scale limits: cameras per server, servers per site and sites per system.

Cybersecurity

• The vendor's vulnerability disclosure process and how quickly patches are released.
• Central management of camera firmware and passwords.
• Directory integration with MFA for operators and administrators.
• Granular roles, for example separating viewing, playback, export and configuration rights.
• Encryption between cameras, servers and clients, and for stored video where needed.
• Audit logs of who viewed, exported or changed what.
• Published hardening guidance, and support for running cameras on an isolated network.
• Any procurement restrictions on specific manufacturers that apply to your organization or its customers.

Privacy features

Privacy masking, retention controls per camera, restricted export rights and access logging all help an organization apply the Data Privacy Act's principles of proportionality and security to video. NPC Circular No. 2024-02 also sets requirements for CCTV notices, documented retention and responding to people who ask to view or obtain copies of footage, so check how easily a platform supports those tasks.

Licensing and total cost

• Licensing model: per camera, per server, per site or subscription.
• Features limited to higher editions.
• Software upgrade and support plans, and what happens if they lapse.
• Cloud storage or bandwidth fees for cloud-managed systems.
• Server hardware and storage for the full retention period.

A structured evaluation

1. Weight requirements with operators, IT and security.
2. Shortlist two or three platforms that meet the hard requirements.
3. Run a proof of concept with your cameras, including night scenes and busy areas.
4. Have real operators run through live monitoring, an investigation and an evidence export.
5. Test recording server failover and restore.
6. Check references from organizations of similar size.