The trigger moments that start this conversation, what actually changes on day one and a four-phase plan that keeps every site recording throughout. Written for teams running a self-learning analytics layer on top of a video management system they already own.
The cameras do not move, so switching changes what sits behind them and how far a detection travels. Both rows describe what each vendor publishes.
Four moments when teams running a self-learning analytics layer start this conversation. If none of them are true, staying put is a reasonable answer.
icetana learns what is normal for each camera and shows what is not, and it publishes that plainly: trained on 700 million hours of real-world video, first alerts inside 24 hours, fully learned in a week. That is a genuinely different job from asking a named question of a named zone. When the request becomes forklift speed in one aisle, or a dock door left open past twenty minutes, an anomaly model answers it only when the behavior happens to be rare.
icetana is a layer, so its renewal is rarely the whole question: the recorder underneath renews too. Ask both vendors to quote the identical site list with recording and detection on one line, because comparing an analytics license against a platform that also records is not a comparison. The cheapest moment to run that exercise is when the two dates are close together.
icetana surfaces unusual events on its Livewall for a control-room operator, and no speaker, strobe or talk-down behavior appears on the pages it publishes. If a site is unstaffed at 03:00, a detection is worth exactly as much as the person available to act on it. That is the gap to size before anything else, because it is the one a better model does not close.
icetana names loitering, fire and smoke, trip and fall, aggressive behavior and unusual location, time of day, direction, speed and count, plus facial recognition, license plate recognition and Forensic Quick Find. That set is shaped for a security operations center. If EHS now wants PPE compliance or a near-miss count on the same fleet, that is a second vendor unless the platform already covers it.
The structural differences that decide whether a switch is worth starting.
Swipe the table sideways to see every column.
icetana data comes from icetana's own public documentation at icetana.ai, read on August 14, 2026, including its FAQ answers and its published detection list. Where icetana publishes nothing, this table records the absence rather than guessing at a value.
A rollout that keeps coverage live throughout. Most sites go live inside six weeks.
Inventory the fleet per site: manufacturer, model, resolution, codec and network path, plus which video management system icetana currently reads from and what that system is licensed for. Because both platforms read the same cameras, this phase is a coverage map rather than a replacement list. The finding that decides the project is what the recorder underneath is contracted for, because leaving the analytics layer and leaving the recorder are two decisions with two end dates.
Run one site live on both at once. That overlap is the point: it is the only way to compare detection quality and what happens after a detection on identical footage, and it costs one site's license rather than an estate. Pick the site where operator coverage is thinnest rather than the busiest one, because the difference between the two platforms shows up in the hours when nobody is watching the wall.
Move site by site rather than estate-wide, keeping icetana running at each site until its replacement has passed a full week. Cameras do not move and cabling does not change, so a site cutover is a configuration change plus an IVR. The analytics layer can be retired independently of the recorder underneath it, so cut the detection over first and let the video management system run out its own term if it has time left.
Once coverage is stable, the work moves from parity to what the old arrangement could not do: adding operations and safety agents on the same cameras, building an Iris detection for something specific to your process and setting what fires at 03:00 when nobody is watching the wall. This phase is where the switch stops being a license exercise and starts paying for itself.
The six that come up in every one of these conversations.
Most switches start before the contract ends, because assess and pilot cost little and the comparison is more honest with both systems live. Run the pilot on one site during the overlap and time the cutover to the renewal date rather than paying twice across the estate. Check the recorder's date at the same time: the two rarely expire together and the later one usually sets the schedule.
No, and the plan makes that structural rather than a promise. Your video management system keeps recording throughout, icetana keeps analyzing at each site until its replacement has run a full week, the cameras never move and cutover happens site by site. If a site fails its sign-off test, that site stays where it is while the others proceed.
It is not icetana's to hand over. icetana publishes no storage or retention behavior, so the footage lives in the video management system underneath it, which is where the export question belongs. Pull the export list and the retention obligation out of that system during the assess phase, not from the analytics contract.
Camera reuse is common ground, so it is not the reason to move. What changes is whether the platform also records, whether detection is a question you asked or a statistical outlier, whether the same fleet reaches past security into operations and safety. Then there is the one that matters most at 03:00: whether anything happens at the moment of a detection without a person reading the wall.
That cost is real and worth naming. The offset is that natural language search removes most of the scrubbing the old workflow needed, so the skill being replaced is largely the one nobody enjoyed. Budget a fortnight of overlap in the pilot so the team compares on their own footage rather than on a demo reel, and let the operators, not the buyer, call the result.
It depends on how much of the stack you are counting, and anyone who answers without that scope is guessing. icetana publishes one entry offer, 40 camera streams from $499USD as a limited time offer. Quote both against the identical site list over three years, and put the recorder underneath icetana on the same line, because a platform that records and detects is being compared with two products, not one.
Bring a camera list and we will tell you what works as it is.
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.
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.
"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."
No. icetana states it is camera agnostic and connects to widely used video management systems or directly to cameras, and Spot AI reads any ONVIF or RTSP IP camera. Analog channels that run through encoders or a hybrid recorder today come in through the Intelligent Video Recorder instead. Nothing on the wall moves and no coax is pulled.
Most estates are live inside six weeks: a week to assess, a fortnight of pilot on one site, then site-by-site cutover. Sites go live individually rather than in one switch, so the timeline scales with how many sites you have rather than how many cameras.
Not necessarily, and the two decisions should be kept apart. icetana is an analytics layer reading from the recorder, so its license can be retired on its own date. Spot AI records as well as detects, so the recorder underneath becomes optional over time rather than on day one. Let the license with the longer term set the schedule.
Yes, and the plan depends on it. The pilot runs one site on both at once so detection and response can be compared on identical footage. icetana keeps analyzing at every site until that site's replacement has passed a full week of sign-off.
icetana learns what is normal for each camera and surfaces what is not, which is why it needs no manual set-up and is useful inside a day. Spot AI ships named detections instead: 15+ pre-trained agents across security, safety and operations, plus Iris for a detection specific to your process. One finds the outlier, the other answers the question you asked.