Softwr

Developer Tools · head to head

Envoy vs Neon

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

Neon

Cloud

Serverless Postgres for modern developers

From
Free
Free plan
Yes
Visit NeonFull review

The short version

  • Neon is a fully managed serverless PostgreSQL database.
  • Envoy is free; Neon starts at $15/mo.
  • Only Envoy lists xDS dynamic configuration; only Neon lists serverless PostgreSQL.
  • Where Neon falls short: compute pricing at $0.106-$0.222/CU-hour means costs scale directly with workload, unlike fixed-price alternatives.
  • Prices and features on this page were last checked on 13 November 2026.

Where they differ

Only the attributes on which Envoy and Neon actually diverge.

Attributes where Envoy and Neon differ
AttributeEnvoyNeon
CategoryDeveloper ToolsCloud

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

Not yet recorded: pricing model for Neon, 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 Neon

  • Serverless PostgreSQL
  • Database Branching
  • Autoscaling
  • Bottomless Storage
  • Point-in-time Recovery
  • Connection Pooling
  • Read Replicas
  • Instant Cloning

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

Neon

  • Serverless applicationsnot Envoy
  • Development databasesnot Envoy
  • Preview environmentsnot Envoy
  • Testingnot 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

Neon

  • Compute pricing at $0.106-$0.222/CU-hour means costs scale directly with workload, unlike fixed-price alternatives
  • Separation of compute and storage may add complexity to cost prediction compared to all-in-one plans

Pricing, plan by plan

Envoy

Free

No published plan breakdown. See the Envoy review.

Neon

Free
  • FreeFree
    • 100 CU-hours/month
    • 0.5 GB storage
    • 1 project
  • Launch$15/mo
    • Pay-as-you-go compute
    • $0.35/GB storage
    • Multiple projects
  • Scale$31/mo
    • Higher compute rates
    • 99.95% SLA
    • HIPAA compliance

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

  • You need serverless postgresql.
  • You want to start without paying.
  • You also want database branching.
Neon review

Questions people ask

Is Envoy or Neon better?
Neither clearly leads. Envoy starts at Free and Neon at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Envoy or Neon?
Envoy starts at Free and Neon at Free.
Does Envoy or Neon run on more platforms?
Both run on Web, so platform support will not decide this one for you.
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 Neon is typically brought in for.
What can Envoy do that Neon cannot?
Envoy covers xDS dynamic configuration, Protocol breadth, Filter chain architecture, Observability by default. Neon covers Serverless PostgreSQL, Database Branching, Autoscaling, Bottomless Storage.

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.

Neon: What is Neon and what makes it different?

Neon is a serverless PostgreSQL database that separates compute and storage, enabling automatic scaling and instant database branching. After acquisition by Databricks in May 2025, pricing has been significantly reduced.

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.

Neon: Does Neon offer a free tier?

Yes, Neon's free tier includes 100 compute units per month and 0.5 GB of storage. This is suitable for development and small projects.

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.

Neon: What are the paid plans and pricing for Neon?

Neon offers consumption-based pricing on Launch ($0.106/CU-hour, approximately $15/month) and Scale ($0.222/CU-hour, approximately $31/month) plans with separate storage billing at $0.35/GB-month. No monthly minimum required.

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.

Neon: What features does Neon provide?

Neon includes git-like branching for database copies, point-in-time recovery, data anonymization for testing, managed authentication, serverless functions, and object storage that branches with projects.

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.

Neon: What compliance and reliability guarantees does Neon provide?

Neon's Scale tier offers 99.95% uptime SLA, HIPAA compliance, SOC2 certification, and private networking via PrivateLink at no extra cost.

Source
Share

Related pages

More on Envoy

More on Neon

Keep looking

Other head to heads