Softwr

Developer Tools · head to head

Envoy vs HAProxy

Envoy logo

Envoy

Developer Tools

A high-performance L7 proxy written in C++ that is configured by an API rather than a config file, and is usually deployed under a control plane.

From
Free
Free plan
Yes
HAProxy logo

HAProxy

Cloud

High-performance TCP and HTTP load balancer

From
Free
Free plan
Yes

The short version

  • Both are free.
  • Only Envoy lists xDS dynamic configuration; only HAProxy lists high throughput.
  • Where HAProxy falls short: configuration syntax is dense and unforgiving, with a steep initial learning curve.
  • Prices and features on this page were last checked on 20 November 2026.

How do Envoy and HAProxy differ?

Envoy and HAProxy differ on pricing model, platforms (Web against Linux, Self-hosted) and category (Developer Tools against Cloud). Only the attributes on which Envoy and HAProxy actually diverge.

Attributes where Envoy and HAProxy differ
AttributeEnvoyHAProxy
Pricing modelOpen-sourceOpen source, no licence fee
PlatformsWebLinux, Self-hosted
CategoryDeveloper ToolsCloud

Identical on both: starting price (Free), free tier (Yes).

Not yet recorded: founded for Envoy.

Which features does each one have?

They share no listed features; 8 appear only for Envoy and 4 only for HAProxy. Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Envoy

  • xDS dynamic configuration
  • Protocol breadth
  • Filter chain architecture
  • Observability by default
  • Outlier detection
  • Traffic shaping
  • mTLS termination and origination
  • Hot restart

Only in HAProxy

  • High throughput
  • Layer 4 and 7
  • Health checking
  • Rate limiting and ACLs

What is each one used for?

HAProxy is most often brought in for precise traffic control — rate limits, sticky sessions, complex routing rules. The jobs each tool is most often brought in to do.

Envoy

  • Acting as the data plane under a service mesh or Gateway API implementation, which is how the overwhelming majority of deployments use itnot HAProxy
  • An edge or API gateway that needs per-route retry budgets, circuit breaking and outlier detection rather than round-robin proxyingnot HAProxy
  • Migrating traffic between service versions or between a monolith and its replacement, using weighted splits and shadow trafficnot HAProxy
  • Standardising observability across a polyglot estate, so that latency, error rates and tracing look the same regardless of the language a service is written innot HAProxy

HAProxy

  • Load balancing at traffic levels where proxy efficiency shows up in the hardware billnot Envoy
  • Precise traffic control — rate limits, sticky sessions, complex routing rulesnot Envoy
  • TCP load balancing for databases and non-HTTP servicesnot Envoy

Where do Envoy and HAProxy fall short?

HAProxy's most cited limit: configuration syntax is dense and unforgiving, with a steep initial learning curve. Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Envoy

  • The configuration surface is very large and hand-written bootstrap YAML runs to hundreds of lines for routing that Nginx expresses in twenty, which is why nearly every production deployment sits under a control plane and inherits that control plane's constraints as well
  • xDS is the real API and it is not stable in the comfortable sense; the v2 API set was removed outright, resource types continue to be deprecated, and your control plane and Envoy binaries have to be upgraded roughly in step or the proxies stop accepting configuration
  • Extending it properly means writing a C++ filter and building and maintaining your own Envoy binary; the alternatives are Lua, which adds per-request overhead, and proxy-wasm, whose ABI has remained effectively experimental for years with a real performance cost
  • At sidecar density the per-proxy memory and CPU footprint is a measurable share of cluster capacity, since thousands of workloads each carry a full proxy, and this is precisely the cost that has pushed mesh projects towards node-level or ambient architectures
  • There is no single vendor selling support for Envoy itself; you get the community plus control-plane vendors such as Solo.io and Tetrate, so an Envoy-level production bug is your own engineers in a C++ codebase unless a support contract happens to cover it
  • Diagnosing why a request got a particular response involves reading config dumps, the stats endpoint and the RESPONSE_FLAGS codes in access logs rather than a readable error, which is a specific skill you must hire or spend months growing

