Softwr

Developer Tools · head to head

Envoy vs Split

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

Split

Testing

Feature flags tied to a metrics pipeline that attributes production impact to each release, now Harness FME

From
On request
Free plan
No

The short version

  • Envoy is free; Split prices on request.
  • Only Envoy lists xDS dynamic configuration; only Split lists feature flags with targeting.
  • Prices and features on this page were last checked on 20 November 2026.

How do Envoy and Split differ?

Envoy and Split differ on starting price (Free against On request), pricing model (Open-source against Quote) and free tier (Yes against No). Only the attributes on which Envoy and Split actually diverge.

Attributes where Envoy and Split differ
AttributeEnvoySplit
Starting priceFreeOn request
Pricing modelOpen-sourceQuote
Free tierYesNo
PlatformsWebWeb, API, iOS, Android, Windows
CategoryDeveloper ToolsTesting

Which features does each one have?

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

  • Feature flags with targeting
  • Metrics impact engine
  • Guardrail metrics
  • Statistical significance testing
  • Event ingestion
  • SDKs and streaming updates
  • Audit and approvals
  • Harness platform integration

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

Split

  • A product organisation that wants every release measured against conversion and latency by default, not only deliberate experimentsnot Envoy
  • Running A/B tests with real statistical significance rather than comparing two dashboard linesnot Envoy
  • Catching a regression at five per cent rollout because a guardrail metric fires before the change reaches everyonenot Envoy
  • A team already committed to Harness for CI and CD that wants flags in the same platform and contractnot Envoy

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

Split

  • Split is now a module of the Harness platform and split.io redirects to harness.io, so buying it means entering a Harness commercial relationship rather than a standalone flag vendor contract
  • Harness no longer publishes per-module prices, so an organisation that wants only feature management cannot get a list price and must negotiate a module out of a platform bundle
  • The measurement engine needs traffic volume to reach significance, so a product with modest usage gets flags with an experimentation layer it will rarely be able to conclude anything from
  • Metric attribution depends on correctly instrumented events flowing into Split, which is an integration project in its own right; without it you have paid for an experimentation platform and are using it as a flag switch
  • As part of a larger DevOps suite the roadmap now competes with CI, CD, security and cloud cost modules for attention, so feature management is no longer the company’s single focus the way it was as an independent product

How much do Envoy and Split cost?

Envoy is free to use; Split is priced on request. Plan by plan below, from each vendor's own pricing page.

Envoy

Free

No published plan breakdown. See the Envoy review.

Split

On request
  • Harness FreeFree
    • Harness Open Source and community support
    • Intended for individuals and small teams
    • Feature management capability limited at this tier
  • Harness EssentialsOn request
    • Bundled DevOps modules including CI, CD, IaC and security testing
    • Standard support
    • Pricing requires contacting sales
  • Harness EnterpriseOn request
    • Mix and match from 15 or more modules including Feature Management and Experimentation
    • Premier support with a dedicated account manager
    • Higher pipeline concurrency and organisation limits

Which should you pick?

Choose Envoy if

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

Choose Split if

  • You need feature flags with targeting.
  • You work on Web, API, iOS, Android, Windows.
  • You also want metrics impact engine.

Questions people ask

Is Envoy or Split better?
Neither clearly leads. Envoy starts at Free and Split at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Envoy or Split?
Envoy has a free tier; the other does not. Paid plans start at Free for Envoy and On request for Split.
Does Envoy or Split run on more platforms?
Envoy runs on Web. Split runs on Web, API, iOS, Android, Windows.
Can I use Envoy for free?
Yes. Envoy has a free tier, so you can try it without paying. Split 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 Split is typically brought in for.
What can Envoy do that Split cannot?
Envoy covers xDS dynamic configuration, Protocol breadth, Filter chain architecture, Observability by default. Split covers Feature flags with targeting, Metrics impact engine, Guardrail metrics, Statistical significance testing.

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.

Split: Is Split still called Split?

It is now sold as Harness Feature Management and Experimentation after the Harness acquisition, and split.io redirects to harness.io.

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.

Split: Can I buy just feature flags?

Not from a price list. Harness publishes bundle tiers and directs single-module buyers to sales.

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.

Split: What does it do that a plain flag service does not?

It attributes changes in your product metrics to specific flags with statistical significance testing and alerts on guardrail metrics.

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.

Split: Do we need a lot of traffic?

Yes. Statistical tests need volume to conclude, so low-traffic products get limited value from the measurement layer.

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