What Meraki's own documentation says MV does not do, or only does on certain models, written for network and security teams sizing cameras inside a Meraki estate. Every constraint below carries the documentation behind it, the operational impact, and the workaround.
Every constraint below comes from Meraki's own documentation, datasheets, MV FAQ and end-of-life notices, read on August 14, 2026. Meraki's marketing pages refuse a plain fetch, so they were read in a browser rather than assumed. Where Meraki publishes nothing, this page says so rather than guessing. Spot AI sells a competing platform, and one thing is worth saying before any constraint is read: Meraki documents its own limits more carefully than almost anyone in this category, so most of what follows is quoted from pages Meraki wrote about itself rather than dug out of anywhere.
Putting the recorder and the processor inside the camera is what makes MV simple to run. It is also why retention, capability and eligibility are all decided by which unit is on the wall.
A constraint list is only useful next to an honest account of the product.
Every MV model is published with its capability, its firmware minimum and a dated lifecycle notice, including MV Gen 2 cameras at end of sale on 31 December 2025 with end of support on 31 December 2030, and MV21 and MV71 already at end of support on 19 June 2026. An IT team can build a refresh plan from published pages rather than from an account manager's calendar.
Video records to solid-state storage inside each camera and image processing runs on the camera's own processor, so there is no recording server per site to size, patch, license or replace. Meraki also publishes that cameras keep recording without network access as long as they have power, with only the live stream to the dashboard unavailable, which is a specific answer where most platforms offer a diagram.
NDAA is published for second and third generation MV cameras and TAA for third generation, and the platform carries PCI DSS v4.0, SOC 2 Type II and ISO/IEC 27001, 27017 and 27018. Meraki also states plainly that it does not identify specific individuals and performs no biometric identification, which is a position a works council or a data protection officer can be handed directly.
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.
Meraki's MV FAQ answers it in its own words: only MVs stream to the dashboard. External RTSP runs the other way, sending MV video outward into an existing deployment, and Meraki publishes the conditions in the same breath: live only, one stream per camera, no metadata, no encryption on that stream, firmware 4.2 or newer, and no support on MV21 or MV71.
Cameras from any other manufacturer stay on whatever system they are on today. On a site inherited through an acquisition, or a plant whose cameras are nowhere near end of life, standardizing means a camera purchase per site rather than a software decision, and until that purchase happens the team runs two systems and two habits.
Meraki's own answer is External RTSP, so treat the MV fleet as a source rather than as the console and run a camera-agnostic layer over everything else. Otherwise, align the standardization with the refresh cycle rather than the contract date, and let the MV footprint grow site by site as cameras genuinely reach end of life.
Video records to solid-state storage inside each camera, and Meraki publishes that higher resolution, higher quality and more motion all reduce retention. Days of footage are therefore an outcome of the model, the settings and the scene rather than a number configured once for the estate.
A retention policy written as thirty days has to be verified per model and per scene. The busy loading dock at 4K holds far less than the quiet corridor at the same setting, and the cameras that matter most in an investigation are usually the ones watching the busiest scenes, so the policy fails first exactly where it is needed.
Measure retention per camera in the first month rather than accepting a datasheet figure, then tune resolution and quality scene by scene. Where a legal or insurance requirement fixes the number, Meraki's own answer is Cloud Archive, and the cameras that need it are usually a small subset rather than the estate.
Cloud Archive is published as 30, 90, 180 or 365 days of continuous recording, sold as a per-camera license and needing up to 3 Mbps of upload per camera. MV Sense is licensed separately, with ten MV Sense licenses available per organization on second-generation cameras at no charge.
Both halves scale with the fleet. Forty cameras at one site on Archive can ask for up to 120 Mbps of sustained upload, which on a shared 100 Mbps line is not a budget question but a network redesign, and the license renews per camera per year alongside it.
Apply Archive to the cameras that carry an evidence obligation rather than to the estate, and calculate the upload figure per site against the actual uplink before signing. Where the number does not fit, that site is telling you it needs storage in the building rather than in the cloud.
License plate recognition is published as an Early Access feature running only on the MV53X, focused on North America, requiring an MV Sense license and an MQTT broker. Cross-camera tracking arrived in July 2026 for third-generation dome cameras. The general set is Motion Search, Motion Recap, motion heatmaps and person and vehicle object detection.
A feature announced this quarter may not reach the cameras on your walls at all, because the analytics run on the camera's own processor. Publishing exactly which model carries which capability is a courtesy most of this market does not extend, and it is still a constraint: the capability map is a hardware inventory.
Build the capability map from the published model pages before assuming a feature is available, and put the models carrying the capability you need at the front of the refresh list. For plate reading specifically, confirm the MV53X count, the MV Sense licenses and who runs the MQTT broker before it appears in a business case.
Microphones and audio detection are documented on selected models. No speaker, talk down, strobe or siren behavior appears in the documentation read for this page. What is published instead is the hook: MV Sense exposes camera analytics over REST and MQTT.
For an unstaffed yard, a detection that ends in a dashboard notification is a record rather than a response. The MQTT hook means the action can be built, which turns a product question into an ownership question: somebody has to write it, host the broker, and still own it after the person who built it moves on.
If deterrence matters, name who builds and supports the MV Sense integration and price that work in the same business case as the cameras. Where a site already has speakers, ask each platform on the shortlist which of them drives those directly rather than through an integration you maintain.
The same five constraints in one view, sized to paste into an evaluation document.
Swipe the table sideways to see every column.
Meraki data comes from its own MV documentation, datasheets, FAQ and end-of-life notices, read on August 14, 2026. Gaps are marked as not publicly specified.
If wireless and switching are already Meraki and the network team owns physical security too, MV removes the recorder, the per-site software and most of the operational surface, and it arrives in a console that team already lives in. The published lifecycle dates and the compliance list make it one of the easier platforms to plan a five-year refresh around, and a site on a poor uplink still keeps recording. Most of the constraints above stop applying when the cameras are being bought new anyway.
Spot AI answers the same brief from the software side, which is why its constraint list looks different. Any ONVIF or RTSP IP camera works at full functionality, whoever made it, and legacy analog comes in through the Intelligent Video Recorder, so a site inherited through an acquisition joins the same console as everything else without a camera purchase in front of it. The agent set is the same on a camera bought last month and a camera bought in 2016, because the detections do not run on the camera's own processor.
Retention and bandwidth work differently as a result. Full-resolution video stays on the IVR in the building and only event metadata crosses the network, so days of footage are a property of the recorder rather than of each camera's storage and scene, and adding retention does not add upload. Response runs through talk down, strobes and horns on standard speakers already on site, without a broker to host or an integration to maintain.
The useful question is not which platform has fewer constraints, but whether you are buying cameras or buying what the cameras you already own could notice.
None of that makes Spot AI the right answer for every buyer. Meraki publishes per-model lifecycle dates and a compliance list covering PCI DSS v4.0, SOC 2 Type II and ISO/IEC 27001, 27017 and 27018 that Spot AI does not match page for page, and a team already standardized on the Meraki dashboard gets cameras, switching and wireless in one console that Spot AI cannot be. MV also needs no appliance on site at all, where Spot AI keeps an Intelligent Video Recorder in the building. 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%.
Bridge33 Capital standardized video across 25 plus properties, each acquisition arriving with a different camera system, and cut footage search from hours to minutes.
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.
"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: only MVs stream to the dashboard, so third-party cameras stay where they are; retention is a property of each camera, and higher resolution, quality and motion all reduce it; Cloud Archive is a per-camera license needing up to 3 Mbps of upload; capability tracks the model, with plate recognition in Early Access on the MV53X only; and on-site response beyond a notification is not publicly specified.
No, and Meraki says so plainly: its MV FAQ states that only MVs stream to the dashboard. The integration runs outward instead. External RTSP is published as a way to bring MV video into an existing deployment, with documented limits of live only, one stream per camera, no metadata, no encryption on that stream, firmware 4.2 or newer, and no support on MV21 or MV71.
It depends on the camera and the scene rather than on a setting. Video records to solid-state storage inside each camera, and Meraki publishes that higher resolution, higher quality and more motion all reduce retention. Cloud Archive is the optional second copy at 30, 90, 180 or 365 days as a per-camera license needing up to 3 Mbps of upload. Meraki also publishes that cameras keep recording as long as they have power when network access is lost.
Microphones and audio detection are documented on selected models, and no speaker, talk down, strobe or siren behavior appears in the documentation read for this page. What is published is the hook rather than the action: MV Sense exposes camera analytics over REST and MQTT, so a response can be built. Ask who would build it, who hosts the broker, and who owns it two years later.
A camera-agnostic platform, because the MV FAQ closes the question directly. Spot AI works with any ONVIF or RTSP IP camera and brings legacy analog in through the Intelligent Video Recorder, runs 15+ pre-trained Video AI Agents across the whole fleet rather than per model, and keeps full-resolution video on site. If the estate is already Meraki end to end, MV is hard to fault on operational simplicity.