Both are Cisco. One is a CLI switch you buy once and configure yourself; the other is a cloud-managed box you rent access to. The marketing won't tell you the trade-offs that actually matter to a small business — the licensing math, the vendor lock-in, and what happens the day the subscription lapses. So we will.
This is a decision we help clients make constantly, and the honest version isn't in either product's brochure. Cisco Catalyst is the traditional line — the switches this whole series has configured. You buy the hardware, own it outright, and manage it by CLI (or a controller you run). Cisco Meraki is cloud-first — the switch phones home to Cisco's dashboard, you manage everything through a slick web UI from anywhere, and you pay a per-device annual licence for the privilege. Crucially: if that licence lapses, a Meraki switch stops passing traffic. Not "loses features" — stops working.
Neither is "better." They're different deals, and the right one depends on who's going to run the network, how many sites there are, and whether you'd rather pay once or pay forever for convenience. As a consultancy that would happily install either, we have no dog in the fight — so here's the comparison we actually give clients, including the parts vendors gloss over.
01
Almost everything else flows from a single difference: own-and-configure versus rent-and-click.
| Catalyst | Meraki | |
|---|---|---|
| Management | CLI / on-prem controller | Cloud dashboard (web, from anywhere) |
| Cost model | Buy once, own forever | Buy hardware + annual licence per device |
| If you stop paying | Keeps working indefinitely | Switch stops forwarding traffic |
| Learning curve | Steep (IOS CLI) | Gentle (point-and-click) |
| Multi-site visibility | DIY (monitoring you build) | Built-in, excellent, single pane |
| Offline / no-internet | Fully functional | Runs, but no management; needs cloud to configure |
| Deep/custom config | Total control | What the dashboard exposes — no more |
| Data control | Stays on-site | Metadata flows to Cisco's cloud |
A Meraki switch without a valid licence stops passing traffic after a grace period — this is by design, not a bug. So the "cheap" Meraki quote is only the first year; budget the licence for the entire service life of the hardware (typically 5–10 years), because you're not buying a switch, you're renting one that happens to sit in your rack. We've seen businesses blindsided when a 3-year co-term licence expired and the network went dark. It's a perfectly fine model if you go in knowing it — the failure is buying Meraki on the hardware price and discovering the subscription later.
02
Cloud management genuinely earns its subscription in specific situations. Be honest about whether yours is one of them.
Meraki shines when you don't have (or don't want) in-house network expertise and value the dashboard's simplicity — a manager can see every site's health, add a VLAN, or block a device from a phone. It's excellent for many small identical sites: a chain of shops, a group of small hotels, franchises — zero-touch provisioning ships a switch to a location and it configures itself from the cloud. And the built-in multi-site visibility, alerting, and one-click firmware replace a monitoring stack you'd otherwise have to build (the observability we set up by hand on Catalyst).
Meraki's pitch isn't better switching — the silicon is comparable. It's that it turns network operations into a subscription you outsource to Cisco's dashboard. For an organization whose core competency isn't IT and who'd rather pay a predictable annual fee than employ or retain a network engineer, that's a rational trade. The subscription is buying simplicity and remote manageability, and for the right buyer that's worth real money. The mistake is buying it for a scenario where you're paying forever for convenience you don't actually use.
03
Ownership, control, and no recurring tax. For a single site with someone competent behind it, this is usually the better deal.
Catalyst wins on total cost of ownership for a stable site: buy quality switches once and they serve for a decade with no licence renewals. It wins when you need configuration depth the dashboard won't expose — the granular QoS, firewall, and routing this series covered are all fully in your hands. It wins where the network must run regardless of internet or a vendor's cloud — a Catalyst doesn't care if Cisco's dashboard is down or your WAN is out; a clinic or a production floor can't have switching depend on a cloud round-trip. And it wins on data sovereignty: nothing about your network leaves the building.
To be fair to Meraki: modern Catalyst isn't entirely licence-free either. DNA/Smart Licensing tiers (Essentials/Advantage) gate some advanced features, and support contracts (SmartNet) cost money. But the crucial difference is that a Catalyst keeps forwarding traffic whether or not a licence is current — you lose access to certain features or TAC support, not the network itself. The base switching, VLANs, routing, and security in this series work on the perpetual base. "Licence lapses" on Catalyst means "no new advanced features"; on Meraki it means "the switch turns off." That asymmetry is the whole ballgame.
04
The Cisco-vs-Cisco framing has a blind spot: for many SMBs, neither is the value pick. We'd be doing you a disservice not to say so.
For a lot of the businesses we serve, a MikroTik or a well-chosen alternative delivers the switching and routing they actually need at a fraction of the cost — no subscription, deep control, and (as this whole series' MikroTik↔Cisco mappings show) the same underlying concepts. The honest hierarchy for a typical Cretan SMB: MikroTik for best value with someone competent running it; Catalyst when you specifically want the Cisco ecosystem, its resale/support depth, or a client/insurer mandates it; Meraki when hands-off cloud management across sites is worth a permanent subscription.
| If your priority is… | Lean toward |
|---|---|
| Lowest total cost, deep control, in-house skill | MikroTik (or Catalyst) |
| Cisco ecosystem, own-it, single site, config depth | Catalyst |
| Zero-touch, many sites, no IT staff, remote mgmt | Meraki |
| Must work with no internet / on-prem only | Catalyst or MikroTik |
| Predictable opex over capex, outsource ops | Meraki |
05
Skip the feature checklists. One question sorts most buyers correctly.
"Who is going to run this network, and do they want to type commands or click a dashboard — and are you willing to pay every year for the dashboard?"
If the answer is "nobody technical, and yes we'll pay for simple" → Meraki. If it's "we have someone (us, or you) who's comfortable in a CLI and we'd rather own it" → Catalyst or MikroTik. Everything else — port counts, PoE budget, 1G vs 10G uplinks, stacking — is spec-sheet work any integrator does after the model is chosen. The model is a business decision about operations and cash flow, not a technical one, which is exactly why the vendor demos steer you past it.
Takeaways
NOCTIS gives vendor-neutral advice — Catalyst, Meraki, or MikroTik — based on who'll run it and what it should cost over five years, not on whose margin is biggest. We'll spec, install, and document whichever genuinely fits.
Book a Discovery Call →