We performed a comparison between HAProxy and Kemp LoadMaster based on our users’ reviews in five categories. After reading all of the collected data, you can find our conclusion below.
Comparison Results: Kemp LoadMaster comes out on top in this comparison. It is a comprehensive and powerful solution with excellent customer support.
"The solution is user-friendly and efficient."
"The ease of use of the configuration, and great documentation, are the most valuable features for us."
"The most important features would be the load-balancing of HTTP and TCP requests, according to multiple LB-algorithms (busyness, weighted-busyness, round robin, traffic, etc). Another important feature that we cannot live without is the username/passwd authentication for legacy systems that had none."
"HAProxy Enterprise Edition has been rock solid. We have essentially had no downtime caused by our load balancers in the last 10 months, because they’ve worked so well. Previously, our load balancers caused us multiple hours per year in downtime."
"The solution is effective in managing our traffic."
"I estimate that this product has saved our company hundreds, if not thousands, of dollars in possible downtime from previous load balancers. We make a lot of our money from online sales, so it is critical to have 99.9% uptime."
"Tech support is super-quick to respond, and always on target with answers specific to the current issue."
"Stability is number one."
"The most beneficial function of using the ADC is to ensure this resiliency."
"The Global WAF has saved us more than one time from unwanted traffic."
"The security features, load balancing, built-in templates, and the easy to implement virtual IPs are great."
"Mitigates content security policy issues."
"It helps with efficiency and reactivity, in case of assistance needs."
"The security features are the most valuable features of this solution."
"I like that this is a Network Load Balancer that can be used practically with any application in the backend. They have how-to guides on how to set up Kemp NLB with Exchange, but you can use it as well for Sharepoint, RDS, or any other back end server."
"Great web balancing and remote access balancing."
"I would like to see better search handling, and a user interface, with a complete functional graphical unit"
"There are three main areas to improve: 1) Make remote management more modern by adding API. 2) Propose a general HA solution for HAProxy (no I'm using keepalived for this). 3) Thread option should be a bit more stable."
"If nbproc = 2, you will have two processes of HAProxy running. However, the stats of HAProxy will not be aggregated, meaning you don't really know the collective status in a single point of view."
"HAProxy could improve by making the dashboards easier to use, and better reports and administration tickets."
"While troubleshooting, we are having some difficulties. There are no issues when it is running; it is stable and very good; however, if there is a troubleshooting issue or an incident occurs, we will have issues because this is open-source."
"There is room for improvement in the pricing model. It could be cheaper."
"Maybe HAProxy could be more modular."
"The logging functionality could use improvement, as it is a little cryptic."
"So far, the only hitch we have run into is that would have been nice to have an easier method to add allow/whitelist entries into the Access Control lists for virtual services."
"Although Kemp is very user-friendly, it lacks a more custom configuration."
"If you want logging for SMTP traffic, you have to enable ESP, which requires you to define allowed IP addresses. That’s irritating, to say the least."
"Several elements of the GUI need work. For example, if you have many content switches, it’s difficult to find the ones you need. And where is the search feature?"
"They were still in the process of development, and for example, we set it up in a cluster. So it was one logistical unit built out of two physical devices. And the expected behavior, which I know from other devices, will be formed into a logic cluster. It's that you configure one unit. Then you bring the second unit into this cluster with the already configured primary unit. So the secondary box pulls all the configured ones from its neighbor, does everything automatically, and then synchronizes with this primary neighbor. And then it works, like, one logical unit. And this didn't work with the Kemp's initially, where they caused a lot of issues when building up a cluster, so there were some specials on how to set this up. When we built or set them up for the first time and the months afterward with no new software releases, there were a couple of problems, but in the end, they worked fine. So, they developed a lot and learned from what they've responded to, what we responded to them, and what needs fixing."
"If I had to change something it would maybe be to have a little better reporting graphics that show more details in the reporting. It seems to be a little small in the graphic, and I'm not sure if possible but maybe a GUI page that one can use to monitor if any server goes down."
"When we go serverless, we may again have to revisit this because the configuration needs to be changed. With this change, we can run into a lot of other configurations that we haven't got into, which involve additional expenses. It would be challenging to convince management to buy at that price point. It would be a balancing act of justifying that expense and the value, that is, how it is going to save a bit of time and make our platform secure. It can have better configuration ability. A lot of iterations happen when we have multiple servers pointing to the same domain. If we do not orchestrate carefully, it gets into a loop, which takes away the precious time of the user who is trying to subscribe to a service. It takes a little longer time to realize services as well as web pages."
"The product is really good as-is out of the box. If there is one thing I would change is to have the license file not be coupled with the MAC address of the device. This is actually not really useful in a virtual environment where if you have a single VM with KEMP LoadMaster and you have not set up static MAC Address, if you, for example, recreate the VM and just load the disk file on a new VM it will get new MAC address and the NLB will not work as it will not see a proper license."
HAProxy is ranked 3rd in Application Delivery Controllers (ADC) with 41 reviews while Kemp LoadMaster is ranked 7th in Application Delivery Controllers (ADC) with 48 reviews. HAProxy is rated 8.2, while Kemp LoadMaster is rated 9.4. The top reviewer of HAProxy writes "Useful for for small and quick load-balancing tasks". On the other hand, the top reviewer of Kemp LoadMaster writes "Reliable, easy to set up, and can increase your security score". HAProxy is most compared with Microsoft Azure Application Gateway, NGINX Plus, Citrix NetScaler, Envoy and F5 BIG-IP Local Traffic Manager (LTM), whereas Kemp LoadMaster is most compared with NGINX Plus, Fortinet FortiADC, Citrix NetScaler, F5 BIG-IP Local Traffic Manager (LTM) and A10 Networks Thunder ADC. See our HAProxy vs. Kemp LoadMaster report.
See our list of best Application Delivery Controllers (ADC) vendors.
We monitor all Application Delivery Controllers (ADC) reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.