Try our new research platform with insights from 80,000+ expert users
reviewer1446387 - PeerSpot reviewer
System Administrator at Routeware, Inc.
Real User
Enabled us to become more reliable and have less downtime
Pros and Cons
  • "Persistence is very valuable. This holds the connection information of the source and that connection is important to RDP and our APO calls. The connection has to be persisted to the original source to operate properly. We also use the subsections for sub-services to create services inside our services for our API resources, this is most awesome. We would not be able to do this without Kemp and offer this type of sub-service to route based on an API instance. It routes the traffic properly based on the sub-service type."
  • "I would like to see more automation and control of overactive and inactive resources. If I could schedule these around our updates then it would be all automated. I would like to set up an automated script to coincide with the scripts I use to update resources and servers."

What is our primary use case?

We use Kemp to balance the load of connections to various places. We have IIS, RDP, API, gateway servers, and objects that get over 5000 connections that are balanced with Kemp. 

We have had very good success at getting this working properly and doing exactly what we need. We need to balance resources and utilize the Kemp Loadmaster to organize the servers and resources to keep them operating at an optimal level. RDP and Gateway servers are 99.99% uptime so having Kemp in the middle makes that an easy transition if there is an outage or server error.

How has it helped my organization?

We used to manually balance the load and we overallocated resources to account for this situation. Since we started using Kemp, we have become more reliable and have less downtime. We also have the added resources back now that we can allocate the precise need. There is another added bonus, we can have rolling updates because we can balance the load and update inactive servers or resources.

We have had our uptime guarantee enhanced because of the Kemp tools and resources. The load that our servers can handle has been minimized and resources have been restored.  

What is most valuable?

Persistence is very valuable. This holds the connection information of the source and that connection is important to RDP and our APO calls. The connection has to be persisted to the original source to operate properly. We also use the subsections for sub-services to create services inside our services for our API resources, this is most awesome. We would not be able to do this without Kemp and offer this type of sub-service to route based on an API instance. It routes the traffic properly based on the sub-service type. 

What needs improvement?

I would like to see more automation and control of overactive and inactive resources. If I could schedule these around our updates then it would be all automated. I would like to set up an automated script to coincide with the scripts I use to update resources and servers. If I update a server on Wednesday then I would use Kemp to automate the server being taken out of service before and then put back into service after. That could streamline the whole update process and it should do some simple checks and tests to make sure the server or resource is reliable and able to be reached. 

Buyer's Guide
Kemp LoadMaster
August 2025
Learn what your peers think about Kemp LoadMaster. Get advice and tips from experienced pros sharing their opinions. Updated: August 2025.
866,218 professionals have used our research since 2012.

For how long have I used the solution?

We have been using Kemp for about five years now. 

What do I think about the stability of the solution?

I have only had one issue in five years, so I would say the stability is impeccable. 

What do I think about the scalability of the solution?

It scales for everything we have grown to need and more so far! 

How are customer service and support?

Kemp has the best customer service of all the vendors we use. 

Which solution did I use previously and why did I switch?

We used DNS Round-robin and some manual intervention but it was unreliable and very time-consuming. 

How was the initial setup?

I had support walk me through the setup. They happily helped me before I was even a client. They set up the first service with me and I had it in production that same day! 

What about the implementation team?

I implemented this myself. It is turn key ready with various templates that are plug and play. 

What was our ROI?

We have saved on man-hours from the manual intervention we used to do as well as the resources we saved from right-sizing our resources that we could then use in other areas. 

The return is triple what we invest. 

What's my experience with pricing, setup cost, and licensing?

I would advise them to take advantage of the trials and support. Use the support to set it up exactly the way you want and see how much actually need to pay for. 

Which other solutions did I evaluate?

I looked at Barracuda but the support was terrible and so I went with Kemp and am so glad I did. The support has been stellar. 

What other advice do I have?

Go with Kemp, you will thank me later. 

Which deployment model are you using for this solution?

