Citrix Gateway (or Citrix NetScaler Gateway) is an access gateway with SSL VPN solution, providing single sign-on (SSO) and authentication for remote end users of network assets.
$995
per month
HAProxy Community Edition
Score 9.3 out of 10
N/A
HAProxy Community Edition is a free, open source reverse-proxy offering high availability, load balancing, and proxying for TCP and HTTP-based applications. It is presented as suited for very high traffic web sites.
$0
Kemp LoadMaster
Score 8.9 out of 10
N/A
LoadMaster from Kemp Technologies in New York is an application delivery controller.
$1,720
per year
Pricing
Citrix Gateway
HAProxy Community Edition
Kemp LoadMaster
Editions & Modules
No answers on this topic
No answers on this topic
VLM-500
1,720
per year
VLM-500
2,000
perpetual license
VLM-3000
3,050
per year
VLM-3000
4,000
perpetual license
VLM-MAX
7,610
per year
VLM-MAX
10,000
perpetual license
Offerings
Pricing Offerings
Citrix Gateway
HAProxy Community Edition
Kemp LoadMaster
Free Trial
No
No
Yes
Free/Freemium Version
No
Yes
Yes
Premium Consulting/Integration Services
No
No
Yes
Entry-level Setup Fee
No setup fee
No setup fee
No setup fee
Additional Details
The price for a Citrix Gateway (VPX) perpetual license is $995.00.
You must contact the sales team for subscription license pricing.
Setup is easier and more straight forward on the Kemp. While I am a technical person and can setup HAProxy for the client's needs, it would be difficult for the client to manage the configuration themselves.
Citrix is used by everyone in our Company globally across departments, and provides a standardized, very clean, rarely-changing launchpad for all the common apps your team may need. It connects to Okta for necessary security. From my understanding, app assignment to users from the back end is also very simple. That being said, while the lack of changes over the years helps with guides and familiarity, Citrix is not without it's flaws that could use updating - apps refusing to open, scheduled app crashing at 12:00pm EST every day, setup being not as streamlined as it could be for new users, ease of use lacking on the desktop app, lack of accessible guides/quick walkthrough of what the platform is upon first login, etc. Overall, I look forward to improvements for Citrix, though overall I appreciate it's simplicity leading to visual ease of navigation.
It prevents a single server failure from being a downtime event by adding redundancy to every layer of your architecture. A load balancer facilitates redundancy for the backend layer (web/app servers), but for a true high availability setup, you need to have redundant load balancers as well. So it is well suited for all production related servers and less suited for individual servers that do not require redundancy.
Loadmaster is very powerful and flexible load balancer. Variety of options allows to create a complex network of rules and routes. During our website rollout Loadmaster allowed us to run multiple generations of the website simultaneously and seamlessly by doing the content switching on the fly. Powerful API allows easy integration into any development lifecycle.
allows seamless use of 2-factor authentication for heightened security within the VPN, and lowers risk of an external hack because of it.
it allows for differing levels of security. access can be set specifically through the VPN so 2 users can use the same site and get different results depending on their active directory security policy.
It can grant the ability to launch a single application or an entire VPN envelope
Where the LoadBalancer excels is the multiple levels at which you can load balance servers. We currently use layer 7 LB, but others are available as well.
I particularly like the ability for the LB to know when servers are down, and if all are offline then you can create a redirect to a static HTML page or some other destination that is more informative.
The ease in which a service can be created and deployed using already pre-canned templates makes it a very convenient setup process.
A few, rare times each year, HAProxy CPU utilization spikes to 100% and server has to be rebooted - this may be related to HAProxy OR it could be an external factor causing this.
Citrix is a visually very clean platform, allowing for ease of use from even the least tech-savvy. That being said, the apps crashes a lot (scheduled or otherwise), and apps very often refuse to open from the dashboard, making for a frustrating/confusing experience from those who have not yet experienced these same issues daily for years now. The launcher app (for MacBook) leaves a lot to be desired in terms of both setup and daily use, making the web version more viable. First-time users are also often confused on what Citrix is - and how each app connects in order to open a program (explaining "log into Citrix on the web, then download the launcher app, then launch the Spectra app via Citrix web, which will open in the Citrix launcher app on your laptop to launch the app, but you have to paste in the URL again and log in again to access" is a handful)
It is very easy to use. I was able to find a lot of documents for it on the internet. Very good community support. There are lots of examples available to try. We mostly use a command-line user interface to interact with it. The CLI is also super easy to use and very easy to interact with
Kemp makes it very easy to setup, configure and manage the LoadMaster without needing a lot of help from their engineers. The interface is very easy to understand and intuitive to use. We like how it is not complicated - I can easily have one of my techs login and they can figure out how to setup/configure virtual services for load balancing without needing a manual or tech support.
Support is pretty good and pretty fast to respond. I can't say I can really complain about the support experience I've had with them, as they've resolved issues within a reasonable time-frame. Of course, they could always be faster and better, but I think for what we pay, it's well worth the money.
We haven't used customer support. We mostly used the community version. We build a multi-node HAProxy cluster with HA to the proxy itself using opensource plugins available. With the support available on the internet and the documents available we don't need to use much customer support.
Support has been easy to deal with; I have only need[ed] to contact them a few times during setup. Once its been in place and operational, we have not need[ed] to mess with the system [which] is a huge advantage. I like system[s] that do not break and require constant attention in a production environment.
We chose Citrix Netscaler Gateway for its wide market presence and its great experience over time. Although the implementation time may be longer than in the other solutions, I think the results are better and it allows configuration with greater capacity than the others. The cost is similar in all the solutions seen.
We chose HA Proxy because it is cheaper than a hardware balancer, it is an open-source solution with a large community behind it and with constant updates. It also allows custom scripts according to needs.HA Proxy is a solution used in many internet sites like GitHub, Reddit, Twitter, and Tuenti.
We chose Kemp LoadMaster because it is 1/10 the price of the competition and MUCH easier to deploy and configure and WORKS. We have had ZERO issues with the product since installation. Their engineers and their sales team have both reached out post-install to check in and see if everything is working as expected.
The largest positive impact was that it provided a path up upgrade from the now defunct CSG Citrix product. Because Netscaler Gateway is an at cost product, where CSG was not, one could argue there is no monetary ROI but the ROI in this scenario comes more from the ability to not have to use a non Citrix product and learn the skills needed to administer it.
Negative wise, Netscaler Gateway can be quite costly in both upfront costs and maintenance fees. It is part of business and a requirement but when using it as a replacement for CSG you will have to account for several thousands of dollars per year in additional cost.
Because it can implemented as a virtual server (it comes in both hardware and non hardware versions) the lack of need to add one more piece of hardware to our data center saves in space, up front costs, and power/cooling needs if you opt to go with the software based version.
Significantly lower investment vs competitors. In the case of F5s we have Virtual Editions so we're paying for the hardware to run it on top of the several thousand dollar licenses that are required for each pair and we currently have a pair of F5s per client so there's a huge potential for cost savings there.
Requires our network engineers to learn a new skill or our Systems engineers to take on the responsibility of managing the load balancers. It's not a huge difference either way, but it does impact the way we have done business in the past.
We used Kemp LoadMaster for many projects. For a lot of customers, load balancers were too expensive or too complicated before we introduced Kemp products.
It's not a overly complicated product, so we were able to train many engineers on it and have them get a certification.
