The Per-Device Cloud Model
Cisco Meraki licensing is a per-device, per-year cloud subscription tied to the Meraki Dashboard. Every access point, switch and security appliance carries its own active licence, enforced from the cloud rather than on the box. The defining characteristic — and the one that distinguishes Meraki from the rest of the Cisco estate — is that the licence is not a perpetual unlock: when a device's subscription lapses, it enters a grace period and then stops passing traffic. The hardware effectively bricks until re-licensed.
That cloud enforcement makes renewal a hard operational deadline, not just a commercial one. List prices run from about $150 per device per year for an entry access point to more than $1,500 for a high-end MX security appliance with advanced security enabled — a wide range that makes tier and term choices material across an estate. The model contrasts sharply with the on-device subscriptions covered in the DNA licensing tier guide, and understanding the difference matters when a network mixes both.
MR, MS and MX Licence Tiers
Each Meraki product line has its own tiers, and as everywhere in the Cisco portfolio the right tier is the lowest one that covers the features a device actually uses.
| Product | Tiers | Indicative List (per device/yr) |
|---|---|---|
| MR (Wireless APs) | Enterprise, Advanced (Upgrade) | From ~$150 |
| MS (Switches) | Enterprise, Advanced (select models) | Model-dependent |
| MX (Security / SD-WAN) | Enterprise, Advanced Security, Secure SD-WAN Plus | $475–$1,500+ |
An MX75, for example, lists around $475–$650 for a one-year Enterprise licence and $525–$700 for Advanced Security, depending on the reseller. The decision that drives MX cost is whether each appliance genuinely needs Advanced Security or Secure SD-WAN Plus, or only routes basic traffic on Enterprise — paying the higher tier on appliances that never use the advanced features is shelfware priced per device per year. This is the same right-tiering discipline applied to the security portfolio in the Cisco security licensing guide and the SD-WAN estate in the Cisco SD-WAN licensing guide.
Co-Termination Mechanics
Meraki's default is co-termination: every licence in an organisation aligns to a single expiry date, calculated as a weighted average across all active licences. Add devices mid-term and the co-term date shifts; the model keeps one renewal but makes that renewal a moving target you have to track. Per-device licensing (PDL) still exists for some organisations but is no longer offered to new customers, and licences cannot move between a co-term and a PDL organisation — a constraint worth knowing before any consolidation.
Co-termination concentrates the entire Meraki estate into one expiry. That is administratively neat but commercially exposed — a single annual deadline a reseller can lean on. Treat the co-term date as a planned event aligned to your budget cycle, and reconcile the device count well ahead of it, the same renewal-timing discipline that governs the subscription transition.
Inside an Enterprise Agreement the mechanics change in the buyer's favour: EAs always use co-term, the EA end date never moves regardless of when you add equipment, and you can over-consume within covered suites and settle at a True Forward event — so you are never out of compliance for adding covered devices. That removes the bricking risk for in-scope hardware and turns the deadline into a reconciliation rather than a cliff.
Term Length and Discounts
Meraki licences are available for 1, 3, 5, 7 and 10-year terms, and longer commitments carry steeper discounts. For a stable deployment with a predictable refresh cycle, a longer term locks in a lower annual rate and reduces renewal frequency; for a fast-changing estate, a shorter term preserves flexibility at a higher unit cost. The trade is the same capex-versus-flexibility judgement that runs through the whole subscription model.
The discipline is to match term length to how confident you are in the device's life — not to default to the longest term for the headline discount on hardware you may replace in three years. Modelling the term against the refresh plan, device by device where the estate is large, prevents a long-term discount becoming a long-term commitment to obsolete kit.
Folding Meraki Into a Cisco EA
The single biggest pricing lever is folding Meraki into a wider Cisco Enterprise Agreement. Cisco customers adding Meraki to an EA can typically negotiate blended rates 20–30 percent below standalone Meraki pricing, because the committed value across the broader agreement lifts the discount band. Where an organisation already runs a Cisco EA for networking, security or collaboration, bringing Meraki under the same umbrella is often the cleanest saving available.
The EA route also smooths the operational risk: covered Meraki devices settle through True Forward rather than bricking on lapse, and the single EA date replaces the moving co-term target. Structuring that inclusion well is part of the wider negotiation set out in the Cisco EA negotiation and pricing guide and the overall Cisco Enterprise Agreement and licensing guide.
Optimising Meraki Spend
Optimising Meraki is three moves: right-tier every device to the features it uses, choose term lengths that match each device's expected life, and fold the estate into an EA for the blended discount. Remove decommissioned devices from the dashboard promptly so they stop counting toward the licence total, and reconcile the device inventory against the licence count before every co-term renewal so you renew what you run, not what you ran two refreshes ago.
Done together, these turn Meraki from a quietly compounding per-device cost into a controlled line with a predictable renewal. To run a Meraki tier-and-term review and fold the estate into your next Cisco negotiation, request a confidential briefing, or download our Cisco EA Playbook.