Softwr

Developer Tools · head to head

Envoy vs Nmap

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
Nmap logo

Nmap

Cybersecurity

Free open source network discovery and security auditing scanner

From
Free
Free plan
Yes

The short version

  • Nmap is a free open source utility.
  • Both are free.
  • Only Envoy lists xDS dynamic configuration; only Nmap lists host discovery.
  • Where Nmap falls short: primarily a command-line tool; the Zenmap interface is a separate component.
  • Prices and features on this page were last checked on 20 November 2026.

How do Envoy and Nmap differ?

Envoy and Nmap differ on platforms and category (Developer Tools against Cybersecurity). Only the attributes on which Envoy and Nmap actually diverge.

Attributes where Envoy and Nmap differ
AttributeEnvoyNmap
PlatformsWebWindows, macOS, Linux
CategoryDeveloper ToolsCybersecurity

Identical on both: starting price (Free), pricing model (Open-source), 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 8 only for Nmap. 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 Nmap

  • Host discovery
  • TCP and UDP port scanning
  • Service and version detection
  • Operating system detection
  • Nmap Scripting Engine
  • Zenmap graphical interface
  • Ncat, Ndiff and Nping companion tools
  • Firewall and IDS evasion options

What is each one used for?

Nmap is most often brought in for network inventory. 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 Nmap
  • An edge or API gateway that needs per-route retry budgets, circuit breaking and outlier detection rather than round-robin proxyingnot Nmap
  • Migrating traffic between service versions or between a monolith and its replacement, using weighted splits and shadow trafficnot Nmap
  • 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 Nmap

Nmap

  • Network inventorynot Envoy
  • Security auditsnot Envoy
  • Firewall rule checkingnot Envoy
  • Service uptime checksnot Envoy

Where do Envoy and Nmap fall short?

Nmap's most cited limit: primarily a command-line tool; the Zenmap interface is a separate component. 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

Nmap

  • Primarily a command-line tool; the Zenmap interface is a separate component
  • A scanner only; it does not manage vulnerabilities or remediation
  • Uses the custom Nmap Public Source License, not a standard open source licence
  • Aggressive scans can trigger intrusion detection alerts on monitored networks
  • Windows scanning relies on the separately maintained Npcap driver

How much do Envoy and Nmap cost?

Envoy is free to use; Nmap 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.

Nmap

Free

No published plan breakdown. See the Nmap review.

Which should you pick?

Choose Envoy if

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

Choose Nmap if

  • You need host discovery.
  • You want to start without paying.
  • You work on Windows, macOS, Linux.
  • You also want tcp and udp port scanning.

Questions people ask

Is Envoy or Nmap better?
Neither clearly leads. Envoy starts at Free and Nmap at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Envoy or Nmap?
Envoy starts at Free and Nmap at Free.
Does Envoy or Nmap run on more platforms?
Envoy runs on Web. Nmap runs on Windows, macOS, Linux.
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 Nmap is typically brought in for.
What can Envoy do that Nmap cannot?
Envoy covers xDS dynamic configuration, Protocol breadth, Filter chain architecture, Observability by default. Nmap covers Host discovery, TCP and UDP port scanning, Service and version detection, Operating system detection.

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.

Nmap: Is Nmap free?

Yes. The project describes it as free and open source, with full source code included under the Nmap Public Source License.

Source
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.

Nmap: What platforms does Nmap run on?

The site lists official binary packages for Linux, Windows and macOS. Wikipedia says it began on Linux in 1997 and was later ported to Windows, macOS and BSD.

Source
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.

Nmap: What can Nmap detect?

It identifies live hosts, open ports, the services and versions behind them, operating systems and firewall behaviour. The manual also describes script scanning through the Nmap Scripting Engine.

Source
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.

Nmap: Which licence does Nmap use?

Wikipedia says it was under the GNU GPL originally and has used the custom Nmap Public Source License since version 7.90 in October 2020. The project also offers a separate proprietary OEM licence.

Source
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