Softwr

Developer Tools · head to head

Envoy vs Envysion

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
Visit EnvoyFull review
Envysion logo

Envysion

Cybersecurity

Managed video for restaurants and convenience stores that pairs camera footage with point of sale transaction data

From
On request
Free plan
No
Visit EnvysionFull review

The short version

  • Envoy is free; Envysion prices on request.
  • Only Envoy lists xDS dynamic configuration; only Envysion lists point of sale exception reporting.
  • Prices and features on this page were last checked on 13 November 2026.

Where they differ

Only the attributes on which Envoy and Envysion actually diverge.

Attributes where Envoy and Envysion differ
AttributeEnvoyEnvysion
Starting priceFreeOn request
Pricing modelOpen-sourceQuote
Free tierYesNo
PlatformsWebWeb, 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 Envysion

  • Point of sale exception reporting
  • Cloud video review
  • Audio capture
  • Loss prevention case management
  • Operational auditing
  • Multi-site dashboards
  • Franchise access controls
  • Managed service model

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

Envysion

  • A 300-store quick service chain where till voids and refunds are a known shrink channelnot Envoy
  • A convenience retailer needing drive-through audio and video to settle a customer disputenot Envoy
  • A franchisor auditing food safety and uniform compliance across franchisee sites remotelynot Envoy
  • An investigator building an evidence package for a termination that will be challengednot 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

Envysion

  • Envysion now sits inside Motorola Solutions alongside Avigilon and Pelco, which overlap with it in retail video, so buyers should establish which platform Motorola intends to invest in before committing to a multi-year multi-site agreement
  • Point of sale integration is per till system, so a chain running two or three POS platforms across acquired brands may find exception reporting works properly in only some of its stores
  • No pricing is published and it is sold as a per-site managed service, usually on a multi-year agreement, so a chain closing or refranchising stores mid-term can be paying for locations it no longer operates
  • It is built specifically for till-level retail and restaurant loss prevention and is a poor fit for campus, industrial or office security, so an operator with a mixed estate needs a second platform for the head office
  • Each site typically needs recording hardware installed, which makes rollout an install project per location rather than a software subscription, and refreshing that hardware is a periodic capital event the subscription does not cover

Pricing, plan by plan

Envoy

Free

No published plan breakdown. See the Envoy review.

Envysion

On request
  • Envysion managed videoOn request
    • Priced per site as a managed service
    • Recording hardware typically required in each location
    • Point of sale integration scoped per till system

Which should you pick?

Choose Envoy if

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

Choose Envysion if

  • You need point of sale exception reporting.
  • You work on Web, iOS, Android.
  • You also want cloud video review.
Envysion review

Questions people ask

Is Envoy or Envysion better?
Neither clearly leads. Envoy starts at Free and Envysion at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Envoy or Envysion?
Envoy has a free tier; the other does not. Paid plans start at Free for Envoy and On request for Envysion.
Does Envoy or Envysion run on more platforms?
Envoy runs on Web. Envysion runs on Web, iOS, Android.
Can I use Envoy for free?
Yes. Envoy has a free tier, so you can try it without paying. Envysion 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 Envysion is typically brought in for.
What can Envoy do that Envysion cannot?
Envoy covers xDS dynamic configuration, Protocol breadth, Filter chain architecture, Observability by default. Envysion covers Point of sale exception reporting, Cloud video review, Audio capture, Loss prevention case management.

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.

Envysion: Who owns Envysion?

Motorola Solutions. It sits in the same video security portfolio as Avigilon, Pelco and Openpath.

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.

Envysion: What makes it different from a cloud camera service?

The point of sale integration. Exception reports link a void, refund or discount directly to the clip of that transaction, which is what makes multi-site review practical.

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.

Envysion: Is pricing published?

No. It is quoted per site as a managed service, typically on a multi-year agreement.

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.

Envysion: Will it work with my point of sale system?

Integration is built per POS platform, so confirm your specific system and version before buying, especially across acquired brands.

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

More on Envoy

More on Envysion

Keep looking

Other head to heads