HAProxy serves as an application load balancer that facilitates communication between applications and microservices. We operate an ad-serving platform that receives a high volume of requests to our front-facing application, and depending on certain criteria, we pass those requests to our backend application, which is horizontally scaled. We needed a proxy or load balancer between them to proxy all these requests. Instead of using a cloud-native solution, we chose HAProxy, which helps us scale effectively whenever requests are being passed through. Being an e-commerce application, we often received a lot of requests, and although we scaled our applications in the backend, HAProxy managed to handle all those connections without much scaling. This significantly helped us during events with massive traffic or specific campaigns in our e-commerce applications.
DevOps engineer at a tech services company with 1-10 employees
Real User
Top 10
Nov 2, 2025
I have been using HAProxy for about a year. My main use case for HAProxy is mostly forwarding public traffic into internal services over a Proxmox HA cluster. I get traffic from Keepalived VIP and forward it to HAProxy, and from there to internal services. I monitor and track port 80 and 443. I am also using HAProxy for Redis and RabbitMQ traffic. I have three dedicated servers right now, with each server having one Redis node and one RabbitMQ node. Based on the traffic, for example, if an API is running on host one, HAProxy forwards traffic from this API host one to host one Redis node or RabbitMQ node one, internally making them use the same host to prevent latency.
Junior System Administrator & DevOps at a tech services company with 11-50 employees
Real User
Top 10
Oct 3, 2025
My main use case for HAProxy is for my project, which focuses on full high availability. I use HAProxy for load balancing between my two apps while connecting to Keepalived. HAProxy is very helpful for myself and my team, utilized primarily for load balancing as it is powerful for that purpose.
I use the solution in my company for TCP streams. I have not used the product for web servers like Apache and NGINX. I have used the product for SMTP and SMPP protocols. I also used the tool for email services and POP3 servers. HAProxy handles the area where traffic has to be forwarded from one port to another very well.
The main use cases are for load balancing and limiting traffic. It is utilized as a front-end server for balancing HTTP traffic, as well as for balancing traffic between application servers and database servers like Redis and Elasticsearch. HAProxy is employed for both HTTP and TCP load balancing purposes, ensuring optimal resource utilization and preventing overloading of any single server.
We use it as a load balancer for our application servers, including Bonita, VPMN, our NAS reporting tools, and Telus solutions. We have two or four applications in the back end and use HAProxy as a load balancer.
UNIX System Administrator at a financial services firm with 5,001-10,000 employees
Real User
Nov 10, 2021
I use it for managing Redis clusters where I have a front-end for a read-write and a front-end for a read-only. I have no idea who else in my company uses it. I had opted to use this because we have silos in our company. We have a network silo that does the load balancing, and I wanted to control how these tests worked with the load balancing. I wanted them to do load balancing where they hand off like a TCP Fast Open. They perform a check on these services with TCP Fast Open. For example, there is one free HAProxy service for each node, and they use TCP Fast Open for things like that. It's flipped to the HAProxy, and then they establish a persistent connection. It's more of a hand-off, and then I can do all the magic. You can do most of the things I'm doing with HAProxy in F5 too. However, it's siloed off and takes a long time to get things done. I don't have any agility. I took that upon myself with HAProxy because it's a lot quicker to do it myself instead of waiting weeks for somebody else to do it.
DevOps-Infrastructure Team Leader at a tech company with 201-500 employees
Real User
Jan 23, 2019
HAProxy is used both as an external (customer facing) and internal (between service APIs) solution. We use it for SSL offload, domain and path based ACLs, request header manipulations, and much more.
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 serves as an application load balancer that facilitates communication between applications and microservices. We operate an ad-serving platform that receives a high volume of requests to our front-facing application, and depending on certain criteria, we pass those requests to our backend application, which is horizontally scaled. We needed a proxy or load balancer between them to proxy all these requests. Instead of using a cloud-native solution, we chose HAProxy, which helps us scale effectively whenever requests are being passed through. Being an e-commerce application, we often received a lot of requests, and although we scaled our applications in the backend, HAProxy managed to handle all those connections without much scaling. This significantly helped us during events with massive traffic or specific campaigns in our e-commerce applications.
I have been using HAProxy for about a year. My main use case for HAProxy is mostly forwarding public traffic into internal services over a Proxmox HA cluster. I get traffic from Keepalived VIP and forward it to HAProxy, and from there to internal services. I monitor and track port 80 and 443. I am also using HAProxy for Redis and RabbitMQ traffic. I have three dedicated servers right now, with each server having one Redis node and one RabbitMQ node. Based on the traffic, for example, if an API is running on host one, HAProxy forwards traffic from this API host one to host one Redis node or RabbitMQ node one, internally making them use the same host to prevent latency.
My main use case for HAProxy is for my project, which focuses on full high availability. I use HAProxy for load balancing between my two apps while connecting to Keepalived. HAProxy is very helpful for myself and my team, utilized primarily for load balancing as it is powerful for that purpose.
The solution is used for high availability. We use it for the backend to distribute the load.
I use the solution in my company for TCP streams. I have not used the product for web servers like Apache and NGINX. I have used the product for SMTP and SMPP protocols. I also used the tool for email services and POP3 servers. HAProxy handles the area where traffic has to be forwarded from one port to another very well.
The main use cases are for load balancing and limiting traffic. It is utilized as a front-end server for balancing HTTP traffic, as well as for balancing traffic between application servers and database servers like Redis and Elasticsearch. HAProxy is employed for both HTTP and TCP load balancing purposes, ensuring optimal resource utilization and preventing overloading of any single server.
We use it as a load balancer for our application servers, including Bonita, VPMN, our NAS reporting tools, and Telus solutions. We have two or four applications in the back end and use HAProxy as a load balancer.
The primary use case of HAProxy is for load balancing.
Our company used the solution as a proxy for Tanzu during an initial installation for conducting performance tests.
The primary use case of this solution is to control the IP addresses accessing our devices and and blocking invalid requests to our back end servers.
I use HAProxy for individuals who can not buy low balancers. I built NFV in a box and send individuals a pathway into an HAProxy VM.
We primarily use HAProxy for the load balancer.
For production purposes, we use HAProxy, which is a web application. Our primary use case is load balancing.
We use it in a model teacher, project, and financial trading system.
I use it for managing Redis clusters where I have a front-end for a read-write and a front-end for a read-only. I have no idea who else in my company uses it. I had opted to use this because we have silos in our company. We have a network silo that does the load balancing, and I wanted to control how these tests worked with the load balancing. I wanted them to do load balancing where they hand off like a TCP Fast Open. They perform a check on these services with TCP Fast Open. For example, there is one free HAProxy service for each node, and they use TCP Fast Open for things like that. It's flipped to the HAProxy, and then they establish a persistent connection. It's more of a hand-off, and then I can do all the magic. You can do most of the things I'm doing with HAProxy in F5 too. However, it's siloed off and takes a long time to get things done. I don't have any agility. I took that upon myself with HAProxy because it's a lot quicker to do it myself instead of waiting weeks for somebody else to do it.
We are just using this product in our UAT environment.
We are using it for application load balancing.
Our primary use for this solution is to mount service for Redis.
Our primary use for this solution is to mount service for Redis.
HAProxy is used both as an external (customer facing) and internal (between service APIs) solution. We use it for SSL offload, domain and path based ACLs, request header manipulations, and much more.
Load balancing and SSL termination.