Professional & Enterprise
The same core video and security foundations. Different ways to run your operation.
Professional
One independent site, one active logical recorder and local control.
Explore ProfessionalCompare the operating scope
| Capability | Professional | Enterprise |
|---|---|---|
| Daily video operations | ||
| Live camera wall and layouts | Included | Included |
| Continuous and scheduled recording | Included | Included |
| Local playback and evidence export | Included | Included |
| Retention, evidence holds and storage checks | Included | Included |
| Named users, camera permissions and audit | Included | Included |
| Camera reconnect, diagnostics and recovery tools | Included | Included |
| Deployment and oversight | ||
| Operating model | One independently managed site | Single-site or distributed operations |
| Active recording topology | One active logical recorder | Multiple managed recorders |
| Central federation of independent sites | Not included | Included with licensed participating sites |
| Cross-site health, events and archive access | Local site only | Within source-site grants and permissions |
| Recording during a WAN interruption | Local operation with a valid licence | Local operation with a valid licence |
| Growth and resilience | ||
| Recording copies | Not included | Available within the designed storage topology |
| Recorder takeover and management HA | Not included | Project-specific infrastructure and validation |
| Camera-channel licensing | Purchased site allocation | Purchased allocation at each site |
| Operator access | Named users and permissions | Named users and permissions |
| Upgrade path | Edition change through licensing | Same core codebase and installer |
| AI analytics | Separately scoped integration | Separately scoped integration |
Channel allocations, retention and performance are sized for the deployment. Enterprise resilience requires the appropriate infrastructure and commissioning; it is not automatic failover on every Windows PC. Hardware and third-party integrations are scoped separately.
Edition questions
Make the choice around your operation.
Is Professional limited to fewer than 100 cameras?
There is no fixed 99-camera edition limit. Professional is defined by one independently managed site and one active logical recorder. The purchased channel allocation and the hardware workload determine the deployment size. Enterprise is the choice when multiple recorders, federation or a resilience architecture are needed, even at a smaller site.
Can we keep our existing cameras or NVR?
Compatible cameras and NVR channels can be connected through ONVIF discovery and profiles, or through a supported RTSP stream. ONVIF handles discovery and device functions; the video may still travel over RTSP. We assess the exact camera or NVR model, firmware, credentials and required functions before confirming compatibility.
Do AI analytics come with either VMS edition?
VMS licensing covers the agreed video-management scope. KVABI visual-intelligence applications are separately scoped and licensed, with compatibility, scene suitability and integration agreed for the project. They are not automatically bundled with a Professional or Enterprise licence.
How does Enterprise federation work?
Participating sites retain their own VMS authority, recording and local permissions. An Enterprise central installation accesses only the information granted by each licensed source site over reachable HTTPS. Remote access depends on connectivity; a WAN interruption does not itself stop valid local recording.
Can Professional be upgraded to Enterprise?
Both editions use the same core codebase and installer. An edition licence change enables the additional rights after the deployment topology is checked. Additional recorders, federation and resilience infrastructure are configured as part of the upgrade project.
What do you need to size a deployment?
Share the number of sites and cameras, camera resolution and codecs, recording bitrate, retention days, concurrent live views and recovery objectives. The proposed recorder, storage and workstation configuration is then validated against that workload.