Softwr

Developer Tools · head to head

Envoy vs Pigment

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

Pigment

Business Intelligence

Enterprise business planning platform for finance, sales and workforce modelling

From
On request
Free plan
No

The short version

  • Pigment is a French-built planning platform.
  • Envoy is free; Pigment prices on request.
  • Only Envoy lists xDS dynamic configuration; only Pigment lists dimensional modelling.
  • Prices and features on this page were last checked on 13 November 2026.

Where they differ

Only the attributes on which Envoy and Pigment actually diverge.

Attributes where Envoy and Pigment differ
AttributeEnvoyPigment
Starting priceFreeOn request
Pricing modelOpen-sourceQuote
Free tierYesNo
CategoryDeveloper ToolsBusiness Intelligence

Identical on both: platforms (Web).

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 Pigment

  • Dimensional modelling
  • Scenario planning
  • Data connectors
  • Application blocks
  • Reporting and boards
  • Access control
  • Audit trail
  • AI assistance

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

Pigment

  • A finance team retiring a fragile Excel consolidation that no one can audit and only one person can runnot Envoy
  • Sales operations modelling quota, territory and headcount capacity against a revenue plan in the same system finance usesnot Envoy
  • A company that needs monthly re-forecasting fast enough to run scenarios live in the leadership meetingnot Envoy
  • Replacing an ageing Anaplan estate where the model has become unmaintainable and per-workspace costs have crept upnot 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

Pigment

  • No pricing is published and the structure has three moving parts, platform fee, use-case fees and tiered seats, so two companies of the same size can pay very different amounts and neither can benchmark the other
  • Cost scales with planning processes rather than with company size, so a successful first deployment creates internal demand that directly increases the bill at renewal
  • It requires a modelling owner. Without a person who understands dimensional design, teams rebuild spreadsheet patterns in Pigment and inherit all the maintenance problems they were trying to escape
  • Implementation is partner-led and measured in months, so the payback horizon is long compared with lighter FP&A tools that a controller can configure alone
  • The connector library covers major systems well but the long tail is thinner than the incumbents, and industry-specific source systems often need a warehouse or a file drop in between

Pricing, plan by plan

Envoy

Free

No published plan breakdown. See the Envoy review.

Pigment

On request
  • Pigment platformOn request
    • Platform fee plus per use-case fees
    • Licences tiered as editor, contributor and explorer
    • No free tier and no self-service signup

Which should you pick?

Choose Envoy if

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

Choose Pigment if

  • You need dimensional modelling.
  • You also want scenario planning.

Questions people ask

Is Envoy or Pigment better?
Neither clearly leads. Envoy starts at Free and Pigment at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Envoy or Pigment?
Envoy has a free tier; the other does not. Paid plans start at Free for Envoy and On request for Pigment.
Does Envoy or Pigment run on more platforms?
Both run on Web, so platform support will not decide this one for you.
Can I use Envoy for free?
Yes. Envoy has a free tier, so you can try it without paying. Pigment 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 Pigment is typically brought in for.
What can Envoy do that Pigment cannot?
Envoy covers xDS dynamic configuration, Protocol breadth, Filter chain architecture, Observability by default. Pigment covers Dimensional modelling, Scenario planning, Data connectors, Application blocks.

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.

Pigment: Does Pigment publish prices?

No. Expect a quote combining a platform fee, fees per planning use case, and seat licences split into editor, contributor and explorer tiers.

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.

Pigment: Is Pigment an alternative to Anaplan?

It is positioned directly against Anaplan and much of its customer base is migrating from it, mainly citing modelling readability and recalculation speed.

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.

Pigment: Can we use it without consultants?

In practice most deployments use Pigment or a partner for the initial build. Ongoing model changes can be handled in-house once someone owns the modelling discipline.

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.

Pigment: Where is data hosted?

Pigment is a European vendor with regional hosting options, which is often the deciding factor for EU buyers with data residency requirements.

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