What Eagle Eye Networks' own documentation says its cloud video management system does not do, or only does under stated conditions, written for IT and security teams consolidating a mixed camera fleet. Every constraint below carries the documentation behind it, the operational impact, and the workaround.
Every constraint below comes from Eagle Eye Networks' own current product, hardware and camera compatibility pages, checked on August 17, 2026. Where Eagle Eye documents nothing, this page says so rather than guessing. Spot AI sells a competing platform, and three claims that circulate about Eagle Eye are corrected here rather than repeated: camera compatibility is not a weakness, deterrence is documented on the platform in the form of sirens and talk-down alerts, and its detections are not security-only, because its own site now names verification of personal protective equipment with AI-driven alerts for safety incidents, alongside environmental sensors for leaks, extreme temperatures and air quality.
Eagle Eye publishes an unusually complete route from an old camera to a cloud console. Each leg of that route carries a condition, and the conditions are what decide whether reuse is real on an estate assembled over a decade.
A constraint list is only useful next to an honest account of the product.
Eagle Eye publishes that it works with more than 7,500 cameras with no need to rip and replace, and that it captures video and extracts AI-driven analytics from virtually any ONVIF-conformant camera. The mechanism is named too, ONVIF Profile S with H.264 and MJPEG dual stream, and analog-ready Bridges digitize the video coming from analog cameras, so the older half of an estate is a documented route rather than a replacement project.
Eagle Eye documents deterring crime with sirens and talk-down alerts as a capability of the system itself. A large part of this category stops at a notification and leaves the response to whoever happens to read it, so this is a real point in Eagle Eye's favour and it is the reason a straight cloud-versus-edge argument understates the product.
If a model is not published as supported, Eagle Eye's own route is to connect it to a Bridge or a CMVR and request support from the dashboard. A vendor that documents what happens when its own compatibility list runs out is a vendor whose list can be taken at face value, and the CMVR line records locally on site across roughly 1 TB to 192 TB for the sites that need it.
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.
Eagle Eye states that it stores video data on its own data centers, and that all video is fully encrypted both in transmission and at rest. That is the architecture written down plainly rather than hedged, and it is what makes the cloud console possible.
Every site brings its uplink and its data-residency position into the project. A plant running 60 cameras on a shared line is a bandwidth exercise before it is a license decision, and a works council asking where footage is held gets an answer set by the platform rather than by the customer.
Eagle Eye publishes its own answer twice over: it states the platform works with any bandwidth, and the CMVR line records locally on site from about 1 TB to 192 TB, which the documentation describes as addressing bandwidth challenges and redundant storage needs. Put a CMVR where the uplink is thin, and settle residency in writing before the pilot rather than at contract review.
Cameras reach the platform through an Eagle Eye Bridge or a CMVR on site, and the analog-ready models digitize the video coming from analog cameras. The appliance is the documented route rather than an optional accessory, and the CMVR line spans roughly 6 to 165 cameras and about 1 TB to 192 TB.
On a twelve-site estate that is twelve appliances and twelve sizing exercises before a single detection lands, and it recurs as sites are added. It is also the part of a multi-site rollout that absorbs budget a per-camera software estimate never showed, because the software number scales with cameras and this one scales with locations.
Size by site against camera count and retention rather than against the estate total, and phase the rollout so the hardware follows the sites. The analog-ready models earn their place by keeping a coax run alive rather than replacing it, so count how many sites that saves before comparing totals with anything else on the shortlist.
Two lines sit on the camera compatibility page in Eagle Eye's own words: additional configuration in the camera web page may be needed, and the firmware listed for each model is the minimum supported version. The platform communicates with cameras over ONVIF Profile S using H.264 and MJPEG dual stream.
On a fleet nobody has touched in five years, the second line is the one that turns into unplanned work. Firmware upgrades across a few hundred cameras mean finding admin credentials that may be lost, scheduling reboots on a live estate, and discovering which models will not take the upgrade at all, none of which appears in a per-camera license estimate.
Run the fleet against the compatibility list before the project starts and record model, current firmware and credentials in the same sheet, then budget a firmware pass as its own line with its own window. Where credentials are gone on a batch of cameras, that batch is a replacement decision, and it is cheaper to know that in the survey than in week three.
Gun Detection, License Plate Recognition, Face Match and Precision Person and Vehicle Detection are named as platform capability, alongside personal protective equipment verification and a Point of Sale Integration. Whether every connected camera qualifies for them, and what a camera needs in order to qualify, is not stated on the pages read.
More than 7,500 supported models is a compatibility answer, not a capability answer, and a buyer who reads one as the other will pick wrong. A camera can connect cleanly, record properly and still sit outside the detection the project was justified on, and the cameras most likely to do so are the oldest ones.
Name the five camera models you actually own and ask for written qualification per detection before the appliance order goes in. Run the proof of concept on the oldest camera in the fleet rather than the newest, because the newest passes either way and tells you nothing about the estate.
Deterring crime with sirens and talk-down alerts is published as platform capability. Which speaker or siren the platform drives, whether it has to be Eagle Eye hardware, and whether a detection can fire it with nobody watching are not stated on the pages read. The documentation covers that the capability exists, not what it runs through.
That decides the cost of deterrence across an estate rather than at one site. If the audio device is vendor-specific, every deterrence point becomes a hardware line on top of cameras and appliances; if the sequence needs an operator, it becomes a monitoring subscription instead. Neither is unreasonable, and both change the model materially.
Ask which device the sirens and talk-down run through, whether it is Eagle Eye hardware, and whether a detection triggers it autonomously, then price the answer per deterrence point rather than per site. Where a public address system or standard speakers already exist, ask each platform on the shortlist which of them drives those directly.
The same five constraints in one view, sized to paste into an evaluation document.
Swipe the table sideways to see every column.
Eagle Eye Networks data comes from its own product, hardware and camera compatibility pages, checked on August 17, 2026. Gaps are marked as not publicly specified.
If the fleet is a decade of different manufacturers, part of it still analog, and the goal is one cloud console over all of it without replacing hardware, Eagle Eye was built for that job and documents it better than most of the field. The published model list and the analog-ready Bridges make it one of the easier platforms to scope honestly against a real site survey, and deterrence being on the platform rather than with a partner removes an evaluation most buyers do not know is coming.
Spot AI answers the same brief with the opposite architecture, which is why the constraint list looks different rather than shorter. Full-resolution video stays on the Intelligent Video Recorder in the building and only event metadata crosses the network, so the uplink calculation largely disappears, the residency conversation is short, and retention is a property of hardware inside your own perimeter rather than a subscription tier.
The camera side stays open in the same way, with any ONVIF or RTSP IP camera at full functionality and legacy analog coming in through the IVR. What differs is the detection set and the response: 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, with Iris for anything not on the list, and deterrence runs through talk down, strobes and horns on standard speakers already installed rather than on a device specified per point.
The useful question is not which platform has fewer constraints, but whether your uplink, your firmware and your oldest cameras can live with the ones it has.
None of that makes Spot AI the right answer for every buyer. Eagle Eye publishes a supported model list running past 7,500 cameras where Spot AI states compatibility by protocol, and its CMVR line comes with published capacities from about 1 TB to 192 TB where Spot AI does not publish IVR capacities that way. Its Video API Platform and certified reseller program are published products, and a site with no appetite for hardware on site can run camera to cloud in a way an edge-first design cannot. 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.
Silver Bay Seafoods replaced fragmented legacy camera systems across 22 locations, including remote Alaska facilities, and lifted operational efficiency 15%.
The YMCA of Greater Richmond deployed 17 locations in two weeks and standardized retention across the estate.
Don Franklin Family of Dealerships had incident footage on responding officers' phones within four minutes of an alarm, and reported five recoveries within the hour.
"Within four minutes of the alarm going off, Spot AI gave us video footage of the incident on the responding officers' phones. We had five recoveries within the hour."
Five, all documented: video is stored in Eagle Eye's own data centers, so bandwidth and residency come into every site; an Eagle Eye Bridge or CMVR is required at each location; the compatibility page states that additional camera-side configuration may be needed and that listed firmware is a minimum version; which detections run on which connected camera is not publicly specified; and the hardware behind the published sirens and talk-down alerts is not publicly specified.
Yes, and more specifically than most. Eagle Eye states it works with more than 7,500 cameras with no need to rip and replace, that the Cloud VMS uses ONVIF Profile S with H.264 and MJPEG dual stream, and that analog-ready Bridges digitize the video coming from analog cameras. For a camera not on the list, the documented route is to connect it to a Bridge or CMVR and request support from the dashboard.
Partly, and this corrects a claim that circulates about the platform. Its own site names verification of proper use of personal protective equipment with AI-driven alerts for safety incidents, and environmental sensors for dangerous leaks, extreme temperatures and air-quality issues, alongside Gun Detection, License Plate Recognition, Face Match and Precision Person and Vehicle Detection. What is not publicly specified is which of those run on which connected camera.
Eagle Eye states it stores video data on its own data centers, with all video fully encrypted in transmission and at rest. Video can also be held locally: the CMVR line records on site and spans roughly 6 to 165 cameras and about 1 TB to 192 TB, which the documentation describes as addressing bandwidth challenges and redundant storage needs. Retention periods and storage tiers are agreed with Eagle Eye or a certified reseller.
An edge-first platform, because a cloud video management system has to move the video to make it useful. Spot AI keeps full-resolution video on the Intelligent Video Recorder in the building and sends only event metadata across the network, works with any ONVIF or RTSP IP camera and legacy analog through the IVR, and runs 15+ pre-trained Video AI Agents across the fleet. If bandwidth and residency are not the constraint, Eagle Eye is hard to fault on compatibility.