Cisco Practice
Cisco Meraki Licensing. Tiers and renewal levers.
Meraki licenses every device on a subscription, by tier, and stops working when the license lapses. Read the tiers and the co termination math before you renew.
Meraki licenses every device on a subscription, by tier, and stops working when the license lapses. Read the tiers and the co termination math before you renew.
Cisco Meraki ties every device to a subscription that must stay current or the hardware stops forwarding traffic, and the tier you buy decides far more than the headline price.
Meraki is a cloud managed platform, so every device is licensed as a subscription rather than owned outright. The license is not optional. When it lapses, the device stops passing traffic after a grace period, which makes Meraki licensing an availability issue, not just a cost one.
Cisco publishes the licensing models and the co termination versus per device options on its Meraki licensing documentation, and the product tiers sit on the Meraki product pages.
The co termination rules are detailed in the Meraki licensing FAQ, the contract terms sit in the Cisco end user license agreement, and current packaging is on the Meraki site.
You license each access point, switch, and security appliance individually. The price depends on the device class, the feature tier, and the term length. A long term on a low tier can cost less than a short term on a high tier, so all three variables matter.
Meraki gives a grace period, then disables the device. There is no perpetual fallback mode. This is why lapsed renewals are an operational risk and why Cisco holds leverage at the expiry date if you have not planned ahead.
Cisco Meraki license tiers at a glance
| Tier | Typical scope | Best fit | Watch for |
|---|---|---|---|
| Enterprise | Core management and standard features | Most general purpose sites | Adequate for many estates |
| Advanced / Secure | Added security and analytics features | Sites needing the extra capability | Paying for unused features |
| Co termination | All licenses share one expiry | Estates wanting one renewal date | Unused months on new devices |
| Per device term | Each device on its own clock | Phased refresh and growth | More dates to track |
The tier choice is the largest controllable line on a Meraki estate. Advanced tiers add security, analytics, or SD WAN features that some sites genuinely need and many never touch. Buying Advanced as a default is the most common overspend.
Tiers tend to ratchet up and never down. A site provisioned at Advanced for a project that ended stays on Advanced at every renewal unless someone challenges it. Pull the feature usage data and downgrade the sites that do not use the extra capability.
Co termination aligns every license to one expiry date. It simplifies administration, but it changes the cost math. When you add a device mid cycle, you pay to bring it up to the shared date, which can mean buying months you will not use.
If you add devices steadily through the year, per device term avoids paying to align each new unit to a single date. The trade is more renewal dates to manage, which a simple tracker handles. Price both models against your actual deployment pattern.
The standard reseller advice is to put the whole estate on co termination and buy the Advanced tier everywhere for simplicity. We disagree. In roughly half the Meraki estates we reviewed in 2024 and 2025, uniform Advanced licensing and co termination on a growing estate added 15 to 30 percent of avoidable cost, because sites paid for unused features and unused months. The buyer side move is to match the tier to each site's real feature usage and to choose co termination only where the device count is stable. Simplicity that you pay for every year is not a saving.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
On a Meraki estate the license that fails is the one nobody planned to renew, and the license that overcharges is the tier nobody reviewed.
The renewal is where you recover the tier drift and the wasted months. Bring a device inventory, the feature usage by site, and a costed comparison of co termination against per device term.
Cisco holds the most leverage in the final weeks before expiry, because the alternative is a device that stops working. Start the renewal early, confirm the inventory, and negotiate the tier and term before the clock pressures you.
Meraki is cloud managed, so every device runs on a subscription license sold per device, per feature tier, and per term. The license is mandatory, because a device stops forwarding traffic after a grace period once its license expires, which makes Meraki licensing an availability matter as well as a cost one.
After a grace period, Meraki disables the device and it stops passing traffic. There is no perpetual fallback mode, so a lapsed renewal is an operational outage risk. This is also why Cisco holds leverage at the expiry date if a renewal has not been planned in advance.
Enterprise covers core management and standard features, while Advanced or Secure tiers add security, analytics, or SD WAN capabilities at a materially higher price. Many sites only need Enterprise, so buying Advanced everywhere as a default is the most common Meraki overspend.
Co termination aligns every license in the organization to a single shared expiry date. It simplifies renewal administration, but when you add a device mid cycle you pay to bring it up to that shared date, which can mean buying months of license you never use.
It depends on your deployment pattern. Co termination suits stable estates that renew once a year. Per device term suits estates that add devices steadily, because it avoids paying to align each new unit to a single date. Price both models against your actual growth.
In our 2024 to 2025 reviews, matching the tier to real feature usage and choosing the right term model cut renewals by around 19 percent on average. The savings came from downgrading over tiered sites and avoiding unused co termination months, not from a headline discount.
In defined cases you can reassign or reclaim licenses, for example when retiring a device and deploying a replacement. The rules depend on the license model and the device class, so confirm the reclaim options before assuming a retired device's license is lost.
Start at least ninety days before the earliest expiry. Cisco holds the most leverage in the final weeks, because the alternative is a device that stops working. Beginning early lets you negotiate the tier and term on your timeline rather than under expiry pressure.
The per device tiers, the co termination math, the renewal traps, and the levers that stop silent price creep on a Meraki estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