On-premises
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
reviewer1444176 - PeerSpot reviewer
Principal Systems Engineer at World Travel Holdings
Real User
Greatly fortified the performance and uptime of our front-door email ingress
Pros and Cons
  • "It has greatly fortified the performance and uptime of our front-door email ingress, simplified and segmented mail routing, and reduced admin overhead for mail issue resolution and troubleshooting."
  • "Certificate installations could be simplified and modernized, and allowed to be monitored for expirations/issues."

What is our primary use case?

We use LoadMaster for HA Clustered Pair Load Balancer for primarily Exchange on-premises deployment and all supporting services (SMTP, ActiveSync, Autodiscovery, OWA/EWS, etc.)  Secondarily, for non-Exchange, application-server-based mail routing.

We implemented in 2014 as a dedicated load handling solution for inbound on-prem internal Exchange SMTP. We soon adapted the appliances to handle more tasks such as VIP-based routing to our middleware MTAs, mobile devices via ActiveSync, Outlook Autodiscover services Exchange Web Services & Outlook Web Access.

How has it helped my organization?

It has greatly fortified the performance and uptime of our front-door email ingress, simplified and segmented mail routing, and reduced admin overhead for mail issue resolution and troubleshooting.

The ease of the UI has allowed several relatively untrained admins to take over administrative duties, firmware upgrades, service monitoring, issue troubleshooting, and basic maintenance tasks like failover/failbacks.

It has also given us previously lacking visibility into mail flow metrics, service-based volume, connection issue granularity, and high availability.

What is most valuable?

The Virtual Service setup, maintenance & monitoring, the straightforward setup, ease of configuration changes, and simple investigation of issues are the most valuable features. 

The ability to rapidly and without interruption, redirect traffic from place to place, set up testing environments, and use as a tool to eliminate variables in downstream application/real Servers when they are having issues are also valuable.

The true real-time monitoring of service interruptions downstream have been a very valuable tool for us when troubleshooting end to end transmission issues.

What needs improvement?

Certificate installations could be simplified and modernized, and allowed to be monitored for expirations/issues.

We had a particular issue where we believed the Kemp LoadMaster was to blame for service disruption of a particular VIP (virtual-IP) based service, based on the supporting evidence. In the end, it was actually expired certificates downstream, which was not the Kemp's fault per se but it would have helped greatly and reduced our time with support if the Kemp had an alert for this type of problem, without needing to search logs/packet capture.

For how long have I used the solution?

I have been using Kemp LoadMaster for more than seven years.

What do I think about the stability of the solution?

In 20 years in IT with over a dozen similar products used, it ranks easily in my top 3 for overall uptime and stability of application/IP-based load balancers.

What do I think about the scalability of the solution?

We only use a 2 node cluster but the scalability at the hardware level seems to be mostly effortless. Partners can be added relatively easily.

Scaling up the number of VIPs/services is likewise as effortless. Performance seems very good for the roughly 20 VIP/services we use it for.

How are customer service and technical support?

Kemp's Support is the best in the business, having opened several tickets with them over the years they have always excelled and never disappointed.

Which solution did I use previously and why did I switch?

Yes, because we were upgrading the entire organization's Exchange version and we wanted a better, HA Clustered solution to match the Exchange redundancy we had built.

How was the initial setup?

From what I have gleaned it was straightforward but we had a 3rd party set it up for us.

What about the implementation team?

Vendor Team, very high level of expertise. The purchase of this product was suggested solely by him due to his past successes with deploying it.

What was our ROI?

I have not quantified actual ROI numbers but given the longevity and high-usage of this appliance I would imagine very high, easily our top 15% of IT Infrastructure ROI.

What's my experience with pricing, setup cost, and licensing?

We did hire a 3rd party professional service contractor for the setup, however, he was already used to implement the Exchange build-out. This added some cost to it but may have not been needed since the Kemp design and initial config seems very straightforward.

Purchasers may want to consider this setup expense depending on their own staff confidence level.

