Developer Tools · head to head
Envoy vs Heroku

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
The short version
- Heroku is a cloud platform as a service.
- Envoy is free; Heroku starts at $5/mo.
- Only Envoy lists xDS dynamic configuration; only Heroku lists git-based deployment.
- Where Heroku falls short: there is no free dyno tier; the cheapest Eco dyno is $5 per month.
- Prices and features on this page were last checked on 13 November 2026.
Where they differ
Only the attributes on which Envoy and Heroku actually diverge.
Not yet recorded: 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 Heroku
- Git-based deployment
- Buildpacks
- Dynos (containers)
- Add-ons marketplace
- Postgres database
- Environment variables
- Logging
- API
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 Heroku
- An edge or API gateway that needs per-route retry budgets, circuit breaking and outlier detection rather than round-robin proxyingnot Heroku
- Migrating traffic between service versions or between a monolith and its replacement, using weighted splits and shadow trafficnot Heroku
- 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 Heroku
Heroku
- Application hostingnot Envoy
- Database as a servicenot Envoy
- CI/CD pipelinesnot Envoy
- API deploymentnot 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
Heroku
- There is no free dyno tier; the cheapest Eco dyno is $5 per month
- Eco dynos sleep after 30 minutes of inactivity, are restricted to personal accounts and allow only 2 process types
- Free SSL and 10 process types start at the Basic dyno at $7 per month
- Private and Shield dyno types require a Private Space, which is billed on top of the dynos
- Private Space dynos start at $250 per month for Private-M and $500 per month for Private-L
- Dyno prices are per dyno per month, so an app with several process types multiplies the bill
Pricing, plan by plan
Envoy
FreeNo published plan breakdown. See the Envoy review.
Heroku
$5/month- Eco Dyno$5/mo
- 0.5 GB RAM
- Git/Docker deploy
- Custom domains
- Basic Dyno$7/mo
- 0.5 GB RAM
- Always-on
- Free SSL
- Standard-1X Dyno$25/mo
- 0.5 GB RAM
- Horizontal scaling
- App metrics
- Standard-2X Dyno$50/mo
- 1 GB RAM
- Horizontal scaling
- App metrics
Which should you pick?
Choose Envoy if
- You need xds dynamic configuration.
- You want to start without paying.
- You also want protocol breadth.
Choose Heroku if
- You need git-based deployment.
- You work on Web, API, Workers.
- You also want buildpacks.
Questions people ask
- Is Envoy or Heroku better?
- Neither clearly leads. Envoy starts at Free and Heroku at $5/month, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Envoy or Heroku?
- Envoy has a free tier; the other does not. Paid plans start at Free for Envoy and $5/month for Heroku.
- Does Envoy or Heroku run on more platforms?
- Envoy runs on Web. Heroku runs on Web, API, Workers.
- Can I use Envoy for free?
- Yes. Envoy has a free tier, so you can try it without paying. Heroku starts at $5/month.
- 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 Heroku is typically brought in for.
- What can Envoy do that Heroku cannot?
- Envoy covers xDS dynamic configuration, Protocol breadth, Filter chain architecture, Observability by default. Heroku covers Git-based deployment, Buildpacks, Dynos (containers), Add-ons marketplace.
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.
Heroku: How much does Heroku cost?
Heroku dyno pricing starts at $5 per month USD for the Eco tier (with 30-minute inactivity sleep), $7 per month for Basic (always-on), and scales up to $1,500 per month for Performance-2XL with 126 GB RAM.
SourceEnvoy: 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.
Heroku: What is the cheapest always-on Heroku plan?
The Basic Dyno at $7 per month USD is Heroku's cheapest always-on container option. It provides 0.5 GB RAM, free SSL, and support for 10 process types.
SourceEnvoy: 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.
Heroku: How is Heroku Postgres priced?
Heroku Postgres Essential tier (shared resources) starts at $5-$20 per month for 1-32 GB disk. Standard tier (dedicated) ranges $50-$12,000 per month. Premium, Private, Shield, and Advanced tiers offer higher performance at corresponding prices.
SourceEnvoy: 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.
Related pages
Other head to heads
- Envoy vs Istio
- Envoy vs Ona (formerly Gitpod)
- Envoy vs Spacelift
- Envoy vs Atlantis
- Envoy vs Jenkins
- Envoy vs Hookdeck
- Envoy vs Restate
- Envoy vs Helix
- Envoy vs Turborepo
- Envoy vs StackBlitz
- Envoy vs Webpack
- Envoy vs Backstage
- Envoy vs OpsLevel
- Envoy vs PartyKit
- Envoy vs PhpStorm
- Envoy vs Pieces for Developers
- Envoy vs RAD Studio
- Envoy vs Refact
- Envoy vs Coolify
- Envoy vs Neon
- Envoy vs Dokku
- Envoy vs DigitalOcean
- Envoy vs AWS (Amazon Web Services)
- Envoy vs Render
- Envoy vs Porter
- Envoy vs SST
- Envoy vs Encore
- Envoy vs Zeabur
- Envoy vs Railway
- Envoy vs Linode
- Envoy vs Cerebrium
- Envoy vs Grafana Cloud
- Envoy vs K3s
- Envoy vs Proxmox VE
- Envoy vs Upstash
- Envoy vs Rancher
- Heroku vs Istio
- Heroku vs Ona (formerly Gitpod)
- Heroku vs Spacelift
- Heroku vs Atlantis
- Heroku vs Jenkins
- Heroku vs Hookdeck
- Heroku vs Restate
- Heroku vs Helix
- Heroku vs Turborepo
- Heroku vs StackBlitz
- Heroku vs Webpack
- Heroku vs Backstage
- Heroku vs OpsLevel
- Heroku vs PartyKit
- Heroku vs PhpStorm
- Heroku vs Pieces for Developers
- Heroku vs RAD Studio
- Heroku vs Refact
- Heroku vs Coolify
- Heroku vs Neon
- Heroku vs Dokku
- Heroku vs DigitalOcean
- Heroku vs AWS (Amazon Web Services)
- Heroku vs Render
- Heroku vs Porter
- Heroku vs SST
- Heroku vs Encore
- Heroku vs Zeabur
- Heroku vs Railway
- Heroku vs Linode
- Heroku vs Cerebrium
- Heroku vs Grafana Cloud
- Heroku vs K3s
- Heroku vs Proxmox VE
- Heroku vs Upstash
- Heroku vs Rancher

