Developer Tools · head to head
Envoy vs Eclipse Mosquitto

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

Eclipse Mosquitto
Networking
Small, EPL-licensed MQTT broker that runs on hardware other brokers cannot
- From
- Free
- Free plan
- Yes
The short version
- Both are free.
- Only Envoy lists protocol breadth; only Eclipse Mosquitto lists MQTT 5.0 support.
- Prices and features on this page were last checked on 20 November 2026.
How do Envoy and Eclipse Mosquitto differ?
Envoy and Eclipse Mosquitto differ on pricing model, platforms and category (Developer Tools against Networking). Only the attributes on which Envoy and Eclipse Mosquitto actually diverge.
| Attribute | Envoy | Eclipse Mosquitto |
|---|---|---|
| Pricing model | Open-source | Open source, no licence fee |
| Platforms | Web | Linux, Windows, macOS, Self-hosted |
| Category | Developer Tools | Networking |
Identical on both: starting price (Free), free tier (Yes).
Which features does each one have?
They share no listed features; 8 appear only for Envoy and 6 only for Eclipse Mosquitto. 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 Eclipse Mosquitto
- MQTT 5.0 support
- Very small footprint
- Bridging
- WebSockets listener
- Command line clients
- Dynamic security plugin
What is each one used for?
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 Eclipse Mosquitto
- An edge or API gateway that needs per-route retry budgets, circuit breaking and outlier detection rather than round-robin proxyingnot Eclipse Mosquitto
- Migrating traffic between service versions or between a monolith and its replacement, using weighted splits and shadow trafficnot Eclipse Mosquitto
- 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 Eclipse Mosquitto
Eclipse Mosquitto
- A home or building automation stack where the broker must run on the same small computer as everything elsenot Envoy
- An industrial gateway that buffers local telemetry and bridges selected topics to a cloud brokernot Envoy
- Local development and testing of MQTT clients without provisioning a cloud IoT servicenot Envoy
- An air-gapped deployment where a broker with no licence server and no phone-home behaviour is a requirementnot Envoy
Where do Envoy and Eclipse Mosquitto fall short?
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
Eclipse Mosquitto
- There is no clustering: Mosquitto is a single process, so high availability means building your own failover and accepting session loss on switchover
- Persistence is a local file rather than a replicated store, so a disk failure or an unclean shutdown can lose retained messages and queued QoS traffic
- Practical capacity is a few thousand concurrent clients on typical hardware, so a growing device fleet eventually forces a migration to a clustered broker
- The Eclipse Public Licence is weak copyleft rather than permissive, which some legal teams treat as a blocker when embedding the broker in a shipped commercial product
- There is no commercial support to buy from the project, so production incidents rely on community mailing lists or on paying a third party who happens to know the codebase
How much do Envoy and Eclipse Mosquitto cost?
Envoy is free to use; Eclipse Mosquitto is free to use. Plan by plan below, from each vendor's own pricing page.
Envoy
FreeNo published plan breakdown. See the Envoy review.
Eclipse Mosquitto
Free- Eclipse MosquittoFree
- Eclipse Public License 2.0 with Eclipse Distribution Licence
- MQTT 5.0, 3.1.1 and 3.1
- No client or message limits beyond your hardware
Which should you pick?
Choose Envoy if
- You need xds dynamic configuration.
- You want to start without paying.
- You also want protocol breadth.
Choose Eclipse Mosquitto if
- You need mqtt 5.0 support.
- You want to start without paying.
- You work on Linux, Windows, macOS, Self-hosted.
- You also want very small footprint.
Questions people ask
- Is Envoy or Eclipse Mosquitto better?
- Neither clearly leads. Envoy starts at Free and Eclipse Mosquitto at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Envoy or Eclipse Mosquitto?
- Envoy starts at Free and Eclipse Mosquitto at Free.
- Does Envoy or Eclipse Mosquitto run on more platforms?
- Envoy runs on Web. Eclipse Mosquitto runs on Linux, Windows, macOS, 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 Eclipse Mosquitto is typically brought in for.
- What can Envoy do that Eclipse Mosquitto cannot?
- Envoy covers xDS dynamic configuration, Protocol breadth, Filter chain architecture, Observability by default. Eclipse Mosquitto covers MQTT 5.0 support, Very small footprint, Bridging, WebSockets listener.
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.
Eclipse Mosquitto: Can Mosquitto be clustered?
No. It is a single process. High availability requires an external failover arrangement you build yourself.
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.
Eclipse Mosquitto: What licence is it?
Eclipse Public License 2.0 alongside the Eclipse Distribution License, a weak copyleft rather than a permissive licence.
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.
Eclipse Mosquitto: How many clients can it handle?
A few thousand concurrent connections on ordinary hardware; beyond that, use a clustered broker.
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.
Eclipse Mosquitto: Does it support MQTT 5?
Yes, along with 3.1.1 and 3.1.
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.
Related pages
More on Eclipse Mosquitto
Other head to heads
- Envoy vs Istio
- Envoy vs Ona (formerly Gitpod)
- Envoy vs Spacelift
- Envoy vs Jenkins
- Envoy vs Hookdeck
- Envoy vs Atlantis
- Envoy vs Restate
- Envoy vs Turborepo
- Envoy vs Helix
- Envoy vs Git
- Envoy vs Okteto
- Envoy vs StackBlitz
- Envoy vs CodeSandbox
- Envoy vs Cody
- Envoy vs Depot
- Envoy vs Neovim
- Envoy vs Azure DevOps
- Envoy vs Bitbucket
- Envoy vs HiveMQ
- Envoy vs Traefik
- Envoy vs Icinga
- Envoy vs pfSense
- Envoy vs OpenVPN
- Envoy vs Zabbix
- Envoy vs Consul
- Envoy vs LibreNMS
- Envoy vs Nebula
- Envoy vs MikroTik RouterOS
- Envoy vs PRTG Network Monitor
- Envoy vs Netdata
- Envoy vs Grafana
- Envoy vs Tailscale
- Envoy vs Cloudflare
- Envoy vs Prometheus
- Envoy vs NetBird
- Envoy vs Twingate
- Eclipse Mosquitto vs Istio
- Eclipse Mosquitto vs Ona (formerly Gitpod)
- Eclipse Mosquitto vs Spacelift
- Eclipse Mosquitto vs Jenkins
- Eclipse Mosquitto vs Hookdeck
- Eclipse Mosquitto vs Atlantis
- Eclipse Mosquitto vs Restate
- Eclipse Mosquitto vs Turborepo
- Eclipse Mosquitto vs Helix
- Eclipse Mosquitto vs Git
- Eclipse Mosquitto vs Okteto
- Eclipse Mosquitto vs StackBlitz
- Eclipse Mosquitto vs CodeSandbox
- Eclipse Mosquitto vs Cody
- Eclipse Mosquitto vs Depot
- Eclipse Mosquitto vs Neovim
- Eclipse Mosquitto vs Azure DevOps
- Eclipse Mosquitto vs Bitbucket
- Eclipse Mosquitto vs HiveMQ
- Eclipse Mosquitto vs Traefik
- Eclipse Mosquitto vs Icinga
- Eclipse Mosquitto vs pfSense
- Eclipse Mosquitto vs OpenVPN
- Eclipse Mosquitto vs Zabbix
- Eclipse Mosquitto vs Consul
- Eclipse Mosquitto vs LibreNMS
- Eclipse Mosquitto vs Nebula
- Eclipse Mosquitto vs MikroTik RouterOS
- Eclipse Mosquitto vs PRTG Network Monitor
- Eclipse Mosquitto vs Netdata
- Eclipse Mosquitto vs Grafana
- Eclipse Mosquitto vs Tailscale
- Eclipse Mosquitto vs Cloudflare
- Eclipse Mosquitto vs Prometheus
- Eclipse Mosquitto vs NetBird
- Eclipse Mosquitto vs Twingate
