Meraki licensing: tiers, co termination and renewals. How to stop paying Advanced prices for Enterprise sites.

Meraki is licensed per device, per tier and per term, and the tier is the line you control most. Match each site to the features it uses, then choose the term model that fits how the network grows.

How does Meraki licensing work in 2026?

Every Meraki device runs on a subscription, with no perpetual right to fall back on when it ends. Each device needs active licensing, priced by device class, feature tier and term. Cisco publishes the rules in its Meraki licensing documentation, and the tiers sit on the Meraki product pages.

Per device, per tier, per term

• Per device. You license each access point, switch and security appliance individually. Every unit needs its own active license, or a place inside the organization's license limit.
• Per tier. Enterprise or Advanced on access points. Enterprise, Advanced Security or Secure SD-WAN Plus on MX appliances. There is a real gap in features and in price between them.
• Per term. Most lines offer 1, 3, 5, 7 or 10 year terms. A few newer ones, such as MS130 Advanced, stop at 5 years.

Which licensing model is your organization on?

Check this first, because the model decides how dates, tiers and reclaim work. Cisco now recommends subscription licensing, and per device licensing is closed to new adopters wherever subscription is sold. Many existing customers still sit on co termination.

What happens when a Meraki license expires?

On co termination and per device licensing, Meraki gives a 30 day grace period and then disables what is unlicensed. On co termination that means every network, because one date covers every device. Nothing reverts to a free basic mode, so a lapsed renewal is an availability problem before it is a billing one.

Subscription licensing softens this. Amber Mode keeps devices forwarding traffic after a lapse, but you lose management until the subscription is current. The contract terms behind all three models sit in the Cisco end user license agreement.

Enterprise or Advanced: which Meraki tier fits each site?

Enterprise fits most general purpose sites. Advanced fits the sites that use its added security, analytics or SD WAN features, and many sites never touch them. The tier is the largest line you control in a Meraki renewal, and it drifts upward because an upgrade is decided once and then renewed by default.

Map features to sites before you map budget

Buy Advanced only where a site uses what Advanced adds. On MX appliances, Advanced Security is the tier that switches on the following:

• Intrusion detection and prevention (IDS/IPS)
• Content filtering powered by Talos intelligence
• Cisco Advanced Malware Protection (AMP) and Secure Malware Analytics integration
• Geography based firewall rules
• Umbrella DNS integration and the ThousandEyes agent

Secure SD-WAN Plus adds WAN, VoIP and web app health plus smart breakout. MR Advanced adds AI radio resource management, Adaptive Policy and Cisco Spaces Advantage. A site that runs none of these pays for features it never switched on.

Why one organization cannot mix editions on co termination

Under co termination, Cisco requires one MX edition and one MR edition across the whole organization. You cannot run 20 appliances on Enterprise and 5 on Advanced Security in one organization, and per device licensing applies the same rule to MX. A few sites that need Advanced lift every site.

A mixed deployment of Enterprise and Advanced is usually cheaper than a uniform Advanced buy, and it is the same network. To get there, split sites into separate dashboard organizations by tier, or move to subscription licensing, where one organization can hold subscriptions at different tiers. Price both routes early.

How tier inflation creeps into a renewal

Tiers ratchet up and rarely come back down. A site moved to Advanced for a project that ended stays on Advanced at every renewal unless someone pulls the feature usage data and challenges it. The partner renews what the dashboard shows was bought, which says little about what each site uses.

What have 25 to 35 Cisco and Meraki reviews shown us?

The finding that came back most often was that sites bought the Advanced tier and used Enterprise features. Across roughly 25 to 35 Cisco and Meraki reviews I led between 2024 and 2025, three patterns recurred.

• Tier inflation. Between 30 and 50 percent of devices sat on Advanced licenses while using only Enterprise capability. The median across the reviews was 38 percent of devices over tiered.
• Co termination waste. Aligning new devices to a single shared date added 5 to 15 percent in unused months across a refresh.
• Stranded licenses. Devices retired mid term left paid licenses behind, and those licenses were never reclaimed against new hardware.

Stranded licenses were the hardest to spot, since they never show on a quote as a separate line. Matching the tier to real feature usage and choosing the right term model cut renewals by 19 percent on average. That saving follows from the over tiering figure, and none of it depended on Cisco conceding discount.

A device by device tier review at refresh time recovers more on a Meraki renewal than any single discount the partner can offer.

How does Meraki co termination change what you pay?

Co termination gives every license in the organization one shared expiry date. It simplifies renewal and changes the cost of growth. When you add licenses, Meraki recalculates the date as a weighted average of all license time across the license limit, so every purchase shifts the date for every device.

In practice, a device added mid cycle has to be brought up to the shared date. Licenses come in whole year terms that rarely match the time left, so a buyer who wants to keep the date usually takes the longer term, and the surplus becomes time prepaid across the organization.

A worked example of the co termination date

