Meraki licensing is subscription only, and an expired license stops the hardware. Read the models, the expiry risk, and the EA math before you renew.
Cisco Meraki is sold as a hardware plus subscription model where an expired license can disable working devices, which makes renewal leverage and term alignment unusually important.
Meraki sells hardware that only functions while covered by a valid cloud subscription. Buy a switch, access point, or security appliance, and you also buy a license that keeps it managed and operational.
That coupling of hardware and license is the defining feature. Unlike traditional networking gear, a Meraki device with an expired license eventually stops passing traffic.
Cisco documents the model on the Meraki licensing pages, and the operational detail sits in the Meraki licensing documentation. Read both before a renewal.
Per device licensing assigns each device its own license and term. Licenses come in tiers, commonly Enterprise and Advanced, where the higher tier unlocks more security and management features.
Co termination pulls every license to one shared expiry date. It is simpler to track, but adding a device mid term means paying to align it to the common date. Cisco has also moved toward per device licensing as the default, described in the per device licensing overview.
Cisco Meraki licensing models compared
| Model | How it tracks | Strength | Weakness |
|---|---|---|---|
| Co termination | Single shared expiry | Simple to renew | Pay to align new devices |
| Per device | Each device own term | Granular control | Many dates to manage |
| Enterprise tier | Core management and routing | Lower cost | Fewer security features |
| Advanced tier | Adds security and analytics | Full feature set | Higher per device cost |
Co termination optimizes for simplicity by giving you one renewal date. Per device optimizes for control by tracking each device separately. The right choice depends on how stable and uniform your estate is.
A stable, uniform estate suits co termination. A changing estate with mixed device lifecycles suits per device, because you avoid paying to align every new device to a shared date.
The standard reseller advice is to move everything to co termination because one date is easier to manage. We disagree. In roughly half the Meraki estates we reviewed in 2024 and 2025, co termination cost 5 to 15 percent more than per device licensing once the alignment payments for mid term device additions were counted. The buyer side move is to model both against your real device refresh pattern. If you add devices steadily through the year, per device licensing usually wins, because co termination forces you to buy partial periods every time you align a new device to the shared expiry.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
With Meraki the license is not a maintenance contract, it is the on switch. That changes how much leverage expiry timing really gives the vendor.
The traps are letting licenses approach expiry under shutdown pressure, over buying tiers, and locking shelfware into an Enterprise Agreement. Each is avoidable with planning.
Cisco offers Meraki inside its broader Enterprise Agreement. An EA can lower the per device rate but locks the quantity, so unused licenses become shelfware you cannot drop mid term. Price the EA against a la carte over the full term, not just at signing.
When a Meraki license expires, the dashboard enters a grace period and then, if unresolved, devices stop functioning. That operational consequence is the vendor's strongest lever, so never let a renewal slip close to expiry.
Cut the renewal by renewing early, right tiering devices, and aligning Meraki with the wider Cisco relationship only where it genuinely lowers cost.
If you run other Cisco software, aligning Meraki renewal timing with the broader agreement consolidates leverage. Confirm what each line includes in the order document, and avoid committing quantities you cannot adjust as the estate changes.
Cisco Meraki sells hardware coupled to a cloud subscription. Each device only operates while it carries a valid license, and an expired license eventually causes the device to stop passing traffic after a grace period.
Per device licensing tracks each device's own term and tier, giving granular control. Co termination aligns every license to one shared expiry date, which is simpler to renew but means paying to align new devices added mid term.
The Meraki dashboard enters a grace period when a license expires, and if the license is not renewed the affected devices eventually stop functioning. This operational consequence is why renewal timing carries real risk.
It depends on your device refresh pattern. For estates that add devices steadily through the year, per device licensing often costs less because co termination forces partial period payments to align each new device to the shared expiry date.
Meraki commonly offers Enterprise and Advanced tiers. Enterprise covers core management and routing at a lower cost, while Advanced adds security and analytics features at a higher per device cost. Right tiering devices is a key saving.
An Enterprise Agreement can lower the per device rate but locks the quantity, turning unused licenses into shelfware you cannot drop mid term. Price the EA against a la carte across the full term before committing.
Renew early to remove shutdown pressure, right tier each device to the lowest tier it needs, drop licenses on idle or decommissioned devices, and test an Enterprise Agreement against a la carte pricing over the full term.
Under per device licensing you can manage each device's term independently, so individual devices can lapse or change tier. Under co termination this is harder because all licenses share one expiry date.
Meraki license models, co termination math, expiry risk, and the renewal levers that cut an over licensed Cisco estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.