What Avigilon's own documentation says its platform does not do, or only does under a stated condition, written for IT and security teams evaluating Alta and Unity. Every constraint below carries the documentation behind it, the operational impact, and the workaround.
Every constraint below comes from Avigilon's own current product pages and its Alta Video documentation, checked on August 17, 2026. Where Avigilon documents nothing, this page says so rather than guessing. Spot AI sells a competing platform, and two things need stating before any constraint is read. Avigilon also makes cameras that Spot AI runs on, so the subject here is the platform above them and nothing on this page treats an Avigilon camera as a weakness. And the claim that Avigilon locks you into its own hardware is wrong: its documentation names ONVIF and the Axis VAPIX protocol, with existing ONVIF, Avigilon, VAPIX and Vivotek cameras all listed as compatible.
Avigilon documents third-party support by standard, which settles the lock-in question. It documents the condition in the same place, and that condition is a purchase order rather than a setting.
A constraint list is only useful next to an honest account of the product.
SOC 2 Type II, ISO 27001 certification, NDAA compliance and a SAFETY Act designation all sit on Avigilon's own pages as stated properties of the platform. For a regulated buyer that removes weeks of questionnaire cycle from the front of an evaluation, and it is disclosure most of this category still treats as a document you have to ask for.
The Alta Video documentation states that the Alta solution is compatible with cameras that meet the ONVIF standards or that use the Axis VAPIX protocol, and that this provides compatibility with your existing ONVIF, Avigilon, VAPIX or Vivotek cameras. An IT team can check a real fleet against a real conformance profile rather than trust the phrase works with anything.
The Alta Horn Speaker is published for two-way audio and live talkdown, and the Arming Station Pro carries a keypad, card reader, camera, dual mics and a loudspeaker. Monitoring is offered both ways: Avigilon's own 24/7 service to validate and respond to events, or a customer's existing monitoring service through the API. A large part of this category stops at a notification.
Each one is a consequence of how the platform is designed rather than a defect. What matters is whether it collides with your starting point.
Avigilon's Alta Video documentation states plainly that you must connect third-party cameras to an Alta Cloud Connector. The condition holds whether the camera is added by IP address, by network discovery or by RTSP stream, and a dedicated documentation section exists for Cloud Connectors for Alta Video. The connector model line-up and the channel count each model carries are not published on the public site.
A 120-camera estate across six sites needs connector hardware at every site before a single detection lands, and the requirement recurs as sites are added. Because the channel capacity per model is not published, the sizing exercise cannot be done on paper the way it can where a vendor publishes camera maximums per appliance, so how many connectors a site needs is settled during the design rather than before it.
Ask for connector model, channel count and price as separate lines in the quote, sized against camera counts per site rather than the estate total, and phase the rollout so the hardware follows the sites. Where a site is being built new, Avigilon's own cameras skip the connector question entirely, which is the cheaper answer for greenfield.
Security AI Analytics, edge analytics for smarter detection and AI alerts are stated as platform capability. Whether a camera Avigilon did not build qualifies for all of them, some of them or none is not stated on the pages read. The documentation covers what the platform can do, not what a third-party camera then gets.
That is the difference between a compatibility list and a capability map, and it decides whether reuse is real. A camera can pass the ONVIF test, appear in the console and record cleanly while still sitting outside the analytics the project was justified on, and the models most likely to fail are the oldest ones.
Name the camera models you actually own and ask for written qualification per analytic before the connector order goes in. Run the proof of concept on the oldest camera in the fleet rather than the newest, because the newest one will pass either way and tells you nothing.
The analytics named on the site are License Plate Reader, Mailroom Management, Occupancy Management and Remote Video Monitoring, alongside edge analytics for detection and AI alerts for faster action. No safety or operations detection set appears on the published pages.
The buying committee usually contains more than security. If EHS wants personal protective equipment or forklift proximity on the same feeds, or operations wants dock dwell and standard-operating-procedure adherence, none of that is on the published list, so the same cameras end up carrying a second platform, a second contract and a second console.
Write the detections you need on one page before the first demo and mark which side of the security line each one sits on, then ask Avigilon which of them exist today and which are a partner integration. Where the safety half is real, price both platforms together rather than discovering the second one next year.
The Alta Horn Speaker is documented for two-way audio and live talkdown, and Alta Protect describes a monitoring service that validates and responds to events. Whether an analytic can trigger that speaker on its own, with nobody in the loop, does not appear on the pages read. The documentation covers the hardware and the service, not the unattended sequence between them.
Live talkdown implies somebody talking. For a yard at three in the morning, the difference between an operator-driven response and an autonomous one is the difference between a monitoring subscription per site and a setting, and it changes the running cost of the whole estate rather than the price of the speaker.
Ask for the unattended sequence to be demonstrated rather than described, on a site with nobody watching. If a human is in the loop by design, price Avigilon's own 24/7 monitoring service, or your existing central station through the API, in the same quote as the hardware.
Avigilon publishes Alta Cloud Security and Unity On-prem Security as separate solutions with separate deployment models, each spanning video, access control and sensors. The Alta Cloud Connector requirement, and the Alta Video documentation it lives in, belong to the cloud line.
A multi-site estate has to pick the line before it can compare features, and a capability documented for one is not evidence of it in the other. That is genuine architectural flexibility and it also doubles the evaluation: a data-residency obligation at one plant and a thin uplink at another can push two sites onto different lines inside the same vendor relationship.
Settle the line first on the three questions that actually decide it, which are residency, uplink and whether there is a server room, then compare features only within that line. Ask for the feature matrix per line in writing, and confirm which of the four named analytics exist on the line you have chosen.
The same five constraints in one view, sized to paste into an evaluation document.
Swipe the table sideways to see every column.
Avigilon data comes from its own product pages and Alta Video documentation, checked on August 17, 2026. Gaps are marked as not publicly specified.
If video, access control and sensors are being bought together, and a security review is going to ask for SOC 2 Type II, ISO 27001, NDAA and a SAFETY Act designation, Avigilon answers all of that in public before the first call. Specifying a site from scratch removes the connector question entirely, and the choice between the Alta cloud line and the Unity on-premises line means a plant with a residency obligation stays inside one vendor relationship. You are buying a security estate on purpose.
Spot AI comes at the same estate from the software side, which is why its constraint list looks different. It is camera agnostic: any ONVIF or RTSP IP camera works at full functionality with no prerequisite appliance in front of it to earn that, and legacy analog comes in through the Intelligent Video Recorder, so a mixed fleet does not split into a supported half and a conditional half. Avigilon cameras are supported hardware on this side too, which is worth saying plainly, because the choice here is about the platform rather than about what is on the wall.
The detections ship with the platform rather than around it. 15+ pre-trained Video AI Agents span security, safety and operations, covering after-hours intrusion, vehicle break-in, personal protective equipment, forklift near-miss, falls and hazard-zone crowding, and Iris builds a detection that is not on the list in natural conversation. Deterrence runs autonomously through talk down, strobes and horns on standard speakers already installed, and full-resolution video stays on the IVR in the building with only event metadata crossing the network.
The useful question is not which platform has fewer constraints, but how much hardware sits between the contract and the first useful detection.
None of that makes Spot AI the right answer for every buyer. Avigilon publishes SOC 2 Type II, ISO 27001, NDAA compliance and a SAFETY Act designation on its own site, which is a fuller certification page than Spot AI maintains, and it sells access control, intercoms, credentials, wireless locks and smart sensors as products where Spot AI reaches those through integrations. Its 24/7 monitoring service is something Spot AI does not offer, and its Unity line gives a fully on-premises option Spot AI does not match. A constraint list earns its keep by lining each platform's shape up against your starting point.
A live pilot on your cameras answers in a week what a spec sheet cannot.
Customer-reported outcomes from named Spot AI customers.
Staccato went from first conversation to full deployment across an 800-acre campus in seven weeks, on the camera infrastructure it already had.
All Star Elite brought cash shrink down from about 6% to 1% across its store estate, and cut investigation time by more than half.
Storage Asset Management was alerted to a break-in around one in the morning, and law enforcement arrived while the incident was still in progress.
"With Spot AI, these facilities are more secure and better watched than the ones we staff traditionally, where we pay for a full-time person on-site."
Five, all documented: third-party cameras must connect to an Alta Cloud Connector, which is hardware at every site; which analytics reach a reused camera is not publicly specified; the named detections are License Plate Reader, Mailroom Management, Occupancy Management and Remote Video Monitoring, with no safety or operations set; whether an analytic can fire the Alta Horn Speaker without an operator is not publicly specified; and Alta and Unity are separate lines that have to be chosen between before features can be compared.
Yes, and the correction is worth making plainly: Avigilon is not proprietary-cameras-only. Its documentation states that the Alta solution is compatible with cameras that meet the ONVIF standards or that use the Axis VAPIX protocol, naming existing ONVIF, Avigilon, VAPIX and Vivotek cameras. The condition published alongside it is that you must connect third-party cameras to an Alta Cloud Connector, whether they are added by IP address, by network discovery or by RTSP stream.
It is the on-site appliance Avigilon's documentation states third-party cameras must connect to in order to reach Alta Video. It matters because it turns camera reuse into a hardware purchase per site rather than a software setting, and because connector models and channel counts are not published, so the sizing exercise cannot be done before a quote. Ask for it as a separate line, sized on cameras per site.
Avigilon publishes SOC 2 Type II, ISO 27001 certification, NDAA compliance and a SAFETY Act designation on its own site, which is more than most of this category discloses in public. A security review should still request the current SOC 2 report and the ISO certificate rather than working from the website, and should confirm which of the two product lines, Alta or Unity, each certification statement covers.
It depends on whether the connector is the constraint. If the estate is already mounted and the goal is full AI on all of it without adding an appliance per site, a camera-agnostic platform such as Spot AI fits: any ONVIF or RTSP camera connects as it is, legacy analog comes in through the Intelligent Video Recorder, and 15+ pre-trained Video AI Agents run across the fleet. If the estate is being bought whole and compliance disclosure matters most, Avigilon is hard to fault.