Get a Speedify Self-Hosted Server to Minimize Latency
Deploying a self-hosted Speedify server well requires thinking about three things in sequence:
- where to put it (geography and network topology),
- how to size it (CPU for throughput, bandwidth for capacity), and
- how to validate it (measure latency before and after, establish a baseline, monitor over time).
Getting those three right produces a deployment that performs comparably to Speedify's own infrastructure for the clients it serves. Learn more from this article.
Speedify server options
Speedify Public Servers
Enjoy increased reliability and more predictable throughput with a private server accessible to only you, your Family, or Team.
Speedify Dedicated Servers
Enjoy increased reliability and more predictable throughput with a private server accessible to only you, your Family, or Team.
Speedify Self-Hosted Servers
Run your own private Speedify server infrastructure on any cloud provider or physical hardware you control.
Included with Speedify Plans
Available to you, your family, or your teamChoose from our Server Locations
Select from any of our server locations across 6 continents and 50+ citiesLimited Speeds
Typically 200-300 Mbps, depending on capacity and network conditionsDynamic IP Address
IP address will change3TB Monthly Bandwidth
shared with you, your family, or your teamChoose from our Server Locations
Select from any of our server locations across 6 continents and 50+ citiesHigher Speeds
Up to 1 Gbps available to you, your family, or your teamStatic IP Address
Ideal for those who need to whitelist their IP for certain secure servicesGuaranteed Service Level Agreement
Each hour your server is down, you'll get a day of free servicePort Forwarding
For those who need to run a server that can be reached from the InternetUnlimited Monthly Bandwidth
shared with you, your family, or your teamChoose your own Host
Select your own hosting provider or utilize your own hardwareUnmetered Speeds
Top speeds dependent on your hosting set up or providerStatic IP Address
Ideal for those who need to whitelist their IP for certain secure servicesIncreased Security through Data Residency
Maintain data handling requirements while utilizing established provisioning, monitoring, and security workflowsPort Forwarding
For those who need to run a server that can be reached from the InternetEmbed Speedify software for the next generation of routers, networking appliances, and smart devices
Speedify Teams
Increased speed, security, and stability for all of the people and devices in your organization.
Speedify for Routers
Turn your OpenWRT, GL.iNET, or Miri router into a Powered by Speedify device that can bond available 4G, 5G, Wi-Fi, wired, and Starlink connections together.
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.
Why Self-hosted Server Location Affects Bonding Performance
Speedify's bonding technology works by splitting packets across multiple connections and reassembling them at the server. For this to work, the server has to receive packets from all the connections, put them in order, and forward the reassembled data to its destination.
Packets from different connections arrive at different times. Some connections are faster, some are slower, and that varies moment to moment. The server has to hold packets from the faster connections briefly while waiting for packets from slower connections — otherwise it would just discard the advantage of the slower connection entirely.
This waiting window is related to latency. Higher latency between client and server means more variation in arrival times, which means the server has to buffer more aggressively to compensate. The result is higher end-to-end latency for your connections and, in some configurations, reduced effective throughput.
Where to Deploy Your Speedify Self-Hosted Servers
Place your Speedify self-hosted server as close as possible, in network terms, to where your Speedify clients are. "Close" here means round-trip latency, not physical distance. A server in the same city connected via a direct fiber path is "closer" than a server in the same building connected through a congested network.
For most enterprise deployments, this means:
- If your clients are in a single office or campus, a server in the same building or in a nearby data center is ideal
- If clients are distributed across a region, a cloud instance in the nearest data center region typically works well
- If clients are spread across multiple continents, consider whether a single self-hosted server or multiple servers (possibly combined with Speedify's existing server network) better serves your population
How to Measure the Speedify Difference
Before deploying the Speedify self-hosted server, measure the round-trip latency from your planned client locations to your planned server location. Ping is a reasonable proxy. If you're seeing 20ms or less to your server location from most clients, you're in a good position. Latency above 80-100ms from client to server will begin to affect the effectiveness of bonding, particularly for latency-sensitive applications.
After deployment, compare the same metrics with an actual Speedify connection. The difference between your raw latency to the server and the latency you see on Speedify connections reflects the overhead of the bonding process. For well-configured deployments, that overhead should be small.
Speedify Proven Track Record, Global Scale
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: Hardware and Throughput
The self-hosted server's bonding performance is CPU-bound. Speedify's packet processing runs on CPU cores, so more cores generally means higher throughput ceiling.
Practical estimates:
- A 2-core VM handles light usage and testing adequately
- A 4-core VM supports moderate traffic for a small team
- 8+ cores are appropriate for higher-throughput deployments or multiple concurrent client connections with high aggregate bandwidth
Memory requirements are relatively modest — the server doesn't need to buffer large amounts of data — so it's generally better to invest in CPU over RAM when specifying server hardware.
Connection Count on the Speedify Self-Hosted Server Side
A Speedify self-hosted server should have a single, reliable, low-latency uplink connection. The bonding on the server side is not about aggregating server-side connections — that's what the client does. The server needs enough bandwidth to handle the aggregate output of all clients, but a single reliable connection is preferable to multiple connections on the server end.
If you're running a dedicated server for a team of field workers who each have 50 Mbps of bonded throughput, and you have ten such workers connected simultaneously, your server needs approximately 500 Mbps of uplink capacity. Plan accordingly.
Get in touch with Speedify
Get in touch today to discuss your business’s needs and discover how Speedify can help deliver faster, more reliable, and more secure online experiences.