Softwr

Developer Tools · head to head

Envoy vs Portkey

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

Portkey

APIs

Observe, govern, and secure every AI interaction across your enterprise

From
On request
Free plan
No

The short version

  • Envoy is free; Portkey prices on request.
  • Prices and features on this page were last checked on 20 November 2026.

How do Envoy and Portkey differ?

Envoy and Portkey differ on starting price (Free against On request), free tier (Yes against No) and category (Developer Tools against APIs). Only the attributes on which Envoy and Portkey actually diverge.

Attributes where Envoy and Portkey differ
AttributeEnvoyPortkey
Starting priceFreeOn request
Free tierYesNo
CategoryDeveloper ToolsAPIs

Identical on both: platforms (Web).

Not yet recorded: pricing model for Portkey.

Which features does each one have?

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

Nothing recorded that Envoy does not also cover.

What is each one used for?

Portkey is most often brought in for accessing 1,600+ language models through unified API gateway. 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 Portkey
  • An edge or API gateway that needs per-route retry budgets, circuit breaking and outlier detection rather than round-robin proxyingnot Portkey
  • Migrating traffic between service versions or between a monolith and its replacement, using weighted splits and shadow trafficnot Portkey
  • 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 Portkey

Portkey

  • Accessing 1,600+ language models through unified API gatewaynot Envoy
  • Monitoring and observing LLM behavior in production environmentsnot Envoy
  • Managing costs and setting budget limits for AI spendingnot Envoy
  • Implementing guardrails and PII redaction for secure AI interactionsnot Envoy

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

Portkey

  • The free Developer tier records only 10,000 logs per month with 3 day log retention; the $49 per month Production tier raises that to 100,000 logs with $9 per additional 100,000 requests, as of August 2026
  • The product is now sold to enterprises as Palo Alto Networks' Prisma AIRS AI Gateway, and the old pricing page redirects to Palo Alto content

How much do Envoy and Portkey cost?

Envoy is free to use. Plan by plan below, from each vendor's own pricing page.

Envoy

Free

No published plan breakdown. See the Envoy review.

Portkey

On request

No published plan breakdown. See the Portkey review.

Which should you pick?

Choose Envoy if

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

Choose Portkey if

Nothing in the data separates Portkey from Envoy on the points above - pick on price and on how each one feels to use.

Questions people ask

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

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.

Portkey: What happens if I exceed my Portkey plan's request limit?

Production tier ($49/month) charges $9 per additional 100,000 requests beyond the included 100,000. Enterprise customers have custom limits determined through their service agreement. Source: https://portkey.ai/pricing

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.

Portkey: Can I self-host Portkey to avoid per-request billing?

Yes. Portkey offers an Open Source self-hosted version with unlimited requests at no cost, including universal API, routing, guardrails, and load balancing features. Source: https://portkey.ai/pricing

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.

Portkey: How long does Portkey retain my logs and metrics?

Free Developer tier retains logs 3 days and metrics 30 days. Production tier retains logs 30 days and metrics 90 days. Enterprise tier offers custom retention periods. Source: https://portkey.ai/pricing

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.

Portkey: What compliance features are included in the Enterprise plan?

Enterprise tier includes SOC2 Type 2 certification, GDPR compliance, HIPAA compliance, VPC hosting, SSO, advanced guardrails, and dedicated support. Custom pricing required. Source: https://portkey.ai/pricing

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