Meraki Co-Term vs Per-Device Licensing Explained

Co-termination and per-device licensing are the two ways a Meraki organization's licenses can be structured, and they answer the same question differently: when does each license expire? Co-termination pools every license in the organization to one shared expiration date, so adding a device mid-term prorates its license to match the existing date and the whole org renews together, once. Per-device licensing (PDL) gives each device its own independent license with its own start and end date, so adding or removing a device doesn't touch anyone else's term. Co-term is simpler to administer for a stable fleet; per-device licensing is more precise for a fleet that grows, shrinks, or refreshes in pieces.

At a glance

An organization is generally set up as one model or the other, not a mix of both at once, and switching between them is an operational decision worth planning rather than defaulting into. Confirm current platform and product-line availability for per-device licensing in a validated quote, since Cisco has expanded which product lines support it over time.

How co-termination actually renews

Co-termination is Meraki's original and still-default licensing model. Every license purchased for the organization is pooled to a single shared expiration date, regardless of when each device was actually added. That single date is what makes annual budgeting simple: one renewal event covers the entire organization, rather than a rolling calendar of individual device expirations to track.

The catch is proration. When a device is added mid-term, its license isn't sold for a full fresh term — it's prorated to match whatever time remains until the org's existing co-term date. That's financially fair, but it means a single new access point purchased ten months into a three-year term can look oddly priced if you're not accounting for the calendar it's being aligned to. It also means removing a device doesn't give you back unused time on its license; that capacity is effectively stranded until the org-wide renewal.

A concrete case makes the mechanics clearer. Picture an organization on a three-year co-term license that started in January. If a new access point is added that October, nine months in, its license isn't sold as a fresh three-year term — it's prorated to expire alongside every other license in the organization, in roughly twenty-seven months rather than thirty-six. The invoice reflects that shorter period, which is fair, but it's also why a single new access point can land on a quote at a price that doesn't match a simple per-device rate card, and why anyone unfamiliar with co-termination sometimes flags it as a pricing error when it isn't one.

How per-device licensing works differently

Per-device licensing assigns each device its own license, with its own start date, term, and expiration, independent of every other device in the organization. Add a device and it gets a clean, full-term license on the date it's added — no proration against someone else's calendar. Remove a device and its license simply ends; there's no shared date to disturb and no stranded capacity sitting on other devices' licenses.

The tradeoff is administrative surface area. Instead of one renewal event, an organization on per-device licensing is tracking as many license timelines as it has devices — which is exactly the granularity that a large, frequently-changing, or multi-team fleet actually wants, but it does mean the license roster needs real tracking discipline rather than a single date on a calendar. Confirm which product lines support per-device licensing for your specific Meraki deployment in a validated quote, since availability by platform has expanded over time and continues to evolve.

The honest tradeoff, and the one-way door

Neither model is objectively better; they trade simplicity for precision in opposite directions. Co-termination is easier to budget and renew as a single annual event, at the cost of proration math that can be confusing when the fleet changes mid-term. Per-device licensing is precise and transparent per device, at the cost of tracking many independent license timelines instead of one. A small, stable fleet that rarely changes gets little benefit from the added precision of per-device licensing. A fleet that's constantly adding, swapping, or retiring devices — an MSP managing multiple client sites, or an organization mid-refresh — usually finds the co-term proration friction outweighs its simplicity.

One more thing worth planning around: moving an organization from one licensing model to the other is an operational change, not a toggle, and migration policy can change over time — confirm the current process and whether it's reversible before switching either direction. Treat the choice as a real decision made once, not something to default into and revisit casually.

Which should you choose?

• Stable fleet that rarely adds or removes devices, and you want one predictable annual renewal: co-termination is the simpler choice.
• Fleet with a rolling refresh cycle, frequent device swaps, or several teams independently adding hardware: per-device licensing avoids proration confusion and stranded license time.
• MSP or multi-client environment managing devices on different timelines: per-device licensing keeps each client's or site's licensing independent and easy to audit.
• Mid-refresh organization retiring old hardware and adding new hardware on different schedules: per-device licensing lets old and new coexist cleanly without disturbing a shared date.
• Small, single-site deployment with a long, stable planning horizon: co-termination's single renewal date is genuinely less overhead.