Developer Tools · head to head
Envoy vs Signicat

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

Signicat
Cybersecurity
European digital identity hub connecting national eID schemes
- From
- On request
- Free plan
- No
The short version
- Envoy is free; Signicat prices on request.
- Only Envoy lists xDS dynamic configuration; only Signicat lists eID scheme brokering.
- Prices and features on this page were last checked on 13 November 2026.
Where they differ
Only the attributes on which Envoy and Signicat actually diverge.
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 Signicat
- eID scheme brokering
- Qualified electronic signatures
- Document verification
- AML screening
- Authentication
- Digital onboarding flows
- eIDAS compliance
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 Signicat
- An edge or API gateway that needs per-route retry budgets, circuit breaking and outlier detection rather than round-robin proxyingnot Signicat
- Migrating traffic between service versions or between a monolith and its replacement, using weighted splits and shadow trafficnot Signicat
- 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 Signicat
Signicat
- A lender expanding from Norway into Sweden, Denmark and the Netherlands without four separate eID integrationsnot Envoy
- An insurer needing eIDAS qualified signatures on policy documents that will hold up in a European courtnot Envoy
- A bank that wants customers to onboard with their existing national bank ID rather than photographing a passportnot Envoy
- A public sector body needing cross-border recognition of notified eID schemes under eIDASnot 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
Signicat
- National eID scheme fees are passed through on top of Signicat's own charge, so a single-country business almost always pays less by integrating with the scheme directly
- Value is concentrated in Northern and Western Europe, and coverage in Southern and Eastern Europe is thinner, so a pan-European rollout still hits gaps requiring document fallback
- Pricing is per transaction and quoted, and because scheme rates vary by country the cost per onboarded customer differs materially between markets in ways that complicate unit economics
- Each eID scheme connection typically carries its own setup fee and approval process, so adding a country is a project with a lead time rather than a configuration change
- Availability is tied to the national schemes, meaning an outage at BankID or MitID stops your onboarding entirely and there is no vendor-side mitigation for it
Pricing, plan by plan
Envoy
FreeNo published plan breakdown. See the Envoy review.
Signicat
On request- Signicat PlatformOn request
- Priced per transaction with national scheme fees passed through
- Signature and verification products licensed separately
- Setup fee per eID scheme connected
Which should you pick?
Choose Envoy if
- You need xds dynamic configuration.
- You want to start without paying.
- You also want protocol breadth.
Choose Signicat if
- You need eid scheme brokering.
- You work on Web, iOS, Android.
- You also want qualified electronic signatures.
Questions people ask
- Is Envoy or Signicat better?
- Neither clearly leads. Envoy starts at Free and Signicat at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Envoy or Signicat?
- Envoy has a free tier; the other does not. Paid plans start at Free for Envoy and On request for Signicat.
- Does Envoy or Signicat run on more platforms?
- Envoy runs on Web. Signicat runs on Web, iOS, Android.
- Can I use Envoy for free?
- Yes. Envoy has a free tier, so you can try it without paying. Signicat 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 Signicat is typically brought in for.
- What can Envoy do that Signicat cannot?
- Envoy covers xDS dynamic configuration, Protocol breadth, Filter chain architecture, Observability by default. Signicat covers eID scheme brokering, Qualified electronic signatures, Document verification, AML screening.
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.
Signicat: Is this an alternative to a document verification vendor?
Only where national eID exists. In markets with a mature bank ID scheme it is better; elsewhere you fall back to document checks, which Signicat also provides.
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.
Signicat: Do we still pay the eID schemes?
Yes. Scheme fees are passed through in addition to Signicat charges. Ask for the split when comparing to a direct integration.
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.
Signicat: Are signatures legally qualified?
Signicat supports eIDAS qualified electronic signatures, which carry the highest legal standing in the EU, as well as advanced signatures.
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.
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.
Related pages
Other head to heads
- Envoy vs Istio
- Envoy vs Ona (formerly Gitpod)
- Envoy vs Spacelift
- Envoy vs Atlantis
- Envoy vs Jenkins
- Envoy vs Hookdeck
- Envoy vs Restate
- Envoy vs Helix
- Envoy vs Turborepo
- Envoy vs StackBlitz
- Envoy vs Webpack
- Envoy vs Backstage
- Envoy vs OpsLevel
- Envoy vs PartyKit
- Envoy vs PhpStorm
- Envoy vs Pieces for Developers
- Envoy vs RAD Studio
- Envoy vs Refact
- Envoy vs Jumio
- Envoy vs Sumsub
- Envoy vs IDnow
- Envoy vs Trulioo
- Envoy vs Veriff
- Envoy vs iDenfy
- Envoy vs Yoti
- Envoy vs Shufti Pro
- Envoy vs Socure
- Envoy vs March Networks
- Envoy vs Featurespace ARIC Risk Hub
- Envoy vs Semperis
- Envoy vs Legit Security
- Envoy vs LogRhythm SIEM
- Envoy vs Metasploit
- Envoy vs MetricStream
- Envoy vs Microsoft Defender
- Envoy vs Microsoft Sentinel
- Signicat vs Istio
- Signicat vs Ona (formerly Gitpod)
- Signicat vs Spacelift
- Signicat vs Atlantis
- Signicat vs Jenkins
- Signicat vs Hookdeck
- Signicat vs Restate
- Signicat vs Helix
- Signicat vs Turborepo
- Signicat vs StackBlitz
- Signicat vs Webpack
- Signicat vs Backstage
- Signicat vs OpsLevel
- Signicat vs PartyKit
- Signicat vs PhpStorm
- Signicat vs Pieces for Developers
- Signicat vs RAD Studio
- Signicat vs Refact
- Signicat vs Jumio
- Signicat vs Sumsub
- Signicat vs IDnow
- Signicat vs Trulioo
- Signicat vs Veriff
- Signicat vs iDenfy
- Signicat vs Yoti
- Signicat vs Shufti Pro
- Signicat vs Socure
- Signicat vs March Networks
- Signicat vs Featurespace ARIC Risk Hub
- Signicat vs Semperis
- Signicat vs Legit Security
- Signicat vs LogRhythm SIEM
- Signicat vs Metasploit
- Signicat vs MetricStream
- Signicat vs Microsoft Defender
- Signicat vs Microsoft Sentinel
