Softwr

Developer Tools · head to head

Envoy vs OpenVPN

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

OpenVPN

Networking

Open source VPN protocol with a commercial Access Server product priced per simultaneous connection

From
Free
Free plan
Yes

The short version

  • Envoy is free; OpenVPN starts at $7/mo.
  • Only Envoy lists xDS dynamic configuration; only OpenVPN lists open source core.
  • Where OpenVPN falls short: open source OpenVPN, while free, requires real technical skill to configure, secure and maintain without the Access Server admin layer.
  • Prices and features on this page were last checked on 20 November 2026.

How do Envoy and OpenVPN differ?

Envoy and OpenVPN differ on pricing model, platforms and category (Developer Tools against Networking). Only the attributes on which Envoy and OpenVPN actually diverge.

Attributes where Envoy and OpenVPN differ
AttributeEnvoyOpenVPN
Pricing modelOpen-sourceOpen source core is free; Access Server billed per simultaneous connection
PlatformsWebLinux, Windows, macOS, iOS, Android
CategoryDeveloper ToolsNetworking

Identical on both: starting price (Free), free tier (Yes).

Which features does each one have?

They share no listed features; 8 appear only for Envoy and 5 only for OpenVPN. 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 OpenVPN

  • Open source core
  • Access Server admin UI
  • Per-connection licensing
  • Free tier
  • Cross-platform clients

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

OpenVPN

  • A technical team wanting a fully free, self-configured VPN server using the open source protocol without any vendor relationshipnot Envoy
  • A small business wanting a supported, easier-to-administer VPN server, willing to pay per concurrent connection rather than per employeenot Envoy
  • An organisation with more staff than typical concurrent VPN usage, since Access Server bills only active simultaneous connections, not total accountsnot Envoy
  • An IoT or large-scale deployment needing custom Enterprise pricing above 2,000 connectionsnot Envoy

Where do Envoy and OpenVPN fall 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

OpenVPN

  • Open source OpenVPN, while free, requires real technical skill to configure, secure and maintain without the Access Server admin layer
  • Per-connection billing on Access Server means usage spikes, such as an all-hands remote day, can push simultaneous connections over a licensed limit and block new connections until usage drops or the plan is upgraded
  • OpenVPN's traditional hub-and-spoke architecture routes traffic through a central server, unlike mesh VPN tools like Tailscale or NetBird that establish direct peer-to-peer connections where possible, which can add latency
  • Client configuration and certificate management for the open source version is more manual and error-prone than newer VPN tools with zero-config onboarding
  • Access Server pricing above the Growth tier reverts to custom Enterprise quoting, so very large deployments lose the pricing transparency of the lower tiers
  • The protocol's throughput is generally lower than newer kernel-integrated protocols like WireGuard under equivalent conditions, which matters for high-bandwidth use cases

How much do Envoy and OpenVPN cost?

Envoy is free to use; OpenVPN has a free plan, with paid plans from $7/mo. Plan by plan below, from each vendor's own pricing page.

Envoy

Free

No published plan breakdown. See the Envoy review.

OpenVPN

Free
  • Access Server FreeFree
    • Up to 2 simultaneous connections
    • All features included
  • Access Server Growth$7/mo
    • Per simultaneous connection beyond the free tier
    • Annual billing
  • Access Server Enterprise/IoTOn request
    • Custom pricing for 2,000+ connections

Which should you pick?

Choose Envoy if

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

Choose OpenVPN if

  • You need open source core.
  • You want to start without paying.
  • You work on Linux, Windows, macOS, iOS, Android.
  • You also want access server admin ui.

Questions people ask

Is Envoy or OpenVPN better?
Neither clearly leads. Envoy starts at Free and OpenVPN at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Envoy or OpenVPN?
Envoy starts at Free and OpenVPN at Free.
Does Envoy or OpenVPN run on more platforms?
Envoy runs on Web. OpenVPN runs on Linux, Windows, macOS, iOS, Android.
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 OpenVPN is typically brought in for.
What can Envoy do that OpenVPN cannot?
Envoy covers xDS dynamic configuration, Protocol breadth, Filter chain architecture, Observability by default. OpenVPN covers Open source core, Access Server admin UI, Per-connection licensing, Free tier.

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.

OpenVPN: Is OpenVPN free?

The open source protocol and software are free under the GPL; Access Server, the commercial packaged product, charges per simultaneous connection beyond a free 2-connection tier.

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.

OpenVPN: What counts as a connection for billing purposes?

A simultaneously active connected device, not a registered user account or total device count; unlimited accounts and devices can be created but only the licensed number can be connected at once.

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.

OpenVPN: How does OpenVPN compare with WireGuard-based tools like Tailscale?

OpenVPN uses a traditional hub-and-spoke VPN architecture rather than the mesh, peer-to-peer approach used by newer tools like Tailscale or NetBird.

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