Softwr

Developer Tools · head to head

Envoy vs Trunk Code Quality

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
Trunk Code Quality logo

Trunk Code Quality

Developer Tools

Metalinter that runs and manages linters, formatters and security scanners

From
Free
Free plan
Yes

The short version

  • Both are free.
  • Only Envoy lists xDS dynamic configuration; only Trunk Code Quality lists version pinning through trunk.yaml.
  • Where Trunk Code Quality falls short: private repositories with more than five active committers need a paid licence.
  • Prices and features on this page were last checked on 20 November 2026.

How do Envoy and Trunk Code Quality differ?

Envoy and Trunk Code Quality differ on pricing model (Open-source against Freemium) and platforms. Only the attributes on which Envoy and Trunk Code Quality actually diverge.

Attributes where Envoy and Trunk Code Quality differ
AttributeEnvoyTrunk Code Quality
Pricing modelOpen-sourceFreemium
PlatformsWebmacOS, Linux, Windows

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

Not yet recorded: founded for Envoy.

Which features does each one have?

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

  • Installs and runs over 100 linters and formatters
  • Version pinning through trunk.yaml
  • Hold the Line checks on new changes only
  • Background daemon that precomputes results
  • VS Code and Neovim editor integration
  • GitHub integration for pull request checks
  • Security scanning tools such as trivy and gitleaks
  • Runs in any CI environment

What is each one used for?

Trunk Code Quality is most often brought in for running one lint command across a polyglot repository. 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 Trunk Code Quality
  • An edge or API gateway that needs per-route retry budgets, circuit breaking and outlier detection rather than round-robin proxyingnot Trunk Code Quality
  • Migrating traffic between service versions or between a monolith and its replacement, using weighted splits and shadow trafficnot Trunk Code Quality
  • 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 Trunk Code Quality

Trunk Code Quality

  • Running one lint command across a polyglot repositorynot Envoy
  • Gradually fixing legacy code with Hold the Linenot Envoy
  • Pinning linter versions across a teamnot Envoy
  • Enforcing the same checks locally and in CInot Envoy
  • Adding security scanners to pull requestsnot Envoy

Where do Envoy and Trunk Code Quality fall short?

Trunk Code Quality's most cited limit: private repositories with more than five active committers need a paid licence. 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

Trunk Code Quality

  • Private repositories with more than five active committers need a paid licence
  • Paid Team and Enterprise prices are not published; quotes come from sales
  • Core CLI is closed source, with only plugins and the GitHub Action under MIT
  • Results depend on the underlying linters, so rule coverage is not Trunk's own

How much do Envoy and Trunk Code Quality cost?

Envoy is free to use; Trunk Code Quality is free to use. Plan by plan below, from each vendor's own pricing page.

Envoy

Free

No published plan breakdown. See the Envoy review.

Trunk Code Quality

Free
  • Free (up to 5 active committers on private repos)Free
  • Team (per seat)On request
  • Enterprise (annual site licence)On request

Which should you pick?

Choose Envoy if

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

Choose Trunk Code Quality if

  • You need installs and runs over 100 linters and formatters.
  • You want to start without paying.
  • You work on macOS, Linux, Windows.
  • You also want version pinning through trunk.yaml.

Questions people ask

Is Envoy or Trunk Code Quality better?
Neither clearly leads. Envoy starts at Free and Trunk Code Quality at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Envoy or Trunk Code Quality?
Envoy starts at Free and Trunk Code Quality at Free.
Does Envoy or Trunk Code Quality run on more platforms?
Envoy runs on Web. Trunk Code Quality runs on macOS, Linux, Windows.
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 Trunk Code Quality is typically brought in for.
What can Envoy do that Trunk Code Quality cannot?
Envoy covers xDS dynamic configuration, Protocol breadth, Filter chain architecture, Observability by default. Trunk Code Quality covers Installs and runs over 100 linters and formatters, Version pinning through trunk.yaml, Hold the Line checks on new changes only, Background daemon that precomputes results.

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.

Trunk Code Quality: What does Trunk Code Quality do?

It is a metalinter that installs, pins and runs third party linters, formatters and security scanners from one CLI. A background daemon precomputes results for editor annotations.

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.

Trunk Code Quality: Is Trunk Code Quality free?

Public and open source repositories have no stated usage limit, and private repositories with five or fewer active committers can use the CLI at no cost. Larger private teams need a paid licence.

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.

Trunk Code Quality: Which operating systems are supported?

The launcher supports macOS and Linux. Windows is supported from CLI version 1.13.0, using git-bash, msys2 or a PowerShell launcher.

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.

Trunk Code Quality: How many linters does it support?

The supported linters page claims over 100 linters and formatters. They cover many languages plus infrastructure, security, SQL and Markdown tooling.

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.

Share

Related pages

Other head to heads