On-premise AI-powered video security with locally hosted recording, analytics and cloud-managed capabilities.
Product and system guidance
Avigilon Unity Video combines VMS, camera/encoder support, search, alerting and analytics with Unity Access and cloud services where selected. Camera families differ in sensor, lens, low light, analytics, multisensor/fisheye/PTZ and environmental design. Size servers, appliances and retention from measured streams.
- Unity Video software editions and operator clients
- H5/H6 camera, multisensor, fisheye and PTZ choices
- Appearance search, object classification and event rules
- NVR/storage, redundancy and cloud service management
- Scene survey, pixels on target, lens and mounting
- Bandwidth, storage, retention and evidence export
- Firmware, cybersecurity, user roles and remote access
- Current regulatory, procurement and customer compliance requirements
Engineering before procurement
Boston High Tech validates current model availability, firmware, licenses, analytics, VMS compatibility and storage calculations. We do not publish private certificate numbers or named certificate-holder records; qualifications can be confirmed through appropriate private channels.
Request a video-system design review
Serving projects from our Charlotte headquarters and local client offices in Massachusetts, New York and New Jersey. Office visits are arranged in advance.
Official manufacturer references
How to compare and specify this product family
For Avigilon Unity Video, Cameras and Analytics, the right model and architecture depend on the site, existing infrastructure and operating policy. A proposal should clearly document the following video-surveillance system decisions before equipment is ordered:
- Scene purpose and required pixels on target
- Lens, mounting height, WDR, IR and low-light needs
- Analytics supported by the selected camera and VMS
- Bandwidth, PoE and network segmentation
- Retention, storage throughput and export workflow
- User roles, cybersecurity, health monitoring and support
Installation, testing and handoff
Design starts with the evidence or operational result required at each scene—not megapixels alone. We document fields of view, identification targets, lighting, camera placement, network load, recording profiles and retention assumptions. Commissioning covers focus, exposure, time synchronization, analytics calibration, user permissions, mobile or remote access, export testing and health alerts. Final documentation records device names, locations, addressing, retention settings and administrator procedures without publishing private credentials.
Frequently asked questions
Questions about Unity Video camera choices, which analytics you can rely on, and where recording and administration actually live.
When is a multisensor the better answer than a PTZ?
When several fixed views are needed from one mounting point at the same time. A PTZ covers a wide area with one movable view, so it records only where it is pointed at that moment. H5/H6 camera, multisensor, fisheye and PTZ choices are made scene by scene, since camera families also differ in sensor, lens, low light, analytics and environmental design.
How do we know which analytics will actually run on the cameras we buy?
By checking analytics supported by the selected camera and VMS before the order, because camera families differ in sensor, lens, low light and analytics. Appearance search, object classification and event rules are the capabilities on the software side, and each one is checked against the specific camera model picked for that scene, not against the family name.
How do you size the recorder and the retention period?
From measured streams. Servers, appliances and retention are sized from what the cameras actually produce at their configured resolution, frame rate and recording mode, rather than from a camera count. NVR/storage, redundancy and cloud service management are decided in the same pass, along with how evidence gets exported when somebody asks for a clip.
How do we know a camera will give us a usable image of a face?
By starting from the result required at that scene rather than from megapixels. Scene purpose and required pixels on target is set first, then lens, mounting height, WDR, IR and low-light needs follow from the actual lighting and distance. Fields of view and identification targets are documented per camera so the design can be reviewed before anything is mounted.
Is this a cloud system or does it stay in our building?
Recording stays in the building. This is on-premise video security with locally hosted recording and analytics, plus cloud-managed capabilities where those are selected. Cloud or on-premise administration and ownership is still a decision to write down, because it determines who holds the accounts, who can reach the system remotely, and what happens to that access when staff change.
How does Unity Access fit alongside Unity Video?
Avigilon presents the two together: Unity Video combines VMS, camera/encoder support, search, alerting and analytics with Unity Access and cloud services where selected. What that pairing covers at a given site is confirmed against current model availability, firmware, licenses, analytics and VMS compatibility, because availability, licensing and integrations change. Who may see what across the two belongs with the firmware, cybersecurity, user roles and remote access decisions.
Avigilon Alta and Unity owner and buyer resources
Discuss Avigilon installation, maintenance or service
Detailed guides are maintained by 360TechnologyGroup.com, the parent-company knowledge center.
Official Avigilon Unity and Alta Video software, firmware and support
Official manufacturer resources. We link out rather than host firmware.
Before updating: confirm model, hardware revision, current version, entitlement and rollback plan, and schedule monitored or life-safety-adjacent systems with the administrator.