HAProxy

  • Configuration syntax is dense and unforgiving, with a steep initial learning curve
  • No automatic certificate management, unlike newer servers that treat it as default behaviour
  • The built-in stats page is basic, so real observability needs exporters and dashboards
  • A dedicated load balancer is more machinery than small deployments need

How much do Envoy and HAProxy cost?

Envoy is free to use; HAProxy is free to use. Plan by plan below, from each vendor's own pricing page.

Envoy

Free

No published plan breakdown. See the Envoy review.

HAProxy

Free
  • HAProxyFree
    • Full functionality
    • No usage limits
    • Community support

Which should you pick?

Choose Envoy if

  • You need xds dynamic configuration.
  • You want to start without paying.
  • You also want protocol breadth.

Choose HAProxy if

  • You need high throughput.
  • You want to start without paying.
  • You work on Linux, Self-hosted.
  • You also want layer 4 and 7.

Questions people ask

Is Envoy or HAProxy better?
Neither clearly leads. Envoy starts at Free and HAProxy at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Envoy or HAProxy?
Envoy starts at Free and HAProxy at Free.
Does Envoy or HAProxy run on more platforms?
Envoy runs on Web. HAProxy runs on Linux, Self-hosted.
Can I use Envoy for free?
Both have a free tier, so you can try either at no cost before committing.
What is Envoy best used for?
Envoy is most often used for acting as the data plane under a service mesh or gateway api implementation, which is how the overwhelming majority of deployments use it, an edge or api gateway that needs per-route retry budgets, circuit breaking and outlier detection rather than round-robin proxying, migrating traffic between service versions or between a monolith and its replacement, using weighted splits and shadow traffic, standardising observability across a polyglot estate, so that latency, error rates and tracing look the same regardless of the language a service is written in. Of those, acting as the data plane under a service mesh or gateway api implementation, which is how the overwhelming majority of deployments use it and an edge or api gateway that needs per-route retry budgets, circuit breaking and outlier detection rather than round-robin proxying are not what HAProxy is typically brought in for.
What can Envoy do that HAProxy cannot?
Envoy covers xDS dynamic configuration, Protocol breadth, Filter chain architecture, Observability by default. HAProxy covers High throughput, Layer 4 and 7, Health checking, Rate limiting and ACLs.

Answered from the vendors’ own pages

Envoy: Should I run Envoy on its own, or under a control plane?

Almost always under one. Directly authoring xDS or static bootstrap configuration is viable for a handful of routes and becomes unmanageable beyond that. Envoy Gateway, Istio, Contour, Gloo and Consul all exist to generate that configuration for you.

HAProxy: Is HAProxy free?

Yes, the community version is open source. HAProxy Technologies sells HAProxy Enterprise separately.

Envoy: How does it compare with Nginx or HAProxy?

Envoy is dynamically configured over an API and instrumented far more heavily; Nginx and HAProxy are faster to configure and lighter for straightforward reverse proxying. If you never need to change routing without a reload, Envoy is more machinery than the problem requires.

HAProxy: HAProxy or Nginx?

HAProxy is a specialist load balancer with deeper balancing and health-check features. Nginx also serves static content and is more approachable, which is why it is more common as a general web server.

Envoy: What does it cost?

Nothing to licence; it is Apache 2.0 and there is no paid edition. The cost is engineering time and, for most organisations, a commercial control plane or cloud service that packages it.

HAProxy: Does HAProxy handle TLS certificates automatically?

No. Certificate issuance and renewal are external, unlike Caddy where it is automatic.

Envoy: Can I write extensions without C++?

You can write Lua filters or proxy-wasm modules in Rust, Go, C++ or AssemblyScript. Both carry per-request overhead compared with a native filter, and the Wasm path has been slower to stabilise than the project originally projected.

Envoy: Is it a CNCF project?

Yes, it is a graduated CNCF project licensed under Apache 2.0, which means the trademark and governance sit with the foundation rather than with Lyft or any vendor.

Share

Related pages

Other head to heads