What Arcules' own documentation says the platform does not do, or only does under conditions, written for IT and security teams moving a multi-site camera estate to the cloud. Every constraint below carries the documentation behind it, the operational impact, and the workaround.
Every constraint below comes from Milestone Systems' Arcules product pages, the Arcules knowledge base and Milestone's Arcules documentation, read on August 14, 2026. Those product pages are client rendered, so they were read in a browser rather than fetched, which is how a vendor profile ends up thin for no good reason. Where Arcules documents nothing, this page says so rather than guessing. Spot AI sells a competing platform, and two claims that circulate about Arcules are corrected here: it is not end of life, because the 2026 release cycle alongside XProtect 2026 R1 extended camera-to-cloud coverage and added long-term video storage, and it is not tied to particular camera brands, because ONVIF conformance is the published requirement.
Arcules publishes three ways a camera reaches the platform, and they are not interchangeable. Which one a site qualifies for is set by the cameras on its walls, and it changes what the site pays and what it uploads.
A constraint list is only useful next to an honest account of the product.
The knowledge base states that the Arcules system supports thousands of cameras and other devices including access control panels and IoT sensors, that an ONVIF conformant IP camera will work with Arcules, and, more precisely than most of this category manages, that Arcules itself is not an ONVIF conformant product but supports IP cameras that are. A supported-devices list and a device search tool sit behind that.
Cloud, a gateway appliance, or camera to cloud, chosen site by site rather than for the estate, and able to run alongside XProtect in a hybrid design. That is what turns a large migration into a sequence rather than a cutover weekend, and it means a warehouse on a thin uplink and a head office on fibre can sit under one console on different architectures.
The 2025 releases added camera-to-cloud models, retention set per camera and multi-NIC support for gateway appliances. The 2026 cycle alongside XProtect 2026 R1 extended camera-to-cloud coverage again and introduced long-term video storage. A published cadence lets a buyer tell a maintained platform from a parked one without asking anybody.
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.
Arcules is published as video security as a service, with retention configured per camera as either continuous cloud backup or motion-triggered upload, and long-term video storage added in the 2026 cycle. The video has to reach the cloud to be useful, which is stated as the architecture rather than hedged.
Every site brings its uplink into the project. A distribution center running 40 cameras on a shared 100 Mbps line is a bandwidth calculation before it is a license decision, and a plant whose works council asks where the footage is held needs a residency answer that a cloud service defines rather than the customer.
Arcules publishes its own answer: set the cameras that do not need continuous coverage to motion-triggered upload, and put a gateway appliance in front of the sites where the uplink is thin. Ask for the upload figure per camera per retention tier in writing, and settle residency before the pilot rather than at contract review.
The knowledge base publishes the list of devices certified for camera to cloud. Cameras outside that list reach the platform through a gateway appliance on site, and the 2025 releases added multi-NIC support for those appliances.
The cheapest architecture is available only to the newest cameras. On an estate assembled over a decade, most sites land on the gateway route, which is a hardware line item and a sizing exercise per location on top of the subscription, and it recurs as sites are added.
Run the fleet against the certified camera-to-cloud list model by model before assuming the appliance-free route, and count how many sites qualify. Where they do not, size gateways per site with the multi-NIC option in mind, and phase the rollout so the appliance spend follows the sites rather than arriving all at once.
Enabling cloud analytics on existing cameras is stated as a benefit. What a camera needs in order to qualify for a given analytic, and whether every connected camera qualifies, is not stated on the pages read. The documentation covers that the analytics exist, not what they require of a lens.
That is the gap between a compatibility list and a capability map. A camera can appear in the console, record cleanly and still not be eligible for line crossing or plate recognition, and the fleet most likely to fail that test is the oldest third, which is exactly the part of the estate the project was justified on.
Name the five camera models you actually care about and ask for written qualification per analytic, then run the pilot on the oldest camera in the fleet rather than the newest. The device search tool answers whether a camera connects; only the vendor can answer what it then qualifies for.
The named analytics are people and vehicle detection, line crossing detection, license plate recognition, real-time alerts powered by AI analytics, forensic video search with similarity search, and Ask, the natural-language insights assistant. All of it is security shaped, and no safety or operations detection set appears.
A cloud console over the whole estate is the easiest platform in the building to sell internally, right up to the moment EHS asks for personal protective equipment on the packing line or operations asks for dock dwell. At that point the same cameras are carrying two vendors, two consoles and two contracts.
Arcules has an answer through its parent: Milestone publishes more than 1,000 third-party applications and a Technology Partner Finder, so ask which partner product covers the safety or operations requirement and price it in the same quote rather than next year's. Write the detections you need on one page before the first demo, and mark which side of the security line each one sits on.
Real-time alerts powered by AI analytics are the documented response. No speaker, talk down, strobe or horn behavior appears on the pages read. The documentation covers who gets told, not what happens at the fence.
For a yard or a forecourt whose real requirement is that an intruder leaves rather than that the footage exists, an alert is the beginning of the answer and not the answer. It also means the deterrence decision is a second evaluation, with its own license and its own integration, on top of the platform.
Ask what the platform does at three in the morning with nobody in the console, and ask for it to be demonstrated rather than described. Where a site already runs a public address system or standard speakers, ask every platform on the shortlist which of them drives those without another device at each point.
The same five constraints in one view, sized to paste into an evaluation document.
Swipe the table sideways to see every column.
Arcules data comes from Milestone Systems' Arcules product pages, the Arcules knowledge base and Milestone's Arcules documentation, read on August 14, 2026. Gaps are marked as not publicly specified.
If the cameras are already up, came from several manufacturers, and the goal is one cloud console over all of them without replacing hardware, most of the constraints above stop applying. Choosing cloud, gateway or camera to cloud per site is what makes a staged migration realistic, and running alongside XProtect means a large estate does not have to move in one weekend. You are buying consolidation on purpose, and the supported-devices list proves the claim rather than asserting it.
Spot AI answers the same brief with the opposite architecture, which is why its constraint list looks different. 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 and the residency conversation is short. There is no certified-model tier either: any ONVIF or RTSP IP camera works at full functionality and legacy analog comes in through the IVR, so the oldest third of the estate is not the part that fails a qualification test.
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. Response runs through talk down, strobes and horns on standard speakers already on site, so the moment of the incident is part of the platform rather than a second purchase.
The useful question is not which platform has fewer constraints, but whether your uplink and your oldest cameras can live with the ones it has.
None of that makes Spot AI the right answer for every buyer. Arcules documents its compatibility more finely than Spot AI does, with a supported-devices list, a device search tool and a published camera-to-cloud certification list where Spot AI states compatibility by protocol. Its parent's ecosystem of more than 1,000 third-party applications reaches requirements no single vendor's roadmap will, running alongside XProtect is an option Spot AI cannot offer, and a cloud-only site needs no appliance at all where Spot AI needs the IVR on the wall. 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.
Bridge33 Capital standardized video across 25 plus properties, each acquisition arriving with a different camera system, and cut footage search from hours to minutes.
The YMCA of Greater Richmond deployed 17 locations in two weeks and standardized retention across the estate.
Cambridge City cut footage search from two hours to 30 seconds after consolidating seven municipal locations on one platform.
"With Spot AI, we were able to standardize video surveillance across existing and newly acquired assets, regardless of what cameras were already installed."
Five, all documented: video is held in the cloud with retention set per camera as continuous backup or motion-triggered upload; camera to cloud is limited to a published list of certified devices, so everything else needs a gateway appliance on site; what a camera must be to qualify for a given analytic is not publicly specified; the named detections are security shaped; and on-site response beyond an alert is not publicly specified.
Yes, and the terms are published. The knowledge base states that an ONVIF conformant IP camera will work with Arcules, that the system supports thousands of cameras and other devices including access control panels and IoT sensors, and that Arcules itself is not an ONVIF conformant product but supports cameras that are. A supported-devices list and a device search tool sit alongside. Cameras outside the certified camera-to-cloud list connect through a gateway appliance.
Yes. Arcules is sold by Milestone Systems, its own domain resolves to Milestone's product pages, and the platform is actively developed: the 2025 releases added camera-to-cloud models, per-camera retention and multi-NIC gateway support, and the 2026 cycle alongside XProtect 2026 R1 extended camera-to-cloud coverage and introduced long-term video storage. No end-of-life notice appears on any page read for this article.
The documented response is real-time alerts powered by AI analytics. Speaker, talk down, strobe and horn behavior do not appear on the pages read, so this is an absence of published detail rather than a statement about what the product can do. Ask for the unattended sequence to be demonstrated, and ask which device any audio would run through if a site already has speakers installed.
An edge-first platform, because a cloud video service 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 the uplink is not the problem, Arcules is hard to fault on compatibility.