The primary use case of this solution is for the web application firewall. We have a Metaswitch system for our telephone service. We're front our SIP provisioning servers and our client communications portals with the WAF.

Loadbalancer.org together with Metaswitch in Enfield, England wrote a set of rules that are being managed on the Loadbalancer to prevent illegal entry, password hacking attempts, invalid SIP provisioning hacking attempts, or just general denial of service attacks into our cloud. It ensures that only what we expect to hit our systems is let through.

We use Loadbalancer.org to check Nova Network and also use it for F5. We use its load-balancing technology.

In our experience, Loadbalancer.org is best suited for small businesses looking to balance their website. They don't require HA, DR, or anything else.

We use this solution when publishing Windows based applications and other custom based SQL applications. We are in the progress of migrating the on-premises data center to the cloud and continue to use Loadbalancer for this.

I work for a value-added reseller.

Loadbalancer.org is used when an application has multiple instances. 

There are also cases where you have a production and a disaster recovery scenario, and the customer wants the users to be able to switch from the production servers to the disaster recovery servers with as little downtime as possible.

We're working on a project where our customers use HJ. We utilize their load balancer to evenly distribute the data load between multiple servers, ensuring that one server doesn't become overloaded.

Load-balancing a web application server. It's a requirement for the application which we're using, which is why we bought the hardware. It does its job. We don't touch it.

We load balance our customer billing and information system, as well as our Exchange services with it.

Web filtering and load balancing.

Load balance http and https requests, our customer service.

We are using this solution for internet management. We have approximately eight incoming ISP lines. All of the ISP lines go to the load balancer.

We use it for normal internet access.

Load balancing Exchange, print servers, our call desk software, and SharePoint.

We provide a web-filtering system for 200 schools, and Loadbalancer.org makes sure that it balances across all of the web-filtering service that we've got, to provide good quality service.

It actually makes our whole network more reliable, because of its load balancing capabilities. And not only load balancing, but also redundancy. That's what we use it for.

It has different models doing different things. One is basic load balancing. The other is doing a web application firewall. Another use case is for handling VPN exposure resources. There is one doing advanced DNS sharing as well.

We use Loadbalancer for balancing loads in our main application.

Loadbalancer.org is used in a bank. All the traffic we forward to the QA are being redirected to Loadbalancer.org. There are additional load balancers created through Microsoft Azure and the traffic is being forwarded there as an additional layer to Loadbalancer.org where we are only using IP addresses and reports.

To have live failover for an intranet site we are using, and to monitor live user connections.

The Loadbalancer.org appliance sits directly behind our firewall, terminates all of our SSL/HTTP traffic and then directs it to the backend servers depending on the requested service.

We are a supplier of medical healthcare IT solutions with a focus on radiology departments. We use it to create a redundant solution with automatic failover.

We use the hardware and the software version of the Loadbalancer.org product line.