Meraki MS vs Catalyst Switches: Cloud-Managed or IOS XE?

Meraki ms vs catalyst used to be a clean binary, cloud dashboard or on-box CLI, and now it isn't, which is the most useful thing to understand before you buy either one. Meraki MS switches are licensed and managed entirely through the Meraki cloud dashboard: zero-touch provisioning, one pane of glass across switching, wireless, and security cameras, and no meaningful local configuration surface. Catalyst switches run IOS XE locally, giving you the deepest CLI, the richest feature set, and full function with no cloud dependency, managed through Catalyst Center, SNMP, or plain SSH. The twist: current Catalyst 9200/9300 software lets you onboard standard IOS XE hardware into the Meraki dashboard itself, in either a fully cloud-configured mode or a hybrid mode that keeps local IOS XE config authoritative while adding cloud visibility on top, and Cisco also sells the Catalyst 9300-M, factory-built for native Meraki management. The real choice is less about hardware and more about how much of your operation you want to live in the cloud.

At a glance

The MS390 and the Catalyst 9300-M share Catalyst 9300 hardware, but the two lines have very different operating philosophies. Here's the comparison before the nuance below.

Cloud dashboard vs CLI: the real operational trade-off

Meraki's dashboard is the product, not just a management add-on, every switch feature is designed to be configured, templated, and audited from one cloud console, and that discipline is why organizations running dozens or hundreds of small sites standardize on it. A junior technician can rack a Meraki switch, plug in the uplink, and have it claim its configuration automatically with zero local commands. Catalyst's IOS XE trades that simplicity for depth: granular QoS policy-maps, detailed routing protocol control, platform-specific hardware tuning, and troubleshooting commands that expose exactly what the ASIC is doing, none of which the Meraki dashboard surfaces to the same level even in cloud mode. Neither approach is wrong; they're optimized for different failure modes. Meraki optimizes for consistent configuration across many similar sites with limited local staff. Catalyst optimizes for deep control at a smaller number of complex sites where an experienced engineer needs to reach into the weeds.

Licensing: Meraki's mandatory subscription vs Catalyst's optional tiers

This is the sharpest philosophical difference between the two lines. A Meraki MS switch is inert without an active license, the subscription isn't an add-on, it's the operating requirement, licensed per device and tracked across your dashboard organization. Let a Meraki license lapse and the organization enters a 30-day grace period in which nothing changes for clients or admins; once that window closes, the organization is shut down, dashboard access is restricted to the license page, and the switches become non-operational until licensing is restored. A Catalyst switch ships with a perpetual Network Essentials or Network Advantage license that never expires; the Cisco DNA subscription bought alongside it (three, five, or seven years) gates the software-defined features, with DNA Advantage on top of Network Advantage required for SD-Access fabric roles and richer telemetry, but base switching keeps working after the subscription term ends. That distinction matters most in a budget crunch or a subscription-renewal gap: a Catalyst switch degrades gracefully in that scenario, and a Meraki switch does not.

The convergence: Catalyst hardware you can manage from the Meraki dashboard

Cisco has spent the last few software cycles narrowing the gap deliberately. Current Catalyst 9200, 9300, and 9500 switches on IOS XE 17.15.3 or later can be onboarded directly into the Meraki dashboard, either as configuration source: cloud, where the dashboard fully manages the device and adds a read-only Cloud CLI terminal for show commands and troubleshooting, or as configuration source: device, where the switch keeps its local IOS XE configuration as authoritative while the dashboard layers on centralized monitoring and a Cloud CLI that can also run configuration commands when the admin role allows it. On top of that, Cisco sells the Catalyst 9300-M, 9300L-M, and 9300X-M outright, the same Catalyst 9300 hardware, factory-positioned for native Meraki cloud management with their own Enterprise and Advanced license tiers in 1, 3, 5, 7, and 10 year terms. In practice this means you're no longer locked into choosing an OS at purchase time the way you were a few years ago: you can buy Catalyst hardware today and decide the management model, local IOS XE, hybrid, or full Meraki cloud, based on how the site actually operates.

SD-Access, deep QoS, and edge cases Meraki doesn't chase

Even with the convergence above, there's a ceiling on how far Meraki cloud management goes. SD-Access fabric roles, the most granular QoS and queuing tuning, complex multicast designs, and some platform-specific hardware features remain IOS XE-native capabilities that the Meraki dashboard doesn't expose in either cloud or hybrid mode. If your target architecture is a full SD-Access fabric with identity-based micro-segmentation across campus, plan on standard Catalyst hardware under Catalyst Center rather than Meraki-managed mode. If your requirement is consistent, auditable switching across many sites with a security-camera and wireless story bundled in, Meraki's dashboard-first approach, whether on classic MS hardware or a cloud-onboarded Catalyst, is built exactly for that job.

Offline and air-gapped environments

Meraki's architecture assumes a cloud connection is reachable at least periodically; sites that must run fully air-gapped or in classified/DoD enclaves are generally not a fit for Meraki-managed switching regardless of hardware. Standard Catalyst under local IOS XE, with Smart Licensing Using Policy's fully offline mode (usage reports saved to a file and uploaded from a connected machine), remains the correct choice whenever the network cannot phone home to a vendor cloud at all, not just intermittently.

Which should you choose?

Let site count and team depth decide, not hardware nostalgia:

• Many small or mid-size sites, lean IT staff, want one dashboard for switching, wireless, and cameras, Meraki MS.
• Large, complex campus needing SD-Access fabric, deep CLI control, or fully offline/air-gapped operation, standard Catalyst under Catalyst Center.
• Want Cisco hardware today with the option to move to Meraki cloud management later without a forklift, Catalyst 9200/9300 onboarded into cloud or hybrid mode, or the factory Catalyst 9300-M.
• Standardizing a mixed estate, decide site by site which management model fits, and keep license terms aligned so renewals don't fragment across the Smart Account.