Peplink 101 — the platform
Peplink is three layers that work as one: hardware (the routers, switches and APs, all speaking the same core protocol), SpeedFusion (the engine that bonds links), and InControl 2 (the cloud that manages one device or ten thousand identically). Most field confusion comes from blurring these — naming the layer tells you where to look.
The Peplink stack, a mental model
Every router is WAN links (cellular, wired, Wi-Fi-as-WAN, satellite) → a routing/SD-WAN core → a LAN (ports, VLANs, Wi-Fi). Think in those three layers and every model, from a pocket BR1 to a maritime SDX, reads the same way. A Peplink device is its own router, firewall, gateway and SD-WAN endpoint in one box.
InControl 2, FusionHub & Zero-Touch
InControl 2 configures, monitors and updates the whole fleet without logging into any device. FusionHub is the virtual SpeedFusion endpoint in your cloud/DC that branch and mobile tunnels terminate into. Zero-Touch lets a router ship straight to site and provision itself — one VoIP provider configured 100 BR1 Minis in about an hour this way.
Topologies & care plans
Hub-and-spoke, mesh and dual-hub topologies let you design for both performance and survivability. Care plans wrap the hardware: the first year of SD-WAN, cloud management and warranty is included, renewable in 1–4 year increments — it’s how firmware, cloud and SpeedFusion stay current.
Own your network
Everyone else sells a subscription — required licenses, cloud fees, hardware that dies with the warranty. Peplink hardware is bought once and it lasts: it keeps bonding and routing with or without an active warranty, and with or without the cloud. You own the box, the connection, and your uptime.
The one rule to memorize
Add every new WAN to SpeedFusion — a newly added interface is default-off in the tunnel. A real West Networks call: a site’s phones were dead for a full day after the wired link went out. The team changed the phone system for hours; the actual fix took sixty seconds. The VoIP rode a SpeedFusion tunnel, the wired link had failed, and the 5G backup had been added to the router but never enrolled in the tunnel — so when the wire dropped, the tunnel had no member and went down. A symptom is not the source: fix the tunnel, not the phones, and add your new WANs to SpeedFusion, every time.