Part One: The Peplink Stack, A Mental Model
The topic
Before any single feature makes sense, you need the shape of the whole system in your head. Peplink is not one product; it is three layers that work together.
At the bottom is the hardware: the routers (Balance, MAX, B-series, UBR, Transit), the switches, and the access points. Every Peplink router, regardless of size, speaks the same core protocol and is managed the same way, which is the entire point.
In the middle is SpeedFusion: Peplink’s patented SD-WAN protocol. It is the engine that turns multiple separate internet connections into one resilient virtual link. Everything people associate with Peplink, bonding, sub-second failover, WAN Smoothing, FEC, comes from SpeedFusion.
At the top is InControl 2: the cloud management platform. It is how you configure, monitor, and update one device or ten thousand without logging into any of them. Zero Touch Configuration, fleet-wide policy, eSIM management, and SpeedFusion orchestration all live here.
How it works on Peplink
The three layers are designed to be learned and sold as a single story. A customer does not buy “a router and then some SD-WAN software and then a management subscription” as separate decisions the way they would in a traditional stack. They buy a Peplink device, which is already a router, firewall, gateway, and SD-WAN endpoint in one box, and they manage it from InControl. The hardware runs the SpeedFusion engine; InControl orchestrates the hardware. When you understand that the same SpeedFusion protocol runs on the smallest BR1 Mini and the largest Balance, and that InControl manages all of them identically, the product line stops looking like a catalog and starts looking like one coherent system at different sizes.
Why it matters
Most confusion in the field comes from blurring these layers. “SpeedFusion isn’t working” is a different problem depending on the layer: it might be a hardware/WAN problem (a link is down), a SpeedFusion configuration problem (no tunnel partner, wrong ports), or an InControl problem (a policy pushed the wrong setting). Knowing which of the three layers you are standing on tells you where to look. When a customer asks what they are actually buying, the cleanest answer is: a device that is its own SD-WAN edge, running an engine that bonds connections, managed from a cloud that makes a thousand sites as easy as one.
The note that matters
Keep this model in mind through every section that follows. When we describe WAN Smoothing, it is a SpeedFusion feature (middle layer) that you turn on from InControl (top layer) and that runs on the router (bottom layer). Almost every Peplink capability is a collaboration between these three, and naming the layer is the fastest way to reason about it.