Softwr

Developer Tools · head to head

Envoy vs Salient CompleteView

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
Salient CompleteView logo

Salient CompleteView

Cybersecurity

Per-camera licensed video management software with unlimited client workstations

From
On request
Free plan
No

The short version

  • Envoy is free; Salient CompleteView prices on request.
  • Only Envoy lists xDS dynamic configuration; only Salient CompleteView lists one licence per camera.
  • Prices and features on this page were last checked on 13 November 2026.

Where they differ

Only the attributes on which Envoy and Salient CompleteView actually diverge.

Attributes where Envoy and Salient CompleteView differ
AttributeEnvoySalient CompleteView
Starting priceFreeOn request
Pricing modelOpen-sourceQuote
Free tierYesNo
PlatformsWebWindows, Web, iOS, Android
CategoryDeveloper ToolsCybersecurity

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 Envoy

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

Only in Salient CompleteView

  • One licence per camera
  • Open camera support
  • Perpetual or subscription
  • Recording server architecture
  • Video wall
  • Cloud Services
  • Forensic search
  • First responder access

What people use each 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 Salient CompleteView
  • An edge or API gateway that needs per-route retry budgets, circuit breaking and outlier detection rather than round-robin proxyingnot Salient CompleteView
  • Migrating traffic between service versions or between a monolith and its replacement, using weighted splits and shadow trafficnot Salient CompleteView
  • 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 Salient CompleteView

Salient CompleteView

  • A school district where dozens of administrators and resource officers need viewing access without per-seat licencesnot Envoy
  • A hospital campus consolidating legacy recorders under one recording architecturenot Envoy
  • A city department needing first responder access to specific cameras during an incidentnot Envoy
  • An integrator deploying a mid-sized site where an enterprise VMS would be over-engineerednot Envoy

Where each one falls 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

Salient CompleteView

  • The third-party integration ecosystem is much smaller than Milestone's, so a specialist analytics, LPR or access control requirement is more likely to need custom integration work
  • It is Windows server based with a conventional recording architecture, so it carries the server, storage and maintenance burden that cloud-native competitors remove entirely
  • International presence is limited and the channel is concentrated in North America, so buyers elsewhere face thin support and few experienced integrators
  • No current pricing is published; distribution list prices circulate but the actual number depends on the integrator, which makes competitive comparison slow
  • Brand recognition is lower than the market leaders, which matters in public procurement where specifications are sometimes written around a named competitor and a substitution has to be argued

Pricing, plan by plan

Envoy

Free

No published plan breakdown. See the Envoy review.

Salient CompleteView

On request
  • CompleteViewOn request
    • One licence per IP camera, sold through distribution
    • No charge or licence for client workstations, unlimited clients
    • Perpetual and subscription licensing both available

Which should you pick?

Choose Envoy if

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

Choose Salient CompleteView if

  • You need one licence per camera.
  • You work on Windows, Web, iOS, Android.
  • You also want open camera support.

Questions people ask

Is Envoy or Salient CompleteView better?
Neither clearly leads. Envoy starts at Free and Salient CompleteView at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Envoy or Salient CompleteView?
Envoy has a free tier; the other does not. Paid plans start at Free for Envoy and On request for Salient CompleteView.
Does Envoy or Salient CompleteView run on more platforms?
Envoy runs on Web. Salient CompleteView runs on Windows, Web, iOS, Android.
Can I use Envoy for free?
Yes. Envoy has a free tier, so you can try it without paying. Salient CompleteView starts at On request.
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 Salient CompleteView is typically brought in for.
What can Envoy do that Salient CompleteView cannot?
Envoy covers xDS dynamic configuration, Protocol breadth, Filter chain architecture, Observability by default. Salient CompleteView covers One licence per camera, Open camera support, Perpetual or subscription, Recording server architecture.

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.

Salient CompleteView: Do I pay for client workstations?

No. CompleteView licenses one licence per IP camera with no additional charge or licence for clients and no limit on the number of client workstations.

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.

Salient CompleteView: Is licensing perpetual or subscription?

Both are offered. Perpetual suits capital budgets; subscription suits organisations that prefer operating expenditure.

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.

Salient CompleteView: Does it have a cloud option?

Yes, Salient Cloud Services, with free registration for an asset dashboard and paid upgrades for remote access, monitoring and first responder connectivity.

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.

Salient CompleteView: What version is current?

CompleteView 8.0 is the current release line.

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