A documented comparison for IT and operations leaders looking at cameras inside a Cisco Meraki estate. The useful question first: Meraki MV is bought as part of a network, on its own camera line. Whether that is the right shape depends on who owns the problem and what is already on the wall.
Cisco Meraki MV is a line of indoor and outdoor cameras managed from the Meraki dashboard, using what Meraki calls cloud augmented edge storage: video is stored on the camera itself, image processing runs on the camera's own processor, and only small amounts of metadata go back to the dashboard. Teams shop for an alternative when the cameras already installed need to stay, when the requirement is a named detection set rather than counting and search, or when video stops being a networking purchase and becomes an operations one. The five below split on exactly those three.
Both architectures keep video off the corporate network and both process at the edge. They part company on a question asked before any of that matters: whose cameras are on the wall.
Every cell is something the vendor publishes, or an explicit not publicly specified.
Swipe the table sideways to see every column.
Cisco Meraki's row was read off documentation.meraki.com on August 12, 2026, including the on-camera storage and processing statements, the Cloud Archive retention options, the facial recognition answer and the MV Sense licensing terms. Meraki's marketing pages moved to cisco.com during 2026, so the technical documentation site is the citable source. The other five rows come from each vendor's public documentation reviewed in July and August 2026 on the same five columns.
Start with what Meraki does unusually well, because it is the reason MV gets bought in the first place. One dashboard covers wireless, switching, SD-WAN, sensors and cameras, which means one vendor approval, one architecture and one support path. The video architecture is genuinely clean: footage sits on the camera, the processing happens on the camera's own chip, and only metadata crosses the network, so there is no server to buy and no raw video competing with production traffic. Meraki also states, without being asked, that its cameras do not identify specific individuals and do no facial recognition, which closes a conversation that stalls plenty of deployments.
The first reason teams look further is that MV is a camera line. There is no documented path for bringing existing cameras into the Meraki dashboard, so adopting it on a site that already has cameras means replacing them. The published integration runs outward: an External RTSP stream a third-party system can consume, which Meraki notes may not itself be encrypted. For an estate assembled through acquisitions, or a plant with working cameras that are nowhere near end of life, that turns a software decision into a hardware programme.
The second is what the video is asked to do. Meraki documents detection and counting: people, vehicles, objects, audio, plates, heatmaps, with MV Sense exposing that as a licensed API. It does not document a named agent set for safety or operations, and it does not document any on-site response when something happens. MV Sense also cannot carry video to another application, only the analytics, so a team hoping to bolt a specialist platform on top of Meraki cameras should confirm that boundary before planning around it.
Meraki's architecture is a network decision that happens to include cameras. If the cameras on your wall are staying, that is the constraint the shortlist has to clear first.
What each one is, where it is strong, and what to check before you commit.
Spot AI is a software-led video AI platform that turns the IP cameras a business already owns into AI coworkers. An on-site Intelligent Video Recorder keeps full-resolution video in the building and sends only event metadata to the cloud, so search and multi-site management stay cloud-based while footage does not leave the facility.
Verkada is a cloud-managed platform that sells its own cameras, access control, sensors, alarms and intercoms under one console, and publishes per-device MSRPs, which is unusual in this market. Third-party cameras come in through Command Connector, which Verkada states is an ONVIF Profile S conformant client and can also ingest RTSP feeds.
Rhombus sells cloud-managed cameras, sensors, access control and alarm monitoring as one system, described by the company as a cloud-edge system that operates offline. Third-party cameras come in through the Relay Connector N100, and the company publishes SOC 2, NDAA, GDPR and TAA compliance badges.
Eagle Eye Networks is a cloud video management system that connects to virtually any ONVIF-conformant camera and digitises analog feeds through analog-ready Bridges and CMVRs, then layers cloud analytics on top of the estate. Its documentation names ONVIF Profile S and dual codec streaming as the integration path.
Coram AI is a camera-agnostic platform built around AI search and investigation across cameras a business already owns, with named detections for firearms, falls and PPE violations, and alerts that can be built in plain English. An on-site appliance called Coram Point is purchased upfront.
Six questions that separate these platforms faster than any feature list.
Answer this before anything else, because it removes options fast. Meraki MV and Verkada both bring their own cameras, though Verkada's Command Connector ingests third-party ONVIF and RTSP feeds. Spot AI takes any ONVIF or RTSP camera plus legacy analog through the Intelligent Video Recorder. Eagle Eye lists more than 7,500 supported cameras and digitises analog through its Bridges. Rhombus reaches third-party cameras through its Relay Connector. Count what you own and what it would cost to replace before you compare features.
Meraki MV is priced and sold through Cisco partners as part of a network estate, which is an advantage when IT owns the refresh and a friction when they do not. If the person with the problem is a safety manager, a loss prevention lead or a plant operations director, check whether the purchase has to travel through a networking budget cycle to reach them.
Meraki documents people, vehicle and object detection, heatmaps, audio detection and license plate recognition. Eagle Eye names Gun Detection, LPR, Face Match and Precision Person and Vehicle Detection. Spot AI ships 15+ named agents across security, safety and operations plus Iris for custom detections. Write down the five things you need spotted and check which vendor names them rather than implying them.
This is where the gap is widest. Meraki's documentation covers detection and notification, with no on-site response described. Eagle Eye documents sirens and talk-down. Verkada's deterrence works with its own BZ11 horn speaker or Intercom hardware. Spot AI runs talk down, strobes and horns through standard speakers already mounted. Decide how much of the response should be automated before an unstaffed shift decides it for you.
Meraki stores video on the camera, with Cloud Archive adding continuous recording for 30, 90, 180 or 365 days as a licensed option, and Smart Codec stretching retention by compressing low-motion scenes. Eagle Eye stores on its own data centers. Spot AI keeps full-resolution video on site in the Intelligent Video Recorder and sends only event metadata out. Match this against your own retention policy and whoever audits it.
Ask about the exit before you sign. Meraki publishes External RTSP so a third-party system can take the stream, while noting the stream itself may not be secured or encrypted, and MV Sense carries analytics but explicitly not video. Rhombus advertises a fully open API. That boundary decides whether a specialist platform can ever sit on top of the cameras you are about to buy.
Spot AI fits when the cameras are staying and the complaint is what the system notices. It connects to any ONVIF or RTSP camera and brings legacy analog in through the Intelligent Video Recorder, ships AI Security Guard, AI Operations Assistant and AI Safety Manager plus Iris for custom detections, and runs talk down, strobes and horns through speakers already mounted. Full-resolution video stays in the building and only event metadata leaves it, which answers the same network objection Meraki answers, without a camera purchase.
Cisco Meraki stays the right call when IT owns the estate and standardizing the whole stack on one dashboard is worth more than reusing cameras. On a greenfield site, or a refresh where the cameras were being replaced anyway, the architecture is clean and the privacy posture is stated up front. The comparison only turns against it when there is an existing camera fleet somebody expects to keep.
Onboarding a site's cameras is the expensive part of any of these decisions, and it is the part you only want to do once.
Watch the AI coworkers work on your live feeds, not a demo reel.
Customer-reported outcomes from named Spot AI customers.
Bridge33 Capital standardized video across 25 plus commercial properties on whatever cameras each acquisition already had, and cut footage search from hours to minutes.
Cambridge City cut the time it takes to find footage from two hours to thirty seconds.
All Star Elite brought cash shrink down from about 6% to 1% across its store estate, and cut investigation time by more than half.
"With Spot AI, we were able to standardize video surveillance across existing and newly acquired assets, regardless of what cameras were already installed."
The five covered here are Spot AI, Verkada, Rhombus, Eagle Eye Networks and Coram AI. Spot AI fits teams keeping the cameras they already own. Verkada fits a single-vendor build with hardware budget. Rhombus fits mid-market cloud-managed camera estates. Eagle Eye fits mixed, partly analog estates moving to cloud management. Coram AI fits investigation-heavy multi-site teams.
No documented path exists for bringing other manufacturers' cameras into the Meraki dashboard; MV is its own camera line. The documented integration goes outward, through an External RTSP stream a third-party system can consume, and Meraki notes that stream may not itself be secured or encrypted. If keeping an existing fleet matters, confirm this early, because it decides whether the project is software or hardware.
No, and its documentation says so directly: Meraki smart cameras do not identify or track specific individuals, they only detect them. That applies to both people detection and object detection. All the image processing happens on the camera's own processor, with small amounts of metadata sent to the dashboard, which is a genuinely strong answer where monitoring is a sensitive subject.
Video is stored on the camera itself, so retention depends on the model and the quality setting. Meraki's own worked example is the MV32 at 256 GB reaching up to 20 days recording continuously. Cloud Archive is a licensed option adding continuous recording for 30, 90, 180 or 365 days, and Smart Codec extends retention by compressing scenes with less motion.
Not as a figure. MV hardware and licenses are quoted through Cisco partners rather than listed. Meraki does publish the MV Sense licensing model: it is licensed per camera, does not co-terminate, and each organization with second-generation cameras gets ten free MV Sense licenses that do not expire. Of the platforms on this page, Verkada is the one publishing per-device MSRPs.