Which deployment model are you using for this solution?

On-premises
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
Buyer's Guide
Kemp LoadMaster
August 2025
Learn what your peers think about Kemp LoadMaster. Get advice and tips from experienced pros sharing their opinions. Updated: August 2025.
866,218 professionals have used our research since 2012.
reviewer1443177 - PeerSpot reviewer
Network and System Administrator at Kliniken Maria Hilf GmbH
Real User
Improved uptime and security for our Exchange servers, and the support is great
Pros and Cons
    • "In the web interface, there are a lot of settings in the different menus and it would be helpful if there were an interactive help system or tooltips to help the administrators find and configure the right settings."

    What is our primary use case?

    Our company e-mail and mobile communication system, which is based on Exchange Servers, needed load-balancing and security. After a few discussions with resellers and external consultants, we decided on the Kemp Load Balancer solution.

    Our installation is a virtual Kemp Load Balancer based on VMware. We have configured four  Exchange Servers in a DAG configuration and we have been very satisfied since it was installed. In the future, we would like to map further services via the Kemp.

    How has it helped my organization?

    For us and our e-mail and mobile communication system, the load-balancing and security features are very well-suited. 

    From the installation and configuration to the daily routine, Kemp is great. Importing and defining the rules for the communication systems was quick and easy. Various services and ports are configured for our e-mail and mobile communication system, and we configured some Access Control Lists (ACLs) and the Web Application Firewall (WAF).

     After the configuration was complete, we found that we can still use Kemp for more services. 

    What is most valuable?

    The most valuable feature is that load-balancing, as Kemp helps to maintain the uptime from the e-mail servers.

    If we have or need a maintenance window for one of the other e-mail servers, Kemp will still deliver your e-mail traffic to the other server. It just works.

    It is easy to apply windows updates to your Exchange environment, and using the Kemp Load Balancer made it easier to handle.

    Another great feature is the ability to use the Kemp Load Balancer virtual appliance in our VMware environment.

    What needs improvement?

    In the web interface, there are a lot of settings in the different menus and it would be helpful if there were an interactive help system or tooltips to help the administrators find and configure the right settings.

    The configuration of "standard" services is quite easy but when you configure more advanced settings, it's no longer easy and can be challenging. The Kemp Load Balancer is a very good product out of the VMware ISO (Box).

    Sometimes, you feel years back in the web interface but it's just cosmetic.

    For how long have I used the solution?

    We have been using Kemp LoadMaster for nearly two years.

    What do I think about the stability of the solution?

    Stability-wise, this is a great product.

    What do I think about the scalability of the solution?

    The scalability is great.

    How are customer service and technical support?

    We had contact with customer service/technical support for the license renewal and i can say the contact was very helpful and friendly, just great. Until now all our questions have been answered and resolved by the vendor.

    Which solution did I use previously and why did I switch?

    We haven't tried any other solution.

    How was the initial setup?

    The initial setup was straightforward.

    What about the implementation team?

    It was a mix between in-house and vendor team, and the expertise of the vendor team is awesome.

    What was our ROI?

    There is no ROI. It is for security reasons that we decided to use the Kemp Load Balancer solution. We no longer wanted the traffic to go directly to the Exchange servers.

    What's my experience with pricing, setup cost, and licensing?

    The costs for the Kemp Load Balancer solution are okay because, for a good product, you have to spend money.

    Which other solutions did I evaluate?

    We did not evaluate other products. We thought about some other solutions in theory but ultimately decided in favor of Kemp.

    What other advice do I have?

    Its a Kemp it works great.

    Which deployment model are you using for this solution?

    On-premises
    Disclosure: My company does not have a business relationship with this vendor other than being a customer.
    PeerSpot user
    PeerSpot user
    IT Manager at SWITCHCRAFT INC
    Real User
    Good protection against email outages, and the support is helpful
    Pros and Cons
    • "The old process of manually having to redirect Outlook Web Access traffic and Email traffic to a second server is a thing of the past."
    • "The cost of the GEO upgrade is not cost-prohibitive but it's something that would be a nice add-in, out of the box."

    What is our primary use case?

    We use the Kemp Load balancer with our on-premise Exchange 2016 using two servers on a DAG at different locations. The Kemp load balancer allows us to have a hands-off failover between servers either in a Disaster Recovery model or during upgrades for security patches or service pack updates for the Exchange software.

    We are now expanding this for our corporate webserver that will also be hosted at both of our locations. We have more confidence in having on-premise applications than trusting the Cloud. 

    How has it helped my organization?

    Our organization is better protected from an email outage than before. The old process of manually having to redirect Outlook Web Access traffic and Email traffic to a second server is a thing of the past.

    I can sleep at night because of the Kemp Load Balancer, just knowing that in case of a failover, the email will keep flowing and our users will have access in the morning.

    Having near 100% uptime for email is critical. Without email access, we would lose business

    What is most valuable?

    With the move from our second Exchange server to the second data center, the GEO function allows the Kemp LoadMaster / Balancer to work together.

    We originally deployed Kemp when we had both Exchange servers at one site. That was good to start with, but as we upgraded to Exchange 2016, we needed to have devices that would handle this increased functionality. The GEO functionality made this happen, allowing the two devices to see each other and determine the failover in either a Disaster Recover of software patch scenario.

    What needs improvement?

    I can think of three things that would be nice; First, it would be helpful if the GEO function was built into every device. The cost of the GEO upgrade is not cost-prohibitive but it's something that would be a nice add-in, out of the box.

    The second is the throughput. If the device was licensed based on the throughput then we could upgrade hardware to get better transactional throughput.

    Third, if they had dual power supply options on the lower end models it would be helpful because I may be a smaller shop with only 35 servers, but I still rely on dual power supplies whenever possible.

    For how long have I used the solution?

    Switchcraft has been using Kemp Load balancer for about three years.

    What do I think about the stability of the solution?

    Kemp is very stable and we have never had an issue.

    What do I think about the scalability of the solution?

    You need to upgrade devices to increase the scale.

    How are customer service and technical support?

    Support has been easy to deal with. I have only needed to contact them a few times during the initial setup. Once it's been in place and operational, we have not needed to mess with the system, which is a huge advantage.

    Which solution did I use previously and why did I switch?

    Kemp was my first experience with load balancers.

    How was the initial setup?

    The initial setup was easy.

    What about the implementation team?

    Our partner was great. They had used the devices before, which made it easy.

    What was our ROI?

    ROI was immediate, as it gives us peace of mind that email would stay up. Call it insurance.

    What's my experience with pricing, setup cost, and licensing?

    Set up was easy; nothing is cheap nowadays but it is well worth the cost

    Which other solutions did I evaluate?

    We did not look at other solutions, as it was recommended by our Consulting partner on the project.

    What other advice do I have?

    The Kemp load balancer is well suited for an on-premise Exchange system, either at one location or at two.

    It is also suitable to use for balancing web site traffic between systems..

    Kemp works well when used with two or more units in a multi-site environment  I have not found a solution that the Kemp will not handle well.

    Which deployment model are you using for this solution?

    On-premises
    Disclosure: My company does not have a business relationship with this vendor other than being a customer.
    PeerSpot user
    reviewer1444170 - PeerSpot reviewer
    Systems Engineer at Rochester Regional Health
    Real User
    Reliable with good support, and offers options to block specific ciphers and protocols
    Pros and Cons
    • "One of the most valuable features I like is the ability to block specific cipher suites like RC4, and older protocols like SSL 3.0."
    • "The only thing I have struggled with is setting up automatic backups."

    What is our primary use case?

    We use LoadMaster for load balancing our Exchange, Skype for Business, LDAP, Citrix, and SharePoint solutions. We have virtual services setup for traffic originating from inside and outside our network and can manage them separately.

    These sites each have certificates and we can update and manage them in one place, which is really helpful with our wildcard certificate that applies to multiple services. We also use the load balancers to manage some security protocols we want to allow or deny per application.

    How has it helped my organization?

    We are able to take balanced servers offline for maintenance without interruption or late nights. This is very helpful to role out things like Windows Updates to our Exchange servers and put them back into the mix, monitoring for logs or user helpdesk tickets for issues before rolling them out to the other servers.

    We can even make protocol changes per real servers and watch for their influence on traffic to that server specifically. We have done this many times for older security protocols we want to block such as old RC4, SSL, and TLS.

    What is most valuable?

    One of the most valuable features I like is the ability to block specific cipher suites like RC4, and older protocols like SSL 3.0. We were also able to block TLS1.3 as it was causing issues with Android phones connecting to Skype and we could do that with one checkbox in one place.

    Another nice feature is the ability to introduce new servers into an application without the need to do interruptive forklift changes to our most critical applications.

    It is also easy to apply our wildcard certificate in one place and it is instantly used by all of the sites that point to it at once.  

    What needs improvement?

    The only thing I have struggled with is setting up automatic backups. When the job runs, it doesn't seem to do anything and the backup file never shows up in the destination folder.  When I run a manual backup it works fine, but it just dumps the file to my local downloads folder. Otherwise, all of the features that it offers work well for us and it hasn't yet let us down.

    For how long have I used the solution?

    We have been using LoadMaster for the past four years.

    What do I think about the stability of the solution?

    The product is very stable! We never had an outage in the four years that I've been with the company.

    What do I think about the scalability of the solution?

    We have been able to manage about 20 virtual services at our highest with two LoadMasters and performance-wise they were easily able to handle the load, even though most of our sites use certificates at the LoadMaster and real-server level.

    How are customer service and technical support?

    Technical support is always great for me. They respond quickly when a case is opened online and I have always had a very knowledgeable agent when I cold call them. It does not take them 30 minutes to figure out what we have set up, they always diagnose and resolve quickly for me.

    Which solution did I use previously and why did I switch?

    Kemp was our first product to use.

    How was the initial setup?

    It was straightforward once we understood the setup, and the support was a great help.  

    What about the implementation team?

    Our in-house team was responsible for deployment.

    What was our ROI?

    We are a hospital and none of our patient applications run through our load balancers, so ROI isn't calculated.

    Which other solutions did I evaluate?

    This product was in place before I started with the company.

    What other advice do I have?

    I would advise that you use the virtual appliances if you can. We did have a hardware failure twice on our original physical appliances and it is a bit of a vulnerability to go down to one LoadMaster while the other one is in the shop.

    I can't think of any services I would like to add, as I haven't come across a situation where I wanted it to do something that it couldn't do.

    It's been a great reliable product for us, and I would recommend it to anyone!

    Which deployment model are you using for this solution?

    Private Cloud

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Other
    Disclosure: My company does not have a business relationship with this vendor other than being a customer.
    PeerSpot user
    reviewer1444182 - PeerSpot reviewer
    IT Services Manager at dSPACE GmbH
    Real User
    Improves our site performance and availability, with load-balancing that is easy to configure
    Pros and Cons
    • "Load-balancing is a great feature that is very easy to configure and it is always working fine."
    • "The product could be improved by making the SSL Offloading easier."

    What is our primary use case?

    We use Kemp LoadMaster for our SharePoint environment, worldwide.

    We use Kemp to improve the security and availability of our web services, to external customers and partners, as well as a custom banquet application that is accessed over a cloud connection.

    The Kemp LoadMaster gives us load balancing and reverse proxy capabilities, as well as a web application firewall to protect our web application environment and website.

    We use the technology across the entire organization to solve the issue of site performance and availability for external users when booking and managing events.

    How has it helped my organization?

    Kemp and the application are hidden in the background and are always working. Kemp is great for organizations that feel they have been squeezed by traditional higher-priced load-balancer vendors (F5).

    Kemp stood out from day one, with a lot of flexibility in how you can deploy and purchase the products. As a software product, they give you a seamless experience, whether you deploy it in the cloud or in your existing networking closet/data center.

    What is most valuable?

    Load-balancing is a great feature that is very easy to configure and it is always working fine.

    If you find that something is not working you can make a feature request. A few weeks later, the feature could be implemented with a new update.

    Installing updates is very easy and always works well.

    The response time after a reboot is good.

    What needs improvement?

    The product could be improved by making the SSL Offloading easier.

    For how long have I used the solution?

    We have been using Kemp LoadMaster for about seven years.

    How are customer service and technical support?

    The Kemp support team is outstanding. They were very helpful; not only did they help us to better understand the technical capabilities of Kemp, but also, they helped us resolve an issue with our VMware environment that had nothing to do with the Kemp deployment. The Kemp support actually tipped us off to the issue.

    These guys are truly experts and didn't give us the run-around. They can explain everything.

    What other advice do I have?

    I don't know what feature could be made better, as it is working really well.

    Disclosure: My company does not have a business relationship with this vendor other than being a customer.
    PeerSpot user
    reviewer1441917 - PeerSpot reviewer
    Information Technology Engineer at a government with 1,001-5,000 employees
    Real User
    Bolsters security, improves performance, and the technical support is good
    Pros and Cons
    • "Using Kemp as a front-facing service appliance, it allows me to have the flexibility of swapping out real servers behind the scenes without any intervention from my network team."
    • "If there is anything that needs to be updated, the GUI can get a refresh to make it look more like 2020, although it is just a cosmetic change."

    What is our primary use case?

    We have a small number of internal web servers that we host on-premises in our data center, along with other services that need to be accessible from the public internet. These include Remote Desktop servers, an SFTP server, Exchange, etc.

    All of these servers need extra protection on top of our standard firewall, intrusion detection, and endpoint protection.

    The primary use case of Kemp is the reverse proxy for added protection, and load balancing for better performance. We are able to leverage Kemp to protect our web servers by adding content rules and restrictions.

    We will continue to add more resources as needed behind Kemp. 

    How has it helped my organization?

    Kemp is a great product to have in our organization.

    For our use case, it provides an additional security layer by using the reverse proxy process to protect my real servers. Using Kemp as a front-facing service appliance, it allows me to have the flexibility of swapping out real servers behind the scenes without any intervention from my network team.

    Using the content rules restriction gives me the power to block off certain sections of the web pages if there is a need to do so. The load balancer aspect will allow me to optimally offload traffic evenly across my servers. 

    What is most valuable?

    For now, the reverse proxy feature is a great feature used to protect my public-facing servers. It is configured to restrict/control certain protocols from hitting my actual servers.

    Though not a feature of the product, tech support from the company is also a feature as part of the overall solution that is very valuable. I was able to get in touch with an engineer within a few minutes of calling the support line. I was able to resolve my issue pretty quickly once we restructured a few things within the environment.

    What needs improvement?

    Overall, the Kemp appliance seems to have performed very well for me over the years.

    If there is anything that needs to be updated, the GUI can get a refresh to make it look more like 2020, although it is just a cosmetic change.

    It would be a plus if there were a real-time live traffic capture that allows administrators to see the current traffic that is coming into the appliance. Currently, you can only start the TCPdump capture and have the information logged into a file.

    Maybe a configurable dashboard to show more detail about each VS service would be welcome.

    For how long have I used the solution?

    We have been using Kemp LoadMaster for three years.

    What do I think about the stability of the solution?

    KEMP is very stable as we have not had any downtime using this appliance.

    What do I think about the scalability of the solution?

    Scalability-wise, it works very well for me.

    How are customer service and technical support?

    Very pleased with the experience of talking to the tech support team.

    Which solution did I use previously and why did I switch?

    We have another solution in place and we are currently planning to retire it, now that Kemp has been implemented.

    Which other solutions did I evaluate?

    The selection was made before I came on board.

    What other advice do I have?

    It is a great product and service support is awesome.

    Which deployment model are you using for this solution?

    On-premises

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Other
    Disclosure: My company does not have a business relationship with this vendor other than being a customer.
    PeerSpot user
    reviewer1443183 - PeerSpot reviewer
    System Administrator Senior Supervisor at Xceed
    Real User
    Enhances our security, availability, and performance
    Pros and Cons
    • "The most valuable features for us are the Load Balancing and Web Application Firewall, as we have a lot of web applications."
    • "It has all types of logs and they are very detailed, but it's a little bit hard to search for a single event."

    What is our primary use case?

    Our primary use for the Kemp LoadMaster is load balancing our exchange and IIS web services to be able to meet the high availability standard for our organization. We get additional security features so there is no need to make these configuration steps on a server again. With the offloading capability, you can even secure servers that normally can't be secured.

    Currently, we are using it with our web servers and exchange, for both internal and external access. Also, the reverse proxy is one of the greatest benefits.

    How has it helped my organization?

    We use Kemp to improve the security and availability of our web properties to external customers and partners, as well as a custom banquet application that is accessed over a cloud connection.

    The Kemp LoadMaster gives us load balancing/reverse proxy capabilities as well as a web application firewall to protect our web application environment and website.

    We use the technology across the entire organization to solve the issue of site performance and availability issues of our applications to external users when booking and managing events.

    What is most valuable?

    The most valuable features for us are the Load Balancing and Web Application Firewall, as we have a lot of web applications. It was difficult to meet the high availability without doubling most of the work. With the WAF, we can publish without risking our infrastructure being internet-facing.

    The following features are also valuable:

    • TLS (SSL) Offload
    • Layer 7 Content Switching
    • High Availability (Active/Standby)
    • Health Checking
    • Permit /Deny Access Control Lists
    • IP address filtering
    • IPsec Tunnel support
    • DDoS mitigation, including L7 rate-based attacks
    • IPSec VPN to Azure, AWS, vCloud Air public clouds
    • Authenticated NTP

      What needs improvement?

      From my point of view, the only minor thing that needed to be improved is log management. It has all types of logs and they are very detailed, but it's a little bit hard to search for a single event.

      Log management is critical for investigating an attack or unwanted behavior. Since they have a lot of logs, it takes a lot of time to look for a specific event. Also, for the WAF, it would be great if they can provide a dashboard or insight dashboard for WAF logs.

      other than that there is nothing need to be improved from kemp

      For how long have I used the solution?

      We have been using Kemp LoadMaster for three years.

      What do I think about the stability of the solution?

      very stable, since 3 years we didn't face any issues 

      What do I think about the scalability of the solution?

      very easy to scale the solution

      How are customer service and technical support?

      very helpful technical team

      Which solution did I use previously and why did I switch?

      We used to work with Windows NLB, and we switched to Kemp to meet a higher level of stability and quality of service.

      How was the initial setup?

      straightforward, using the documentation provided by kemp

      What about the implementation team?

      in-house

      What's my experience with pricing, setup cost, and licensing?

      This product has good value and features for the money.

      Which other solutions did I evaluate?

      Prior to choosing Kemp, we evaluated Zen Load Balancer and NGINX. Comparing price and features, Kemp was the best option for us.

      What other advice do I have?

      Basically, Kemp covers every critical thing that must be needed to complete the task at hand.

      Which deployment model are you using for this solution?

      On-premises
      Disclosure: My company does not have a business relationship with this vendor other than being a customer.
      PeerSpot user
      Buyer's Guide
      Download our free Kemp LoadMaster Report and get advice and tips from experienced pros sharing their opinions.
      Updated: August 2025
      Buyer's Guide
      Download our free Kemp LoadMaster Report and get advice and tips from experienced pros sharing their opinions.