Softwr

Cybersecurity · head to head

Dahua Technology vs Envoy

Dahua Technology logo

Dahua Technology

Cybersecurity

Large Chinese video platform that US federal buyers and federal contractors cannot lawfully use

From
On request
Free plan
No
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

The short version

  • Envoy is free; Dahua Technology prices on request.
  • Only Dahua Technology lists DSS Pro V8; only Envoy lists xDS dynamic configuration.
  • Prices and features on this page were last checked on 13 November 2026.

Where they differ

Only the attributes on which Dahua Technology and Envoy actually diverge.

Attributes where Dahua Technology and Envoy differ
AttributeDahua TechnologyEnvoy
Starting priceOn requestFree
Pricing modelQuoteOpen-source
Free tierNoYes
PlatformsWindows, Linux, Web, iOS, AndroidWeb
CategoryCybersecurityDeveloper Tools

What each one covers

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 Dahua Technology

  • DSS Pro V8
  • Distributed architecture
  • DeepXplore
  • Access management
  • Parking Lot application
  • Intelligent Analysis
  • Maintenance Center
  • DMSS mobile app

Only in Envoy

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

What people use each for

The jobs each tool is most often brought in to do.

Dahua Technology

  • A private industrial site outside the United States with no federal or defence supply chain exposurenot Envoy
  • A large-channel-count deployment in a market where Section 889 and the FCC Covered List do not applynot Envoy
  • An existing Dahua estate authorised before February 2023 being maintained rather than expandednot Envoy
  • A buyer who has taken written legal advice confirming no federal contracting exposure now or in futurenot Envoy

Envoy

  • Acting as the data plane under a service mesh or Gateway API implementation, which is how the overwhelming majority of deployments use itnot Dahua Technology
  • An edge or API gateway that needs per-route retry budgets, circuit breaking and outlier detection rather than round-robin proxyingnot Dahua Technology
  • Migrating traffic between service versions or between a monolith and its replacement, using weighted splits and shadow trafficnot Dahua Technology
  • 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 Dahua Technology

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Dahua Technology

  • Dahua is named under NDAA Section 889 and listed on the FCC Covered List, so the US federal government cannot procure its video surveillance equipment and cannot contract with entities that use it, which disqualifies most organisations with any federal contracting ambition regardless of how good the software is
  • Rules adopted by the FCC in late 2025 gave the Commission authority to revoke equipment authorisations already granted, so equipment that is legal to sell today may not be tomorrow and a multi-year rollout carries regulatory risk the vendor cannot indemnify
  • Sourcing has degraded sharply: new equipment, replacement parts and system expansions are increasingly difficult to obtain through compliant US distribution and major retailers have removed listings, so an installed estate faces a spares problem long before end of life
  • Any organisation that later wins or bids for federal work, or supplies a federal contractor, must audit and replace Dahua equipment across all its facilities under Section 889(a)(1)(B), turning a cheap installation into an expensive forced rip-out
  • Beyond procurement law, insurers, auditors and enterprise customers increasingly treat Chinese-manufactured surveillance as a supply chain finding in its own right, so the reputational cost lands even where the legal prohibition does not

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

Pricing, plan by plan

Dahua Technology

On request
  • DSS Pro V8On request
    • Base video licence covering 16 channels, required before adding more
    • Additional video channel licences purchased per channel
    • Access control, video intercom and parking licensed separately

Envoy

Free

No published plan breakdown. See the Envoy review.

Which should you pick?

Choose Dahua Technology if

  • You need dss pro v8.
  • You work on Windows, Linux, Web, iOS, Android.
  • You also want distributed architecture.

Choose Envoy if

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

Questions people ask

Is Dahua Technology or Envoy better?
Neither clearly leads. Dahua Technology starts at On request and Envoy at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Dahua Technology or Envoy?
Envoy has a free tier; the other does not. Paid plans start at On request for Dahua Technology and Free for Envoy.
Does Dahua Technology or Envoy run on more platforms?
Dahua Technology runs on Windows, Linux, Web, iOS, Android. Envoy runs on Web.
Can I use Envoy for free?
Yes. Envoy has a free tier, so you can try it without paying. Dahua Technology starts at On request.
What is Dahua Technology best used for?
Dahua Technology is most often used for a private industrial site outside the united states with no federal or defence supply chain exposure, a large-channel-count deployment in a market where section 889 and the fcc covered list do not apply, an existing dahua estate authorised before february 2023 being maintained rather than expanded, a buyer who has taken written legal advice confirming no federal contracting exposure now or in future. Of those, a private industrial site outside the united states with no federal or defence supply chain exposure and a large-channel-count deployment in a market where section 889 and the fcc covered list do not apply are not what Envoy is typically brought in for.
What can Dahua Technology do that Envoy cannot?
Dahua Technology covers DSS Pro V8, Distributed architecture, DeepXplore, Access management. Envoy covers xDS dynamic configuration, Protocol breadth, Filter chain architecture, Observability by default.

Answered from the vendors’ own pages

Dahua Technology: Can a US federal agency buy Dahua?

No. Dahua is explicitly named under NDAA Section 889, so federal agencies cannot procure or obtain its video surveillance equipment, including OEM-rebadged versions.

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.

Dahua Technology: Can a private US company use Dahua cameras?

Section 889 does not directly regulate private companies without federal contracts, and existing installations are not required to be removed. But the moment the company bids for federal work or supplies a federal contractor, Section 889(a)(1)(B) makes the installed equipment a problem.

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.

Dahua Technology: Is existing Dahua equipment banned?

No. The prohibition on new authorisations does not apply retroactively to equipment authorised before February 2023, and legacy systems may remain in use. New purchases and expansions are the restricted part.

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.

Dahua Technology: Is Dahua available outside the United States?

Yes, and it remains one of the two largest manufacturers globally, though a number of other countries have introduced their own restrictions on government use.

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