What LVT's own FAQ, hardware pages and master services agreement say its mobile units do not cover, written for security, construction and property teams comparing deployed hardware against a fixed estate. Every constraint below carries the documentation behind it, the operational impact, and the workaround.
Every constraint below comes from LVT's own current pages at lvt.com, including its FAQ, hardware, features, alert response and privacy pages and its published master services agreement, checked on August 17, 2026. Where LVT documents nothing, this page says so rather than guessing. Spot AI sells a competing platform, so nothing here rests on an anonymous source or an aggregated user rating, and two corrections are worth making before anything else: LVT does publish a unit cost range and a public contract, and its alert response packages are now published per day rather than the per-month volumes quoted in older write-ups.
The unit brings power, connectivity, cameras and deterrence to ground that has none of them. That completeness is the product, and it is also the boundary of what a deployment can reach.
A constraint list is only useful next to an honest account of the product.
Two 400-watt solar panels combined with battery backups, with smart generators providing additional uninterrupted power support, 4G LTE cellular with Wi-Fi and satellite for complex environments, off-road tires and a telescopic mast, all set up in minutes, not days with no wires, power, or internet connection required. For a lot on day one of a build or a yard three hundred meters from the nearest outlet, no software platform answers that at all.
Strobe lights, escalated strobes, a PT spotlight and loudspeakers are published alongside AI Talk Down, described as personalized, human-like voice alerts that describe individuals by their clothing or actions, with the GuardGate mobile barrier and alert response through partnered central stations behind it. LVT has been shipping outdoor deterrence longer than the newer entrants and the pages back it.
The FAQ states LVT Units can cost anywhere from $1,500 to $4,000 depending on your needs and configurations, alert response is published as two packages sized in alerts per day, and the master services agreement is public. On data, LVT publishes that the business deploying the platform retains exclusive access to all camera footage and data, that requests from third parties must be made through the footage owner, and that footage is typically kept for 30 days with each customer able to customize that period.
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.
Nothing on the pages this page read describes LVT ingesting a customer's own fixed cameras, and the published integrations run in the other direction: unit feeds stream into Genetec Security Center, with Axon Fusus and Immix named alongside an open API. The documentation covers where LVT's video goes, not what LVT can read.
The yard and the building stay two systems with two consoles and two sets of alerts. A property team with 60 cameras on the poles, doors and loading bays gets nothing from them under this model, and the intelligence it is paying for applies only to what the units can see.
Split the estate on a site walk: ground that genuinely has no cameras, power or network, and everything already visible to a fixed camera. Ask LVT directly whether an RTSP ingest exists and get the answer dated, then run the fixed half on a platform that reads it so the two halves are not competing for the same budget.
The FAQ states units can cost anywhere from $1,500 to $4,000 depending on needs and configurations. LVT's master services agreement states that subscription hardware is provided, not sold, remains LVT's property and may not be transferred or sold by the customer, references shipping charges for its return, and renews automatically for successive terms unless notice is given at least 30 days before the end of the current term. Title to purchased hardware passes to the customer on delivery.
Covering a second gate is a procurement decision rather than a configuration change, and on the subscription model the coverage ends with the term rather than with a decision you own. A construction group that has quietly accumulated eleven units across four sites is carrying eleven renewal dates and eleven return obligations.
Put the renewal date and the 30-day notice window in the calendar the day the contract is signed, per unit and per site. Model a three-year unit count against the sites you actually intend to keep, and ask which deployments are purchase rather than subscription, since title on purchased hardware passes on delivery.
Alert response is published as two packages. Standard covers up to 15 alerts per day and is active during nighttime hours, described as suiting solar farm daytime coverage and overnight monitoring for retail, construction or critical infrastructure. Extended covers up to 50 alerts per day and is active up to 24 hours per day.
A site gets busier or noisier for reasons the customer does not fully control: a night shift starts, a hedge grows into a camera view, a neighbouring lot changes use. A construction site in its noisiest phase can push past 15 alerts on a bad night, and the nighttime-only window on Standard is a second constraint on any site with a daytime problem.
Baseline the alert volume across a full week before the package is fixed, and tune the zones rather than accepting the tier sized at the point of sale. Ask in writing what happens on a day that crosses the ceiling, whether the count is per unit or per site, and what it takes to move between Standard and Extended mid-term.
LVT states footage is typically kept for 30 days and that each customer can customize that period, and it publishes strong data rights: the business deploying the platform retains exclusive access to all camera footage and data, third-party requests go through the footage owner, and the customer retains title to data collected through the system. Where full-resolution video is held is not publicly specified.
A claims process that opens ten weeks after an incident, an insurer asking for the original file, or a legal hold across a whole estate all need to know where the video lives and who can reach it. The ownership terms are unusually good and they answer a different question from the storage one.
Ask three things in writing during the evaluation: where full-resolution video is stored and in which region, what the export path is for an investigation, and how a legal hold is applied across multiple units. Put the answers next to your own retention policy rather than the published default.
The unit is the product: cameras on a telescopic mast, power from solar with battery backups, connectivity over cellular and the deterrence hardware all deploy together, with camera options across PTZ, thermal, pole-mounted and pole-and-wall mounted. That completeness is the design, and it is also the boundary of what a deployment can see.
A 20-acre yard with three blind corners is three units rather than three zones, and moving a unit to cover a new problem leaves the ground it came from uncovered. Coverage is therefore a map exercise rather than a settings exercise, and it changes every time the site plan does.
Map the coverage arcs on a site plan before the order and mark what each unit gives up if it moves. Keep the fixed estate on a platform that reads the cameras already installed, so units are deployed only where nothing else can see, which is also where their cost is easiest to justify.
The same five constraints in one view, sized to paste into an evaluation document.
Swipe the table sideways to see every column.
LVT data comes from LVT's own pages at lvt.com, including its FAQ, hardware, integrations and alert response pages and its published master services agreement, checked on August 17, 2026. Gaps are marked as not publicly specified.
If the requirement is a lot on day one of a build, a remote yard, an unlit car park or a temporary site that has to be watched from next week, most of the constraints above stop applying, because there are no cameras, no power and no network there to work with. LVT answers that end to end with published hardware, published deterrence and a published cost range, and nothing that runs on cameras a business already owns competes for that job.
Spot AI is the software layer rather than a deployed unit, which is why its constraint list looks different. It is camera agnostic: any ONVIF or RTSP IP camera works at full functionality, legacy analog comes in through the Intelligent Video Recorder, and full-resolution video stays on the IVR in the building while only event metadata crosses the network. The 60 cameras already on the poles, doors and loading bays become the estate the AI runs on rather than a separate system with its own console.
The response does not depend on a unit being parked in the right place. AI Security Guard reads the context and answers within seconds through talk down, strobes or horns on standard speakers already on site, and 15+ pre-trained Video AI Agents cover vehicle break-in, fire, cash register theft, after-hours intrusion, personal protective equipment, forklift near-miss, falls and crowding in hazard zones across every connected camera at once. Mobile units, where a site needs them, come from trailer partners rather than from Spot AI.
Quote the mobile line separately from the fixed estate. A leased unit priced per deployment and a per-camera subscription do not compare on a single line.
None of that makes Spot AI the right answer for every buyer. LVT publishes a unit cost range in its own FAQ, packaged alert response tiers and a public master services agreement, so a procurement team can read the terms before a sales call. More importantly, Spot AI is software on cameras a business already owns: it does not bring power, connectivity or a mast, and mobile units come from trailer partners rather than from Spot AI, so ground with nothing on it is not a job Spot AI does alone. Spot AI publishes no retention period, and access control and sensors arrive through integrations. A constraint list earns its keep by holding each platform's shape against your starting point, and most estates turn out to be a mix of both shapes.
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%.
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.
Blackmon Oil runs a vehicle loitering filter to keep parking lots clean and safe at its around-the-clock stores, with a smaller overnight crew.
"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: the cameras on your own buildings are not part of the published model, since the integrations run outward; coverage is a unit count and subscription hardware is provided, not sold; alert response is metered at up to 15 alerts per day on Standard or up to 50 on Extended; retention is published as typically 30 days without stating where full-resolution video is held; and coverage stops where the unit is parked, so more ground means more units.
Not publicly specified. Nothing on the pages this page read describes LVT ingesting a customer's own fixed cameras, and the published integrations run in the other direction: LVT streams its unit feeds into Genetec Security Center and names Axon Fusus and Immix alongside an open API. Treat that as an absence to confirm with the vendor rather than as a documented no, and plan the fixed estate on the assumption that it stays a separate system.
It depends which category a deployment falls into. LVT's master services agreement states that subscription hardware is provided, not sold, remains its property and may not be transferred or sold by the customer, and that the agreement renews automatically for successive terms unless notice is given at least 30 days before the end of the current term. Title to purchased hardware passes to the customer on delivery, so ask which category each unit sits in.
By volume, and openly. LVT publishes two alert response packages: Standard covers up to 15 alerts per day and is active during nighttime hours, and Extended covers up to 50 alerts per day and is active up to 24 hours per day, with LVT stating it will work with you to match you to one of them. That makes alert volume a budget variable: baseline it across a full week, tune the zones, then fix the package, and get the treatment of an over-ceiling day in writing before you sign.
It depends which half of the estate you are solving. If the cameras are already on the buildings, poles and gates and the goal is one platform across all of them, 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 whole fleet with talk down, strobes and horns through standard speakers. For open ground with no power and no network, LVT remains one of the strongest answers available.