freenginx vs HAProxy Community Edition

freenginx is an effort to preserve free and open development of server software used for HTTP, mail, and TCP/UDP proxying. Its HTTP server can serve static files, reverse proxy with caching, balance load, and provide fault tolerance. It supports SSL/TLS SNI, HTTP/2, and HTTP/3, along with access controls based on client IP address, HTTP Basic authentication, or a subrequest result. Cached and accelerated connections are available for FastCGI, uwsgi, SCGI, and memcached servers. The mail proxy supports IMAP, POP3, and SMTP authentication methods with SSL and STARTTLS/STLS. TCP and UDP proxying includes load balancing, fault tolerance, and client-address access control. The process design uses one master and several workers running under an unprivileged user. Configuration can be reloaded and the executable upgraded without interrupting client service. Source and documentation are distributed under a 2-clause BSD-like license. The software is self-hosted and uses file-based configuration; downloads include source, Windows builds, and mainline and stable versions.

HAProxy Community Edition is free, self-hosted software for proxying TCP and HTTP applications, with high availability and load balancing. It is aimed especially at very high-traffic websites. HAProxy runs on Linux, where it is included with most mainstream distributions and is often deployed by default on cloud platforms. Its event-driven design uses light multithreading on SMP machines. The project lists Layer 4 and Layer 7 routing and TLS termination, along with TCP and HTTP support; recent versions also include QUIC and HTTP/3 features. Listed safeguards include chroot, privilege drops, fork prevention, strict protocol validation, and checks for impossible states. The site reports up to 2 million SSL requests per second and 100 Gbps of forwarded traffic on AWS Graviton2. HAProxy 3.4 is in development, and 3.4.6 is the latest listed release in that branch. Its features include dynamic backends, HTTP/2 flood protections, ACME improvements, experimental QMUX, and an OpenTelemetry filter. LTS branches receive five years of maintenance; other stable branches receive 12 to 18 months.