Cloud-managed security and SD-WAN appliances from branch to campus

Cisco documents the MX as an enterprise security and SD-WAN appliance built for distributed deployments that need remote administration, with AutoVPN used to build site-to-site connectivity without hand-configuring tunnels. Every model in this family is managed from the same Meraki dashboard, so the difference between them is capacity and uplink options rather than feature set or management model.

The range HTS carries splits into three practical tiers. The MX67 and MX68 are small-branch appliances, and each is also offered in variants with radios built in: the MX67W and MX68W add 802.11ac Wi-Fi, while the MX67C and MX68CW add a built-in LTE modem so a site can come up on cellular alone or fail over to it. Those cellular models are sold in separate North America and worldwide forms because the modem bands differ by region, and picking the wrong one is the most common ordering mistake in this family. The MX75, MX85, MX95, and MX105 cover the mid-range, where a growing site needs more throughput and more physical WAN ports than a branch box provides. The MX250 and MX450 sit at the top of the range for campus cores, concentrator roles, and data-centre edges.

Sizing an MX is not a port count exercise. Cisco publishes recommended client counts and throughput figures per model, and those assume a particular mix of enabled security services — turning on more inspection lowers effective throughput. HTS sizes from your real user count, WAN circuits, VPN topology, and which security features you actually intend to run, then quotes the model that leaves headroom. Licensing is a separate decision: Meraki licences are subscription terms that must line up with your existing dashboard organisation, so we confirm your current expiry date before quoting rather than assuming a fresh term.