How Cisco Meraki Co-Term and Subscription Licensing Work
Short answer: Meraki has three licensing models. Co-term puts every claimed licence into one organisation-wide expiration date (a weighted average). Subscription binds licences to networks, uses a fixed start and end date, and keeps traffic flowing in Amber Mode if you lapse. Per-device licensing (PDL) still exists only for orgs already on it — new conversions are closed. You cannot mix the three models in one organisation. Cisco’s current guidance is to plan a move to Subscription as co-term approaches expiry, not to assume co-term is the forever default.
Related pages: Cisco Meraki · How to choose the right Cisco / Meraki access point · Technical refresh in a co-term organisation · Knowledge base
Licensing rules change. Preview every claim in dashboard. Confirm the current SKU list and term card with Cisco or your partner before you buy.
| Model | How dates work | Bound to | If you lapse | Who can still start on it |
|---|---|---|---|---|
| Co-termination (co-term) | One dynamic date for the whole organisation | Organisation (licence limit by family) | 30-day grace, then organisation shutdown (devices stop passing client traffic) | Default for a new org until a subscription key is claimed |
| Subscription | Fixed start / end per subscription | One or more networks | Amber Mode: management locks; client traffic keeps flowing | New and renewing customers (claim a subscription key) |
| Per-device (PDL) | Date per assigned device | Device (or some network products) | Device-level shutdown | Legacy only. New conversions to PDL are not accepted |
A new dashboard organisation still defaults to co-term. It becomes a subscription organisation when you claim a subscription key — and only if no active co-term or PDL keys remain.
Cisco Enterprise Agreement (EA) co-term is a contract alignment (add-ons lined up to the EA end date, True Forward). It is not the Meraki dashboard average. Do not run EA math through License Calculator.
How does Meraki co-term licensing work?
Every licence claimed into a co-term organisation is folded into one expiration date. Individual keys do not keep their own end dates after they are averaged in.
Published co-term terms are 1, 3, 5, 7 and 10 years. Meraki does not sell prorated co-term keys. Exact cards still depend on the product family.
How is the co-term date calculated?
Each licence contributes time × quantity (AP-months, MX-months).
That pool is divided by the licence limit (how many devices that family is allowed), not by how many are powered on.
The result is the common date.
Cisco’s example: 10 APs on 1-year licences; four months later you add 6 APs on new 1-year licences. Unused overlap is 4 months × 6 APs = 24 AP-months, spread across 16 APs = 1.5 months added to the common date.
That example is official. It is also incomplete for a mixed estate. The engine Cisco documents as “the science” weights each family by a base price (incremental dollar-days ÷ daily usage rate), uses seconds internally, and enforces at 09:00 Pacific on the rounded day. An MX Advanced day is not equal to an MR Enterprise day. Always preview in Organization → Configure → License info and the License Calculator.
Adding licences recalculates the date. It can lengthen remaining time or pull the date forward if you drop a large pile of short keys into a long-dated org.
Removing hardware does not add days. The date follows licence limit, not online count.
What is the difference between “license more devices” and “renew”?
This is the usual quoting mistake.
| Claim action in dashboard | What it does |
|---|---|
| License more devices | Raises the licence limit. Spreads the new key’s time across the org. Use this when you are adding APs / MX / MS mid-term. |
| Renew my Dashboard license | Invalidates prior limit counts and resets the org to the devices on that renewal key. Use this for a true whole-org renewal. |
Co-term organisations use one feature tier per product family. You do not mix Enterprise and Advanced wireless inside the same co-term org the way subscription lets you mix tiers by network.
What happens when a co-term org is out of compliance?
Over-limit or past the date starts a 30-day grace. If you do not return to compliance, Meraki shuts the organisation down. Devices stop passing client traffic; they still talk to the cloud so the org can recover when licences are fixed. That is not Amber Mode.
How does Meraki subscription licensing work?
Subscription is the model Cisco now describes as the flexible, long-term path. Licences live in a subscription. You bind networks to that subscription. Devices in a bound network consume seats from it.
A network binds to one subscription at a time. Several networks can share one subscription.
What do you actually buy?
Order a Meraki Subscription (MERAKI-SUB) or Cisco Networking Subscription (CISCO-NETWORK-SUB) with quantities and tiers for each family (wireless / CW, MS, MX, MV, and the rest of the current list). Subscription SKUs are hardware-agnostic inside a family — one wireless subscription SKU can cover MR and CW-917x class APs in that family, which is why a hardware refresh often does not need a new licence SKU.
Claim the subscription key once. Later additions and upgrades that Cisco processes against that subscription update dashboard without another key claim.
What is Amber Mode?
If the subscription expires or the bound network is over its seat count, dashboard management for the affected scope is restricted. Client traffic continues. That is the point of Subscription versus co-term. Co-term has no Amber Mode.
Enforcement is scoped to the non-compliant subscription / devices, not an automatic whole-org brick.
How do feature tiers work on subscription?
Subscription uses a two-tier pattern for most families. Names on the page are usually Essentials and Advantage (co-term pages still say Enterprise / Advanced). You can put different tiers on different networks in the same organisation — headquarters on Advantage, a small branch on Essentials — which co-term cannot do for the same family.
How do you add, upgrade and renew a subscription?
Add seats mid-term without moving the subscription end date.
Upgrade a tier on a network (processed as a subscription change; dashboard updates after the partner / Cisco change, no second claim).
Automatic renewal: partner-enabled, typically same terms for a further year after end date. Confirm the current lead-time rule with the partner (commonly set well before expiry).
Manual renewal: change quantities, tiers, payment cadence or duration inside what Cisco will accept.
Dashboard warnings can appear well before expiry (subscription materials cite up to 120 days). Do not rely on email alone.
Payment cadence on subscription can be monthly, quarterly, annual or prepaid — subject to the current Cisco offer, not to the old co-term prepaid-only habit.
| Rule | Detail |
|---|---|
| Active co-term or PDL keys | Must expire first. You cannot convert a live co-term org by stacking a subscription key on top. |
| Same organisation | You do not need a new org. Claim the subscription key in the existing org once legacy keys are gone. |
| Timing | Start planning 9 to 6 months before the co-term date. |
| Scope | Org-wide change. Documented as not reversible back to co-term. |
| After the claim | Bind each network to the subscription. Unbound networks are not licensed. |
| SKU mapping | Use dashboard’s subscription recommendation from deployed devices. Do not copy an old co-term key 1:1. |
You need at least one subscription per organisation. One subscription does not cover a second dashboard org.
| Situation | Practical choice |
|---|---|
| New Meraki / CW deploy in 2026 | Start on Subscription unless there is a documented reason to stay on co-term |
| Co-term date 6–9 months out | Size subscription SKUs now; convert when the co-term keys expire |
| Stable single-site co-term, happy with one date | Co-term still works. Know the shutdown risk and the Renew vs Add-devices trap |
| Many networks, different security / wireless tiers | Subscription |
| Already on PDL | Stay until expiry, then Subscription. You cannot convert to PDL |
| Hardware refresh MR → CW-917x | Subscription SKUs are family-based; still count seats. Co-term still needs a wireless licence on the limit |
| “Just add six APs” mid co-term | Model the new date in License Calculator before you claim. Longer terms on the add protect the date; a stack of 1-year keys can shorten it |
FAQ
Are licences tied to the access-point serial?
Not under co-term. The org holds a wireless licence limit. Under subscription, seats sit on the subscription and are consumed by devices in bound networks. PDL is the model that assigned a key to a serial — and you cannot newly convert to it.
Can we keep co-term forever?
Yes, Cisco still sells and renews co-term. Their own co-term FAQ now tells customers to consider Subscription before the next renewal. The conversion still requires the old keys to expire first.
Does buying longer co-term keys when we add APs help?
Usually, because you are adding more remaining time into the average. Always run the calculator. Short keys on a large add can move the common date the wrong way.
Send the current License info screenshot (or subscription page), device count by family, and whether this is a mid-term add or a renewal. Megatron Technology will model co-term impact or a subscription seat list for a Singapore org — including the claim type so the date does not reset by accident.
Request a licence review: www.megatron.com.sg/ciscomeraki