Softwr

Developer Tools · head to head

Envoy vs Upstash

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

Upstash

Cloud

Serverless data for modern developers

From
Free
Free plan
Yes
Visit UpstashFull review

The short version

  • Envoy is free; Upstash starts at $10/mo.
  • Only Envoy lists xDS dynamic configuration; only Upstash lists serverless Redis.
  • Where Upstash falls short: HTTP-based REST API only, no TCP connections means higher latency than self-hosted or connection-pooled Redis.
  • Prices and features on this page were last checked on 13 November 2026.

Where they differ

Only the attributes on which Envoy and Upstash actually diverge.

Attributes where Envoy and Upstash differ
AttributeEnvoyUpstash
PlatformsWebAPI, Vercel Edge, Web, AWS Lambda
CategoryDeveloper ToolsCloud

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

Not yet recorded: pricing model for Upstash, founded for Envoy.

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 Upstash

  • Serverless Redis
  • Serverless Kafka
  • QStash
  • Global Replication
  • REST API
  • Edge Functions Support
  • Rate Limiting
  • Caching

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

Upstash

  • Cachingnot Envoy
  • Session storagenot Envoy
  • Real-time messagingnot Envoy
  • Rate limitingnot Envoy
  • Serverless backendsnot 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

Upstash

  • HTTP-based REST API only, no TCP connections means higher latency than self-hosted or connection-pooled Redis
  • Rate limiting occurs when traffic exceeds configured budget cap or request limits
  • Kafka service discontinued in March 2025, requiring migration to Upstash Workflow or alternatives
  • Limited Redis feature support compared to self-hosted Redis or Redis Cloud
  • High-request-volume workloads can accumulate significant costs due to per-request pricing model

Pricing, plan by plan

Envoy

Free

No published plan breakdown. See the Envoy review.

Upstash

Free
  • FreeFree
    • 256 MB data
    • 500K commands per month
    • 10 GB bandwidth
  • Pay-as-you-go$0.2
    • Per-request billing
    • Storage at $0.25/GB
    • Unlimited commands
  • Fixed Plan$10/mo
    • 250 MB Redis
    • Predictable pricing
    • Global replication available at higher tiers

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 Upstash if

  • You need serverless redis.
  • You want to start without paying.
  • You work on API, Vercel Edge, Web, AWS Lambda.
  • You also want serverless kafka.
Upstash review

Questions people ask

Is Envoy or Upstash better?
Neither clearly leads. Envoy starts at Free and Upstash at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Envoy or Upstash?
Envoy starts at Free and Upstash at Free.
Does Envoy or Upstash run on more platforms?
Envoy runs on Web. Upstash runs on API, Vercel Edge, Web, AWS Lambda.
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 Upstash is typically brought in for.
What can Envoy do that Upstash cannot?
Envoy covers xDS dynamic configuration, Protocol breadth, Filter chain architecture, Observability by default. Upstash covers Serverless Redis, Serverless Kafka, QStash, Global Replication.

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.

Upstash: Does Upstash have a free tier?

Yes. The free tier provides 256 MB of data and 500,000 commands per month with 10 GB of bandwidth in a single region, no credit card required.

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.

Upstash: How does Upstash work with edge platforms like Vercel and Cloudflare Workers?

Upstash uses a REST API instead of TCP connections, enabling it to work from Vercel Edge, Cloudflare Workers, and AWS Lambda without persistent connections or connection pooling.

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.

Upstash: What programming languages are supported?

Upstash provides native SDKs for Python, Node.js, Go, and Rust. Java, C#, and PHP developers can use the REST API or community libraries.

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.

Upstash: Is Upstash Kafka still available?

No. Upstash Kafka was deprecated on September 11, 2024 and fully discontinued on March 11, 2025. Upstash Workflow is now recommended for durable serverless messaging and task queuing.

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.

Upstash: How is Upstash pricing structured?

Upstash uses per-request pricing at $0.20 per 100K commands for Redis, $0.25/GB for storage, and $0.40 per 100K requests for Vector database. Idle applications cost nothing.

Source
Upstash: Can Upstash be used with AWS Lambda?

Yes. Upstash works with AWS Lambda via its REST API, eliminating the need for connection pooling and making it ideal for stateless serverless functions.

Source
Share

Related pages

More on Envoy

More on Upstash

Keep looking

Other head to heads