Say you run 200 access points on co termination with 730 days left, and a new building adds 40 more. Today the organization holds 146,000 license days (200 times 730). Meraki spreads the combined total across all 240 devices.

Meraki sells no 2 year license, so no single term holds the date, but the split in the middle row does. Ask the partner to quote it. Any extra time is pooled, and it becomes a cost when the organization shrinks, splits or converts to subscription before that prepaid tail is used.

When is per device term the cheaper answer?

Co termination gives one date and a simple renewal, which suits a stable network. If you add devices steadily through the year, a separate clock per device or per subscription avoids paying to align each new unit, and no months are bought only to align. The trade is more renewal dates, which a simple tracker handles.

We work through the comparison with numbers in the co termination cost comparison, and the wider Cisco picture sits in the Cisco knowledge hub.

How do you check your own Meraki licensing position?

Start in the Meraki dashboard, which holds the license limit, the device count and each network's feature settings. Pull these views before any partner meeting.

• License info page. Under Organization, it shows the co termination date and the license limit per device type against devices in use. On per device organizations it lists each license, its device and its end date.
• Inventory. Compare devices in use with devices claimed but unused. Retired units still in inventory, or still holding a license, are where stranded spend hides.
• Feature settings by network. For every MX on Advanced Security, open the Threat protection and Content filtering pages. If IDS/IPS, AMP and category blocking are all off, that site is an Enterprise site on an Advanced bill.
• Dashboard API. Beyond a few dozen networks, the getOrganizationLicensesOverview and getOrganizationInventoryDevices calls export the same data into a sheet you can sort by site.

How do you cut the cost of a Meraki renewal?

Fix scope before you discuss price. Bring a device inventory, feature usage by site, and a costed comparison of the term models, then work through four changes.

• Right tier each site. Downgrade Advanced sites that use only Enterprise features, splitting organizations or moving to subscription where co termination forces one edition.
• Reclaim stranded licenses. Move them off retired devices onto live ones where the model allows, before buying new licenses with new hardware.
• Pick the right term model. Co termination for stable networks, separate clocks for growth.
• Plan the expiry. Settle everything early so the grace period is never used against you.

On co termination, the renewal key itself resets the count. When you apply a renewal, the organization's license limit changes to match the device count on that key, so a renewal sized to live devices drops retired ones for good.

Why we advise against Advanced everywhere on one date

The standard reseller advice is to put everything on co termination and buy Advanced everywhere for simplicity. We disagree. In roughly half the Meraki deployments we reviewed in 2024 and 2025, uniform Advanced licensing plus co termination on a growing network added 15 to 30 percent of avoidable cost. Sites paid for unused features and unused months.

Match the tier to each site's measured feature usage instead, and use co termination only where the device count is stable. Both halves can be measured before the quote arrives.

How to avoid the expiry date trap

Cisco and its partners have the most bargaining power in the final weeks before expiry, because the alternative is a device that stops working. Start early, confirm the inventory, and settle tier and term before the clock does it for you.

Where Meraki sits inside a wider Cisco agreement is a separate question, covered in the enterprise agreement inclusion brief, and the negotiation itself in Cisco negotiation services.

What the partner will say, and how to answer

• "Co termination needs one edition, so Advanced everywhere is simplest." True for MX and MR within one organization. Ask for a quote with the Enterprise sites in their own organization, and one on subscription licensing with tiers set per subscription.
• "The new switches and access points come with licenses on the quote." Ask for the license info page first. If retired units freed room in the license limit, the new hardware may need fewer licenses than quoted.
• "Take 3 year terms on the new devices so your renewal date does not come forward." Ask for the recalculated co termination date under 1 year and 3 year options side by side, then decide on cash and timing.
• "Your licenses lapse in two weeks, so we need the order now." The 30 day grace period is a safety net for mistakes. Starting 90 days out means you never have to hear this line.

Contract terms to ask for

• Price hold for additions. Fix the price per license and tier for devices added during the term, so growth is bought at the renewal discount.
• Dates on every quote. Each co termination quote should state the organization's date before and after the claim.
• Renewal sized to live devices. The renewal key should match the inventory count you supply, which is what drops retired units from the limit.
• A tier schedule. An appendix listing each organization or subscription and its tier, so an upgrade needs a signed change.
• Written reclaim terms. Confirmation of how licenses on retired or replaced devices transfer, including between organizations.

What to do next

1. Build the inventory. List every Meraki device, its tier, its licensing model and its expiry date, because the tier conversation cannot start without it.
2. Pull feature usage by site. Flag every Advanced device that uses only Enterprise features, network by network, from the Threat protection and Content filtering settings.
3. Find stranded licenses. Identify retired devices still carrying paid licenses or license limit, and check the reclaim options for your model.
4. Model the term options. Compare co termination against per device or subscription terms on your real deployment pattern, using the weighted average date for each purchase.
5. Open the renewal early. Start at least 90 days before the earliest expiry. The Cisco licensing experts in our Cisco practice run the tier review before the quote arrives.

Frequently asked questions