HAProxy already provides many of the features that other solutions in the market are providing, such as Nginx, so I do not see much room for improvement.
DevOps engineer at a tech services company with 1-10 employees
Real User
Top 10
Nov 2, 2025
HAProxy is very easy for me to use. I installed it easily and configured it after checking the documentation, which was clear. I wrote as described, and it worked well, but an easier desktop interface to connect to a remote server and make changes on my PC would be beneficial. An alerting system would be better as I need to check log files if any backend is down. Integrated Telegram alerts or WhatsApp or different channels would make it better.
Junior System Administrator & DevOps at a tech services company with 11-50 employees
Real User
Top 10
Oct 3, 2025
HAProxy is already a robust solution, but there are a few areas for potential improvement, especially regarding configuration complexity. The configuration syntax is powerful yet can become overwhelming for newcomers; a more beginner-friendly interface or a native GUI without relying on third-party tools would ease the onboarding process. Built-in observability could be enhanced; while HAProxy features great logging and stats, utilizing Grafana, Prometheus, or external tools for in-depth insights is still necessary. Native service discovery could be improved; although dynamic scaling works, it generally requires DNS or runtime API scripting. More features in the Community Edition would be beneficial, as the Enterprise version contains advanced security, WAF, and bot protection that would be advantageous for smaller teams if included in the community build. Another area that could see improvement is documentation and onboarding resources. HAProxy's documentation is very detailed but can feel dense for newcomers, and finding practical, step-by-step examples often requires sifting through mailing lists, GitHub issues, or blog posts. More modernized guide tutorials and real-world playbooks would simplify getting started for beginners, so enhancing technical improvements to make HAProxy more approachable through better docs and a stronger community ecosystem would significantly assist in broader adoption. Additionally, an important area for improvement is tighter integration with cloud ecosystems, particularly AWS. Native AWS service discovery would be advantageous; currently, one usually relies on DNS or external scripts to register new EC2 instances in HAProxy, but direct hooks into AWS Auto Scaling Groups, ECS, or EKS would facilitate automatic joining and leaving of instances without added glue code. Furthermore, direct integration with AWS Certificate Manager or Secrets Manager could reduce manual steps surrounding SSL, TLS, and backend credentials management. Enhancing cloud-native integration, especially with AWS services, could significantly strengthen HAProxy's plug-and-play appeal in cloud environments.
HAProxy is very weak in the logging and monitoring part and requires improvement. In the future, the tool should have additional modules for different purposes.
There is room for improvement in HAProxy's dynamic configuration. Currently, dynamic changes are lost when reloading the service, and it would be beneficial if dynamic configuration changes could be applied without losing the configuration or reloading the service, ensuring backups and preserving the static configuration.
The solution can be improved by controlling TCP behavior better rather than just reporting them in the logs. Automatic blocking of clients that don't properly close their TCP session (CH/CD) would be good.
Although HAProxy is essentially open-source, many features are not available. 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. We are only experiencing problems at that time. Otherwise, everything is fine. Because we need to search for a document or some troubleshooting information. That could be beneficial to us. To resolve the troubleshooting issues, additional documentation and troubleshooting are required. The product is satisfactory. However, additional documentation, additional technical documents, and troubleshooting steps are the types of things that can only make this solution better. Also, more clarity on where the package is hitting and where it is stopping is needed.
UNIX System Administrator at a financial services firm with 5,001-10,000 employees
Real User
Nov 10, 2021
The logging is pretty hard to understand, but the documentation for the logging is decent. That would be my only criticism. Sometimes it's challenging to get through the log, and you need a log to understand what is going on. It isn't easy to map the logging with the documentation, and every time I read the log, I have to pull out the documentation to understand what I'm reading. And there is some more functionality that I would like to see. For example, you'll do a TLS to the front leg— whatever connects to your load balancer. You do the HTBS or whatever TLS connection there. And then, on the back end, you usually have to clear it a lot of times. I want to be able to do TLS all the way through on both legs. I don't know if it can do that. HAProxy might be able to do this already, but I haven't done enough research to see if this is possible
Director at a financial services firm with 501-1,000 employees
Real User
Jul 23, 2021
There is no standardized document available. So, any individual has to work from scratch to work it out. If some standard deployment details are available, it would be helpful for people while deploying it. There should be more documentation on the standard deployment. When you have to customize it for your application requirements, there are a lot of challenges. There should be more support for customization. To customize it better, there should be some kind of programming integration.
UNIX System Administrator at a financial services firm with 5,001-10,000 employees
Real User
Jun 4, 2019
The logging functionality could use improvement, as it is a little cryptic. Additional logging functionality with better documentation would be helpful.
UNIX System Administrator at a financial services firm with 5,001-10,000 employees
Real User
Jun 4, 2019
The logging functionality could use improvement, as it is a little cryptic. Additional logging functionality with better documentation would be helpful.
HAProxy is considered by many in the industry to be one of the fastest and most popular and trusted software load balancer products in the marketplace today. Organizations are able to immediately deploy HAProxy solutions to enable websites and applications to optimize performance, security, and observability. HAProxy solutions are available to scale to any environment.
HAProxy is an open-source product and has a robust, active, reliable community. The solutions are continually tested and...
HAProxy already provides many of the features that other solutions in the market are providing, such as Nginx, so I do not see much room for improvement.
HAProxy is very easy for me to use. I installed it easily and configured it after checking the documentation, which was clear. I wrote as described, and it worked well, but an easier desktop interface to connect to a remote server and make changes on my PC would be beneficial. An alerting system would be better as I need to check log files if any backend is down. Integrated Telegram alerts or WhatsApp or different channels would make it better.
HAProxy is already a robust solution, but there are a few areas for potential improvement, especially regarding configuration complexity. The configuration syntax is powerful yet can become overwhelming for newcomers; a more beginner-friendly interface or a native GUI without relying on third-party tools would ease the onboarding process. Built-in observability could be enhanced; while HAProxy features great logging and stats, utilizing Grafana, Prometheus, or external tools for in-depth insights is still necessary. Native service discovery could be improved; although dynamic scaling works, it generally requires DNS or runtime API scripting. More features in the Community Edition would be beneficial, as the Enterprise version contains advanced security, WAF, and bot protection that would be advantageous for smaller teams if included in the community build. Another area that could see improvement is documentation and onboarding resources. HAProxy's documentation is very detailed but can feel dense for newcomers, and finding practical, step-by-step examples often requires sifting through mailing lists, GitHub issues, or blog posts. More modernized guide tutorials and real-world playbooks would simplify getting started for beginners, so enhancing technical improvements to make HAProxy more approachable through better docs and a stronger community ecosystem would significantly assist in broader adoption. Additionally, an important area for improvement is tighter integration with cloud ecosystems, particularly AWS. Native AWS service discovery would be advantageous; currently, one usually relies on DNS or external scripts to register new EC2 instances in HAProxy, but direct hooks into AWS Auto Scaling Groups, ECS, or EKS would facilitate automatic joining and leaving of instances without added glue code. Furthermore, direct integration with AWS Certificate Manager or Secrets Manager could reduce manual steps surrounding SSL, TLS, and backend credentials management. Enhancing cloud-native integration, especially with AWS services, could significantly strengthen HAProxy's plug-and-play appeal in cloud environments.
The solution's implementation and troubleshooting are not easy. The solution's dashboards and reports could be improved.
The product has the basic foundations of any load-balancing product. It is simple and basic. The product does not have any new technologies.
HAProxy is very weak in the logging and monitoring part and requires improvement. In the future, the tool should have additional modules for different purposes.
There is room for improvement in HAProxy's dynamic configuration. Currently, dynamic changes are lost when reloading the service, and it would be beneficial if dynamic configuration changes could be applied without losing the configuration or reloading the service, ensuring backups and preserving the static configuration.
There is room for improvement in the pricing model. It could be cheaper.
The visibility could be improved. Stability can falter when there is a lot of traffic. End-to-end connections are limited.
The solution has bad performance issues.
The solution can be improved by controlling TCP behavior better rather than just reporting them in the logs. Automatic blocking of clients that don't properly close their TCP session (CH/CD) would be good.
I would like to see better search handling, and a user interface, with a complete functional graphical unit.
HAProxy could do with some good combination integrations.
Although HAProxy is essentially open-source, many features are not available. 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. We are only experiencing problems at that time. Otherwise, everything is fine. Because we need to search for a document or some troubleshooting information. That could be beneficial to us. To resolve the troubleshooting issues, additional documentation and troubleshooting are required. The product is satisfactory. However, additional documentation, additional technical documents, and troubleshooting steps are the types of things that can only make this solution better. Also, more clarity on where the package is hitting and where it is stopping is needed.
We've changed solutions as it doesn't fit with our current needs.
The logging is pretty hard to understand, but the documentation for the logging is decent. That would be my only criticism. Sometimes it's challenging to get through the log, and you need a log to understand what is going on. It isn't easy to map the logging with the documentation, and every time I read the log, I have to pull out the documentation to understand what I'm reading. And there is some more functionality that I would like to see. For example, you'll do a TLS to the front leg— whatever connects to your load balancer. You do the HTBS or whatever TLS connection there. And then, on the back end, you usually have to clear it a lot of times. I want to be able to do TLS all the way through on both legs. I don't know if it can do that. HAProxy might be able to do this already, but I haven't done enough research to see if this is possible
There is no standardized document available. So, any individual has to work from scratch to work it out. If some standard deployment details are available, it would be helpful for people while deploying it. There should be more documentation on the standard deployment. When you have to customize it for your application requirements, there are a lot of challenges. There should be more support for customization. To customize it better, there should be some kind of programming integration.
Pricing, monitoring, and reports can be improved.
The logging functionality could use improvement, as it is a little cryptic. Additional logging functionality with better documentation would be helpful.
The logging functionality could use improvement, as it is a little cryptic. Additional logging functionality with better documentation would be helpful.
I would like to see a two (or more) native cluster support without third parties or DNS manipulations.
A better GUI would be nice.