Speedify Self-Hosted Servers, where you choose your own server hosting, let you run your own private Speedify server infrastructure on any cloud provider or physical hardware you control. A Speedify Self-Hosted Server gives you complete control over server setup, maintenance, and location. The Speedify Self-Hosted Server, where you choose your own server hosting, is set up and maintained by you.
If you’re evaluating self-hosted bonding servers, Peplink’s FusionHub and Speedify’s Self-Hosted Server will both come up. They solve the same core problem: running the server side of a connection-bonding setup on infrastructure you control. But they make very different assumptions about what the rest of your network looks like.
This post compares the two solutions directly across the dimensions that matter most for an IT self-hosted server deployment decision.
With Speedify, your internet stays on when one connection fails.
When one of your connections drops, Speedify automatically routes your traffic to your remaining connections — so calls don't cut out and downloads don't stall.
Watch now
How Speedify's channel bonding technology works on any hardware
Get started with Speedify for your business
Speedify offers three commercial paths. They're not exclusive — most enterprise customers combine two or more.
01
Speedify Teams
Speedify on every supported OS for every team member
Centralized dashboard for billing, user provisioning, and usage analytics
CSV import/export and a RESTful management API
02
Speedify for Routers
License for supported OpenWrt routers
Powered by Speedify hardware lineup ready to deploy out of the box
Miri, GL.iNET, and other partner models
Whole-LAN bonding without per-device install
03
Embed Speedify into your product
A · DIY
Build it yourself with the Speedify SDK.
Integrate Speedify into your iOS, Android, Windows, macOS, Linux, or QNX product. Full developer documentation, sample code, and supported integration paths. You own the build, we provide the bonding stack.
B · CUSTOM ENGINEERING
Have us build it for you.
Speedify Self-Hosted Servers and Peplink FusionHub – Overview of Each Solution
FusionHub is Peplink’s virtual SpeedFusion appliance. It runs the server side of Peplink’s SpeedFusion bonding technology, deployable on VMware, Hyper-V, KVM, AWS, Azure, GCP, and other platforms. It requires client devices running Peplink or Pepwave hardware and firmware — SpeedFusion bonding endpoints must be Peplink products on both sides of the connection.
Speedify Self-Hosted Server is the server component of Speedify’s bonding stack, deployable on standard Linux. Client devices run the Speedify app, which is available for Windows, macOS, Linux, iOS, and Android, as well as OpenWrt-based routers. No proprietary hardware is required on either end.
Speedify Self-Hosted Servers vs. Peplink FusionHub – Feature Comparison
|
Speedify Self-Hosted Servers |
Peplink FusionHub |
|
|
Server OS |
Linux |
VMware, Hyper-V, KVM, OVF/OVA image; cloud via AWS/Azure/GCP AMI |
|
Client hardware requirement |
None; any device running Speedify will work |
Peplink/Pepwave hardware required on client side |
|
Client platforms |
Windows, macOS, Linux, iOS, Android, OpenWrt |
Peplink routers and Pepwave devices |
|
Bonding technology |
Packet-level channel bonding |
SpeedFusion packet-level bonding |
|
Failover |
Packet-level, automatic |
Packet-level seamless failover |
|
Encryption |
AES, ChaCha (client to server) |
SpeedFusion encrypted tunnel |
|
License model |
Subscription add-on (per server) |
One-time license by peer count; optional software warranty for updates |
|
Free tier |
No |
FusionHub Solo (1 peer, free) |
|
Air-gapped / offline network support |
Yes |
No: license validation requires connectivity to Peplink’s InControl servers |
|
Centralized management |
Via Speedify Teams’ dashboard |
Via InControl 2 (subscription required for full management) |
|
Deployment complexity |
Linux package install + license key |
OVF/OVA import or cloud marketplace AMI; more involved configuration |
The Client Hardware Question: Speedify Self-Hosted Server vs. Peplink FusionHub
FusionHub is the server side of a Peplink ecosystem. The client side — the device doing the bonding — must run Peplink or Pepwave hardware and firmware. If you want to bond connections on a laptop, a smartphone, or a non-Peplink router, FusionHub isn’t the answer. You’d need SpeedFusion Cloud (Peplink’s hosted service) or a different solution entirely for those devices.
Speedify’s Self-Hosted Servers work with the Speedify client app running on any supported platform. A field team using a mix of Windows laptops, Android phones, and OpenWrt routers can all connect to the same Speedify Self-Hosted Server without purchasing specialized hardware.
This distinction matters significantly when you’re evaluating total deployment cost. A Peplink deployment that includes FusionHub also requires Peplink or Pepwave client hardware at every bonding endpoint. That’s a capital expenditure beyond the FusionHub license itself. Speedify’s self-hosted server adds cost only at the server level; existing devices at the edge continue to work.
Licensing Structure: Speedify Self-Hosted Server vs. Peplink FusionHub
FusionHub uses a peer-based licensing model. You purchase a license that supports a maximum number of simultaneous connected devices, with tiers available from a single peer (the free Solo license) up to 4,000 peers for large-scale enterprise deployments. The license is a one-time purchase, but software updates and InControl 2 management access require an ongoing software warranty.
Speedify’s Self-Hosted Server is a subscription add-on, licensed per server rather than per client device. Client device licensing is handled separately through Speedify’s standard Teams or Enterprise plans.
One notable FusionHub constraint: the license validation mechanism requires the FusionHub server to communicate with Peplink’s InControl servers over the internet. Deployments on networks that are fully isolated from the internet — air-gapped networks, restricted government environments, certain industrial networks — cannot use FusionHub without a Private InControl Virtual Appliance (ICVA), which is a separate product.
Speedify’s Self-Hosted Server does not have this constraint once licensed; it operates independently of Speedify’s infrastructure after activation.
Deployment Complexity: Speedify Self-Hosted Server vs. Peplink FusionHub
FusionHub deploys as a virtual appliance: an OVF/OVA image that you import into a hypervisor, or a marketplace AMI for cloud deployments. The installation process involves provisioning a VM, importing the image, configuring network interfaces, and registering with InControl 2. For organizations with existing VMware or cloud infrastructure and staff familiar with those platforms, this is standard work. For organizations that prefer simpler deployment paths, the process has more moving parts than a package install.
Speedify’s Self-Hosted Server installs as a Linux package on a standard Linux instance. The process is a package install, license activation, and pointing clients at the server’s IP address. It does not require a hypervisor or a VM image; it runs directly on bare metal or a standard cloud VM.
When Speedify Self-Hosted Server Makes More Sense
- Your clients are a mix of platforms — laptops, phones, tablets, or non-Peplink routers — and you can’t or don’t want to standardize on Peplink hardware
- You need to run the server on an isolated or air-gapped network without external license validation
- You want a simpler deployment path without the overhead of provisioning and managing a virtual appliance
- You’re already running Speedify for client-side bonding and need the server component in a specific location or compliance boundary
- Your use case centers on individual devices bonding multiple connections (cellular + Wi-Fi, for example) rather than site-to-site WAN connectivity
Speedify Is Used on Millions of Devices Worldwide
Speedify has powered stronger Internet for millions of consumers since 2014
15M
Millions of Speedify downloads worldwide, and growing every day5⭐️
More than 75,000 5-star reviews for Speedify in the iOS and Android app stores82
Points of Speedify presence in datacenters around the globe500TB
Hundreds of terabytes of fast, secure data streamed every week via SpeedifySpeedify Partners
Speedify partners with these amazing organizations to deliver better internet and next-generation networking technology to their customers and employees.
Speedify Self-Hosted Server vs. Peplink FusionHub: Conclusion
FusionHub and Speedify’s self-hosted server are both legitimate answers to the same underlying question: how do I run a bonding server on infrastructure I control? They arrive at different answers because they’re built for different network architectures.
FusionHub is designed for organizations building on the Peplink ecosystem — where the hardware on both ends is Peplink, where InControl 2 is the management plane, and where SD-WAN is primarily a site-to-site problem. It’s a complete solution within that ecosystem, and within that ecosystem it works well.
Speedify’s Self-Hosted Servers are designed for businesses where bonding happens at the device level across heterogeneous hardware, where the clients are laptops and phones and embedded systems running Speedify, and where the server needs to live inside a specific infrastructure boundary. It doesn’t require buying into a hardware ecosystem to use it.
If you have existing infrastructure, mixed client hardware, or requirements that push against FusionHub’s constraints — particularly around client hardware, air-gapped networks, or deployment simplicity — Speedify’s Self-Hosted Servers are worth a closer look.
Speedify Business Solutions
Speedify Teams
Speedify for Routers
Speedify Embedded Solutions and Integrations
Embed Speedify software into your app or hardware products and leverage the core channel bonding technology of Speedify in new and interesting ways.