Catalyst vs Meraki: the Hardware Question Has Dissolved. What's Left Is What Happens When You Stop Paying.
Written and maintained by Haink's network infrastructure team · Verified against Cisco and Meraki documentation, 23 August 2026 · authorized-channel, serial-verified
This used to be a choice between two product lines. It is not any more. Catalyst 9300, 9300X and 9300L switches are all available in Meraki-managed -M variants, and Cisco states that Catalyst 9300 switches "can be ordered directly or migrated to the Meraki software option," after which "all configuration and monitoring is performed natively in the dashboard." The same silicon, managed two ways.
So the decision has moved. It is no longer about which switch. It is about which management model you want, and — much more consequentially — which licensing failure mode you can live with. Because on that point the two are not similar. They are opposite.
What happens when the licence lapses
| Catalyst (DNA or Catalyst subscription) | Meraki | |
|---|---|---|
| Immediately | Nothing — the perpetual Network Stack licence has no expiry | 30-day grace period. Meraki: "During the grace period, network clients will not see a difference" |
| After that | Switch keeps forwarding with all Network Stack features intact. You lose Catalyst Center automation and analytics | The network "will be shut down until proper licensing is applied to the organization" |
| Out of compliance | Not a technical state | Meraki: hardware "will be non-operational… your network products will no longer allow traffic to pass to the Internet" |
| Formal fallback | Deactivate the add-on licence and reload; the switch runs on its perpetual tier | None. There is no unlicensed mode |
Read those two right-hand cells against each other, because this is the whole decision compressed into two sentences from the vendors' own documentation. A Catalyst switch whose subscription lapsed is a switch that has lost features. A Meraki switch whose licence lapsed, after the grace period, is a switch that has stopped.
Meraki is explicit that this is by design: "every Meraki hardware component requires a cloud license to be managed." Only devices actively in a network consume a licence — stock sitting in inventory does not — but there is no configuration in which a deployed Meraki device runs without one.
Why this matters more than it sounds
Not because anyone plans to stop paying. Because of what it means for risk, and for the shape of the relationship:
- A procurement delay becomes an outage. A renewal stuck in a purchasing cycle, a budget freeze, a change of finance system — on Catalyst these are annoying. On Meraki they run against a 30-day clock with the network on the other side of it.
- The estate has no residual value without the subscription. Meraki hardware without a licence is not reduced-function hardware; it is non-operational hardware.
- It changes the negotiation. At renewal, one vendor is discussing features and the other is discussing continuity. Those are not the same conversation, and both sides know it.
None of which makes Meraki wrong. It makes the model explicit — and it deserves to be a conscious decision rather than something discovered at year three.
What you actually get for it
The Meraki model buys something real, and understating it would be as dishonest as ignoring the licensing question.
| Meraki is stronger on | Catalyst is stronger on |
|---|---|
| Time to deploy a new site — claim the device, it configures from a template | Depth of configuration: full CLI, every knob IOS-XE exposes |
| Operating a large number of small sites with a small team | Air-gapped and restricted networks — no cloud dependency at all |
| Consistency: one dashboard for switching, wireless, security | Complex routing, fabric roles, and anything requiring feature-level control |
| Staff who are not network specialists | Estates with in-house network engineering already invested in IOS-XE |
| Visibility without building a monitoring stack | Regulated environments where the management plane must stay on-premises |
The clearest way to put the trade: Meraki removes work and removes options. If your constraint is operational capacity — thirty branches and two engineers — that trade is obviously correct. If your constraint is what the network must be able to do, it is obviously not.
The access points are already dual-mode
On wireless the convergence is furthest along. The Wi-Fi 7 access points — CW9171, CW9172, CW9174, CW9176, CW9178 — operate either with a Catalyst 9800 controller or under the Meraki cloud platform. The same part number, two management models.
That makes the wireless refresh a natural decision point. If Wi-Fi 6 access points are being replaced anyway — and after the 2026 end-of-sale many are, see the Wi-Fi 6 guide — the hardware does not force the management choice. Which is worth knowing before anyone claims a migration requires new access points.
Cisco Networking Subscription blurs it further
The newest Cisco licensing model, Cisco Networking Subscription, applies to the C9350, C9550 and C9610 Smart Switches, Wi-Fi 7 access points and 9800 controllers — and it can be managed through either the Meraki dashboard or Cisco's on-premises Smart Software Manager. On the C9350 and C9550, Cisco supports both Networking Subscription licences and Meraki Classic licensing; the C9610 supports only the Networking Subscription.
The direction of travel is a single hardware line with a management choice at the top. It does not change the licensing failure mode question below, which still resolves to whether the device holds a perpetual entitlement or a cloud one. See the licensing guide for where each model applies.
How to decide
- Answer the licence-lapse question first. If a thirty-day gap in purchasing could take a site down, and that is unacceptable, the decision is made and the rest is detail.
- Check for a cloud constraint. Air-gapped sites, data-residency requirements and restricted markets remove Meraki from consideration regardless of preference.
- Count the engineers against the sites. This is the honest driver of most Meraki deployments and a perfectly good reason.
- List what you configure that a dashboard does not expose. If the list is empty, the CLI is not buying you anything.
- Price five years, not the hardware. Both are subscription models; the comparison is only meaningful over the full term with support included.
- Remember the hardware is often the same. A Catalyst 9300 in an
-Mvariant is a Catalyst 9300 — this is not a choice between silicon.
Want both priced properly?
Send the site list, port counts and how many people run the network. We quote the same estate both ways — Catalyst with subscription, Meraki with cloud licences — over five years with support included, so the comparison is real. Within one business day.
Frequently asked questions
What happens when a Meraki licence expires?
There is a 30-day grace period during which, in Meraki's words, "network clients will not see a difference." After that the network "will be shut down until proper licensing is applied to the organization." Meraki states that out-of-compliance hardware "will be non-operational" and "will no longer allow traffic to pass to the Internet."
What happens when a Catalyst subscription expires?
The switch keeps working with all Network Stack features intact, because that licence is perpetual. You lose the add-on features and Catalyst Center integration. The documented way to discontinue the add-on licence is to deactivate it and reload the switch.
Can Catalyst switches be managed from the Meraki dashboard?
Yes. Catalyst 9300, 9300X and 9300L are available in Meraki-managed -M variants, and Cisco states they can be ordered directly or migrated to the Meraki software option, with all configuration and monitoring performed natively in the dashboard.
Do Wi-Fi 7 access points work with both?
Yes. The CW9171, CW9172, CW9174, CW9176 and CW9178 operate either with a Catalyst 9800 controller or under the Meraki cloud platform.
Is Meraki suitable for an air-gapped network?
No. Management is cloud-based and every device requires a cloud licence to be managed. Where the management plane must stay on-premises, Catalyst with Smart Software Manager is the applicable option.
Which is cheaper?
It depends on the estate and the term, and any answer without both is guesswork. Both are subscription models, so the only meaningful comparison is total cost over the full term with support included — which is why we quote both when asked.
Related
- Cisco licensing explained — perpetual versus subscription, and where each model applies
- Is the DNA subscription mandatory? — the Catalyst side in detail
- Wi-Fi 6 AP end-of-sale — the refresh where this decision usually surfaces
- Catalyst 9200 versus 9300 · Reading a part number
- Enterprise switches · Wireless access points · Cisco stock and lead times
Sources
- Meraki — licensing FAQ (licence required per device, out-of-compliance behaviour)
- Meraki — co-termination licensing overview (30-day grace period, shutdown)
- Cisco — Catalyst 9300 data sheet (Meraki software option, -M variants)
- Cisco — Catalyst and DNA subscription FAQ (network does not stop working at expiry)
- Cisco — Networking Subscription data sheet