Softwr

Developer Tools · head to head

Envoy vs Red Hat OpenShift

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
Red Hat OpenShift logo

Red Hat OpenShift

Cloud

Kubernetes-based application platform sold as self-managed editions and managed cloud services

From
$0.076/hour
Free plan
No

The short version

  • Envoy is free; Red Hat OpenShift starts at $0.076/mo.
  • Only Envoy lists xDS dynamic configuration; only Red Hat OpenShift lists kubernetes-based application platform.
  • Where Red Hat OpenShift falls short: self-managed edition prices are not published and need a quote.
  • Prices and features on this page were last checked on 20 November 2026.

How do Envoy and Red Hat OpenShift differ?

Envoy and Red Hat OpenShift differ on starting price (Free against $0.076/hour), pricing model (Open-source against Subscription) and free tier (Yes against No). Only the attributes on which Envoy and Red Hat OpenShift actually diverge.

Attributes where Envoy and Red Hat OpenShift differ
AttributeEnvoyRed Hat OpenShift
Starting priceFree$0.076/hour
Pricing modelOpen-sourceSubscription
Free tierYesNo
PlatformsWebWeb, Linux
CategoryDeveloper ToolsCloud

Not yet recorded: founded for Envoy.

Which features does each one have?

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

  • Kubernetes-based application platform
  • Managed services on AWS, Azure, Google Cloud and IBM Cloud
  • Self-managed editions for datacentre or cloud
  • OpenShift GitOps and Pipelines for CI/CD
  • OpenShift Virtualization for virtual machines
  • OpenShift Serverless and Service Mesh
  • OpenShift AI for AI workloads

What is each one used for?

Red Hat OpenShift is most often brought in for running enterprise Kubernetes on premises. 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 Red Hat OpenShift
  • An edge or API gateway that needs per-route retry budgets, circuit breaking and outlier detection rather than round-robin proxyingnot Red Hat OpenShift
  • Migrating traffic between service versions or between a monolith and its replacement, using weighted splits and shadow trafficnot Red Hat OpenShift
  • 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 Red Hat OpenShift

Red Hat OpenShift

  • Running enterprise Kubernetes on premisesnot Envoy
  • Managed Kubernetes on AWS or Azurenot Envoy
  • Migrating virtual machines to containersnot Envoy
  • CI/CD with GitOps pipelinesnot Envoy
  • Hybrid cloud application platformsnot Envoy

Where do Envoy and Red Hat OpenShift fall short?

Red Hat OpenShift's most cited limit: self-managed edition prices are not published and need a quote. 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

Red Hat OpenShift

  • Self-managed edition prices are not published and need a quote
  • The 0.076 dollars per hour price assumes a three-year reserved contract
  • Subscription cost and complexity exceed plain Kubernetes for small teams
  • Managed services are billed by cloud providers, so costs are split across vendors

How much do Envoy and Red Hat OpenShift cost?

Envoy is free to use; Red Hat OpenShift starts at $0.076/mo. Plan by plan below, from each vendor's own pricing page.

Envoy

Free

No published plan breakdown. See the Envoy review.

Red Hat OpenShift

$0.076/hour
  • Managed cloud reserved instances (from)$0.076/hour
  • Self-managed editionsOn request

Which should you pick?

Choose Envoy if

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

Choose Red Hat OpenShift if

  • You need kubernetes-based application platform.
  • You work on Web, Linux.
  • You also want managed services on aws, azure, google cloud and ibm cloud.

Questions people ask

Is Envoy or Red Hat OpenShift better?
Neither clearly leads. Envoy starts at Free and Red Hat OpenShift at $0.076/hour, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Envoy or Red Hat OpenShift?
Envoy has a free tier; the other does not. Paid plans start at Free for Envoy and $0.076/hour for Red Hat OpenShift.
Does Envoy or Red Hat OpenShift run on more platforms?
Envoy runs on Web. Red Hat OpenShift runs on Web, Linux.
Can I use Envoy for free?
Yes. Envoy has a free tier, so you can try it without paying. Red Hat OpenShift starts at $0.076/hour.
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 Red Hat OpenShift is typically brought in for.
What can Envoy do that Red Hat OpenShift cannot?
Envoy covers xDS dynamic configuration, Protocol breadth, Filter chain architecture, Observability by default. Red Hat OpenShift covers Kubernetes-based application platform, Managed services on AWS, Azure, Google Cloud and IBM Cloud, Self-managed editions for datacentre or cloud, OpenShift GitOps and Pipelines for CI/CD.

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.

Red Hat OpenShift: What deployment options does OpenShift have?

Managed services on AWS, Azure, Google Cloud and IBM Cloud, and self-managed editions such as Container Platform and Platform Plus. Managed options are jointly run with the cloud provider.

Source
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.

Red Hat OpenShift: How much does OpenShift cost?

Red Hat lists reserved managed instances from 0.076 US dollars per hour on a three-year contract. Self-managed editions have no published list price.

Source
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.

Red Hat OpenShift: Is there an open source version?

The community upstream is OKD, licensed under Apache 2.0. OpenShift itself is listed as a commercial product.

Source
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.

Red Hat OpenShift: Can I try it first?

Red Hat lists a Developer Sandbox, a self-managed trial and a free eight-hour ROSA hands-on experience. Trials of the managed and self-managed products are listed on the pricing page.

Source
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