Softwr

Developer Tools · head to head

Envoy vs Teleport

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

Teleport

Cybersecurity

Certificate-based access to servers, Kubernetes, databases and apps, replacing shared credentials and VPNs

From
On request
Free plan
No

The short version

  • Envoy is free; Teleport prices on request.
  • Only Envoy lists xDS dynamic configuration; only Teleport lists short-lived certificates.
  • Prices and features on this page were last checked on 13 November 2026.

Where they differ

Only the attributes on which Envoy and Teleport actually diverge.

Attributes where Envoy and Teleport differ
AttributeEnvoyTeleport
Starting priceFreeOn request
Pricing modelOpen-sourceQuote
Free tierYesNo
PlatformsWebLinux, macOS, Windows, Self-hosted, Web
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 Teleport

  • Short-lived certificates
  • Protocol coverage
  • Session recording and replay
  • Access Requests
  • Device Trust
  • Identity provider integration
  • Machine identity
  • FIPS and FedRAMP builds

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

Teleport

  • Removing long-lived SSH keys and shared database passwords so that offboarding an engineer takes one action in the identity providernot Envoy
  • Producing session recordings and per-user database audit trails as direct evidence for SOC 2 or FedRAMPnot Envoy
  • Giving contractors or on-call engineers time-boxed, approved access to production instead of standing admin rightsnot Envoy
  • Replacing a flat VPN with per-resource authorisation across servers, Kubernetes and internal web appsnot 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

Teleport

  • Pricing is not published and is described as active users plus protected resources, so an autoscaling estate cannot forecast the bill and finance teams discover the true cost only after the first true-up
  • The proxy is a hard dependency on reaching production, so it needs its own high availability deployment and a tested break-glass path or an outage in Teleport becomes an outage in your ability to respond to outages
  • The open source Community Edition omits Access Requests, Device Trust and the FIPS builds, which are exactly the controls an auditor asks about, so the free tier rarely survives a compliance review
  • Self-hosting means running and upgrading a certificate authority and its backing store, and Teleport releases frequently enough that upgrade work becomes a standing operational commitment
  • Coverage across protocols is uneven in depth, so teams with legacy systems, unusual databases or bespoke network appliances find gaps that still require the old VPN to remain in place alongside it

Pricing, plan by plan

Envoy

Free

No published plan breakdown. See the Envoy review.

Teleport

On request
  • Teleport Community EditionOn request
    • Open source, self-hosted
    • SSH, Kubernetes, database and app access
    • Session recording
  • Teleport EnterpriseOn request
    • Cloud-hosted or self-hosted
    • Access Requests and approval workflow
    • Device Trust and hardware key enforcement

Which should you pick?

Choose Envoy if

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

Choose Teleport if

  • You need short-lived certificates.
  • You work on Linux, macOS, Windows, Self-hosted, Web.
  • You also want protocol coverage.

Questions people ask

Is Envoy or Teleport better?
Neither clearly leads. Envoy starts at Free and Teleport at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Envoy or Teleport?
Envoy has a free tier; the other does not. Paid plans start at Free for Envoy and On request for Teleport.
Does Envoy or Teleport run on more platforms?
Envoy runs on Web. Teleport runs on Linux, macOS, Windows, Self-hosted, Web.
Can I use Envoy for free?
Yes. Envoy has a free tier, so you can try it without paying. Teleport 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 Teleport is typically brought in for.
What can Envoy do that Teleport cannot?
Envoy covers xDS dynamic configuration, Protocol breadth, Filter chain architecture, Observability by default. Teleport covers Short-lived certificates, Protocol coverage, Session recording and replay, Access Requests.

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.

Teleport: Is the open source edition usable in production?

Yes, but it lacks Access Requests, Device Trust and FIPS builds, which most compliance programmes end up requiring.

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.

Teleport: How is it priced?

Not publicly. The vendor prices on active users and protected resources and provides a quote after a sales conversation.

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.

Teleport: What happens if Teleport goes down?

Nobody reaches the resources behind it, so you need a highly available deployment and a documented break-glass procedure.

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.

Teleport: Does it replace our VPN?

For anything you put behind it, yes. Legacy systems and appliances it does not support will keep the VPN alive.

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