Softwr

Technology · head to head

Envoy vs Segment

Envoy logo

Envoy

Technology

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
Rated
-
Full reviewWebsite
Segment logo

Segment

Technology

Customer data platform that unifies your data

From
Free
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: 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.; Segment pricing is not transparent; requires sales contact for quotes
  • They diverge on capability: Envoy covers xDS dynamic configuration, Segment covers Data collection.
  • Prices and features above were last checked on 30 August 2026.

Where they differ

Only the attributes on which Envoy and Segment actually diverge.

Attributes where Envoy and Segment differ
AttributeEnvoySegment
Pricing modelopen-sourceUnknown
PlatformsWebWeb, API
FoundedUnknown2011

Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated), category (Technology).

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 Segment

  • Data collection
  • Data routing
  • Data warehouse
  • Identity resolution
  • Protocols
  • Privacy portal
  • Functions
  • Replay

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

Segment

  • Customer data unificationnot Envoy
  • Marketing attributionnot Envoy
  • Product analyticsnot Envoy
  • Data governancenot Envoy
  • Personalizationnot 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.

Segment

  • Pricing is not transparent; requires sales contact for quotes
  • No lower-tier option for small businesses without contacting sales
  • Custom pricing can be expensive for mid-market companies
  • Now owned by Twilio, which affects long-term independence and focus

Pricing, plan by plan

Envoy

Free

No published plan breakdown. See the Envoy review.

Segment

Free

No published plan breakdown. See the Segment review.

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

  • You need data collection.
  • You want to start without paying.
  • You work on Web, API.
  • You also want data routing.
Segment review

Questions people ask

Is Envoy or Segment better?
Neither clearly leads. Envoy starts at Free and Segment at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Envoy or Segment?
Envoy starts at Free and Segment at Free.
Does Envoy or Segment run on more platforms?
Envoy runs on Web. Segment runs on Web, API.
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 Segment is typically brought in for.
What can Envoy do that Segment cannot?
Envoy covers xDS dynamic configuration, Protocol breadth, Filter chain architecture, Observability by default. Segment covers Data collection, Data routing, Data warehouse, Identity resolution.

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.

Segment: Does Segment have a free plan?

Segment uses a freemium model with 10K users included free. Additional users require paid plans based on monthly active users (MTUs), calculated as monthly active users plus anonymous visitors per month.

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.

Segment: What is Segment's pricing based on?

Segment pricing is based on monthly active users (MTU), which equals your monthly active users plus anonymous visitors. Pricing is customized; contact sales for specific quotes.

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.

Segment: What is the difference between Customer Data Pipeline and Customer Data Platform?

Pipeline (Business) focuses on data collection and delivery to 700+ destinations. CDP includes Pipeline plus Unify for unified profiles and Engage for audience orchestration with AI capabilities.

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.

Segment: How many integrations does Segment have?

Segment connects to over 700 destinations, allowing data to be sent to analytics platforms, data warehouses, CRMs, and other business tools.

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.

Segment: Does Segment have SSO and HIPAA compliance?

Yes. Both Pipeline and CDP tiers offer multi-factor authentication, single sign-on (SSO), and HIPAA eligibility for healthcare organizations.

Source
Share

Related pages

More on Envoy

More on Segment

Keep looking

Other head to heads