Install haproxy with Homebrew, apk, apt, dnf, MacPorts, Nix, pacman, zypper

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• haproxy

Project history

The HAProxy history page traces the project back to Zprox, a tool used in 1999 to test how applications behaved with many slow modem clients. In 2000 Zprox gained header rewriting and a minimal configuration language with concepts such as listeners and servers; in 2001 HAProxy 1.0 appeared as a tool for offloading traffic from hardware load balancers.

The public branch table on haproxy.org places HAProxy 1.0 on 2001-12-16, followed by 1.1 in 2002, 1.2 in 2003, and 1.3 in 2006. The early releases established the durable shape of the program: a single-purpose network daemon, a configuration file centered on frontends/backends/listeners/servers, health checking, cookie persistence, logging, and incremental protocol support.

HAProxy evolved by adding operational features without changing its basic package identity. HAProxy 1.5 brought SSL and compression into the community branch, 1.8 introduced multithreading and HTTP/2-era plumbing, 2.0 added cloud-native-adjacent features such as the Kubernetes Ingress Controller, Data Plane API, and Prometheus exporter, and 2.8 added production-oriented QUIC work along with reliability, observability, and usability improvements.

Adoption history

HAProxy became a standard choice for high-traffic HTTP and TCP load balancing because it combined low overhead, predictable behavior, and admin-friendly configuration. The project homepage emphasizes high availability, reliability, performance, and security, and the package appears across many Unix package managers in the supplied input facts.

Its adoption also reflects a packaging pattern: operations teams often need distro or package-manager builds for repeatable deployment, while also caring about exact upstream branch support, OpenSSL or alternate TLS linkage, systemd integration, and whether a branch receives only critical fixes or broader maintenance.

How it is used

Typical use is as a front-line or internal load balancer: accepting HTTP or raw TCP connections, selecting backends, checking server health, adding forwarded headers, terminating TLS, exposing stats, and allowing controlled reloads or runtime changes.

For Homebrew users, the package provides the `haproxy` executable for local development, test rigs, laptop-hosted reverse proxying, and small deployments. Production Unix installations commonly pair the daemon with a service manager and a configuration file such as `haproxy.cfg`, but the batch input has no official config path to preserve.

Why package nerds care

HAProxy is package-nerd material because it is both tiny in surface area and heavy in operational consequences. A package revision can change TLS behavior, threading defaults, QUIC support, Lua support, compression, service files, or hardening flags.

The project's parallel branch model makes version selection meaningful. A formula named `haproxy` follows the general package role, while versioned formulae such as `haproxy@2.8` exist to keep a particular upstream branch available for operators who need that branch's ABI, behavior, or support window.

Timeline

• 1999: Zprox used as a slow-client testing tool.
• 2001-12-16: HAProxy 1.0 branch listed by haproxy.org.
• 2002-03-10: HAProxy 1.1 branch adds early scheduler, health-check, logging, and cookie features.
• 2003-11-09: HAProxy 1.2 branch adds client-side IPv6 and maxconn-era scaling features.
• 2014-06-19: HAProxy 1.5 branch listed; project history highlights SSL and compression.
• 2017-11-26: HAProxy 1.8 branch listed; project history highlights multithreading and HTTP/2-related work.
• 2019-06-16: HAProxy 2.0 branch listed; project history highlights cloud-native logging, Kubernetes ingress, Data Plane API, and Prometheus exporter.
• 2023-05-31: HAProxy 2.8 branch listed; project history and homepage describe QUIC and operational improvements in that branch.

Related projects

• Related infrastructure includes NGINX, Envoy, Varnish, Keepalived, the HAProxy Kubernetes Ingress Controller, the HAProxy Data Plane API, and tools that consume HAProxy's stats or runtime interfaces.
• The PROXY protocol is closely associated with HAProxy's ecosystem because it lets upstream proxies preserve client connection metadata across TCP hops.

Sources

• https://docs.haproxy.org/
• https://github.com/haproxy/haproxy/
• https://www.haproxy.com/history
• https://www.haproxy.org/