Skip to content
Safety Tech Review
Menu

Cisco Meraki MV

Cisco's cloud-managed smart camera line, which stores video and runs people and vehicle detection on the camera, with APIs and custom computer vision models that partners can use for safety use cases.

Category
Video platform
Founded
2006 (Meraki); acquired by Cisco in 2012
Headquarters
San Francisco, California, USA
Deployment
Own cameras with on-camera storage and analytics, managed from the Meraki cloud dashboard; optional cloud archive; per-camera licences
Funding
Part of Cisco Systems (NASDAQ: CSCO)
Focus
retail, education, healthcare, offices, warehousing, multi-site organizations

Public evidence checklist

What a buyer can verify about Cisco Meraki MV from public sources, checked 2026-10-06. This is desk research, not a hands-on test, and it is not a rating or a ranking: a missing item may simply be shared under NDA, so ask for it. How we check

  • Security or trust page: found · Meraki trust center: data center security, storage architecture, security tools, subprocessors, SLA, vulnerability reporting and rewards, technical and organizational measuressource
  • Data processing agreement published: found · Trust page refers to the Cisco Master Data Protection Agreement (MDPA) with EU standard contractual clauses, and publishes a subprocessor list; MDPA text itself not openedsource
  • ISO 27001 or SOC 2 claimed: found · SOC 2 Type II, ISO/IEC 27001, 27017, 27018, PCI DSS v4.0 and FedRAMP Moderate listed (vendor claim; Meraki cloud, not MV-specific)source
  • Privacy features documented: found · Retention controls (motion-based retention, Smart Retention, Cloud Archive with 30 to 365-day options); Cloud Archive encrypted in transit and at rest per FAQ. Face blurring or privacy masking not confirmed in the pages readsource
  • Deployment architecture documented: found · On-camera storage and analytics managed from the cloud dashboard; optional Cloud Archive; storage per model (MV32 256 GB, about 20 days)source
  • Pricing or pricing model public: not found · Licensing model documented (per-camera MV Sense and Cloud Archive licences, ten free MV Sense licences per organization) but no pricesnot found
  • Accuracy or validation method published: not found · People and vehicle detection documented without accuracy figures or validation methodnot found
  • Independent evidence: not found · No independent test or analyst evaluation of MV analytics for safety use foundnot found
  • Named customer case study: not found · No named MV customer case with measured safety outcomes found in the pages reviewednot found
  • Integrations listed: found · MV Sense REST and MQTT APIs; Custom Computer Vision for uploaded TFLite models with MQTT outputsource
  • Company details disclosed: found · Cisco Meraki, part of Cisco Systems since December 2012, headquartered in San Francisco (Wikipedia)source
  • Third-party reviews (5 or more): not found · G2 refused automated access on 2026-10-06; review count not checkednot found

What it does

Cisco Meraki MV is a line of security cameras managed from the same cloud dashboard as Meraki networking equipment. It is a video platform rather than a safety analytics product. Its relevance to safety buyers is that the cameras process video on the device and expose detections to other software, so a site that already runs Meraki can add safety use cases without a separate video server.

Each camera records to its own storage. For example, Meraki says the MV32 fisheye has 256 GB and can hold up to about 20 days of continuous recording, depending on quality [2]. Built-in machine learning detects people and vehicles; detections appear as boxes on recorded video and feed occupancy counts, histograms and motion heatmaps in the dashboard [4].

Two features matter for safety use. MV Sense is a licensed set of REST and MQTT APIs that sends the camera's detections to third-party applications; Meraki says organizations with second-generation cameras get ten free MV Sense licences [2]. Custom Computer Vision lets a customer or partner upload its own TensorFlow Lite model to a camera, which then runs it and publishes detections over MQTT; one custom model runs per camera at a time, and an MV Sense licence is required [3]. In practice, use cases such as PPE checks or forklift and pedestrian proximity would come from a partner model or application, not from Meraki's built-in people and vehicle detection.

Who it is for

MV suits organizations already standardized on Meraki networking, especially multi-site businesses that want central management without on-site recorders. Safety teams would usually work with IT, because the dashboard, licences and APIs sit with network administrators.

How it is deployed

Video stays on the camera unless a user streams it or the customer buys Cloud Archive. Meraki says Cloud Archive uploads over TLS and stores video encrypted at rest [2]. Retention depends on resolution, quality and how much motion a scene has; motion-based retention, Smart Retention and Cloud Archive can extend it [5]. Cloud Archive licences come in 30 to 365-day storage options, per camera [2].

Meraki's trust pages describe an out-of-band architecture in which only network configuration and usage statistics are stored in the cloud, describe data center controls, list subprocessors, and refer customers to Cisco's Master Data Protection Agreement, which includes EU standard contractual clauses [1]. Meraki lists certifications including SOC 2 Type II, ISO/IEC 27001, 27017 and 27018, PCI DSS and FedRAMP Moderate (vendor claim) [1].

Notable public customers and coverage

Meraki was founded in 2006 and acquired by Cisco in December 2012 for about $1.2 billion, according to Wikipedia [6]. The trust page covers the Meraki cloud as a whole rather than MV specifically [1]. We did not find a named Meraki MV customer case with measured safety outcomes, a published accuracy figure for MV object detection, or an independent test of MV analytics in the pages we reviewed [4].

Things to ask in an evaluation

  • Which safety detections (PPE, zones, forklift proximity) are available today, and from which partner application or model?
  • What accuracy and false alarm data exist for those detections in conditions like yours?
  • How much retention will each camera give at your resolution and motion level, and is Cloud Archive needed?
  • What does the MDPA cover for MV video, and where is archived video stored?
  • What are the total costs of cameras, licences and partner applications over five years?

Our take

Strengths

  • Strong published security and privacy documentation for the Meraki cloud, with a subprocessor list and a data protection agreement route [1].
  • Edge processing and on-camera storage reduce bandwidth and keep most video on site [2] [5].
  • Open, documented paths for partners: MV Sense APIs and custom models on the camera [2] [3].

Watch-outs

  • Built-in analytics detect only people and vehicles; safety use cases depend on partners or custom models [3] [4].
  • No published accuracy method or safety case studies for MV analytics [4].
  • Works only with Meraki cameras and per-camera licences, and prices are not on the pages we reviewed [2].

Best fit: Organizations already running Meraki that want cloud-managed cameras across many sites and plan to add safety analytics through a partner application or their own models.

This profile is desk research from public sources, not a hands-on product test or an endorsement. Last reviewed 2026-10-06. Spot an error? Tell us.

Sources

  1. [1]Cisco Meraki: Trust
  2. [2]Cisco Meraki Documentation: MV Smart Camera FAQ
  3. [3]Cisco Meraki Documentation: MV Sense Custom Computer Vision
  4. [4]Cisco Meraki Documentation: MV Object Detection
  5. [5]Cisco Meraki Documentation: Video Retention
  6. [6]Wikipedia: Cisco Meraki