Softwr

Cybersecurity · head to head

Acunetix vs Envoy

Acunetix logo

Acunetix

Cybersecurity

Web application security testing made easy

From
On request
Free plan
No
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

The short version

  • Acunetix is an automated web vulnerability scanner.
  • Both are free.
  • Only Acunetix lists DAST scanning; only Envoy lists xDS dynamic configuration.
  • Where Acunetix falls short: pricing available by quote only; no transparent pricing published online.
  • Prices and features on this page were last checked on 13 November 2026.

Where they differ

Only the attributes on which Acunetix and Envoy actually diverge.

Attributes where Acunetix and Envoy differ
AttributeAcunetixEnvoy
Starting priceOn requestFree
Pricing modelSubscriptionOpen-source
Free tierNoYes
PlatformsWindows, macOS, Web, APIWeb
CategoryCybersecurityDeveloper Tools

Not yet recorded: founded for Envoy.

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 Acunetix

  • DAST scanning
  • IAST technology
  • AcuSensor
  • JavaScript security
  • SQL injection testing
  • XSS detection
  • OWASP Top 10
  • API security testing

Only in Envoy

  • xDS dynamic configuration
  • Protocol breadth
  • Filter chain architecture
  • Observability by default
  • Outlier detection
  • Traffic shaping
  • mTLS termination and origination
  • Hot restart

What people use each for

The jobs each tool is most often brought in to do.

Acunetix

  • Scanning web applications for security vulnerabilitiesnot Envoy
  • Testing APIs for exploitable weaknesses and threatsnot Envoy
  • Automating dynamic application security testing (DAST)not Envoy
  • Finding and validating security issues in production environmentsnot Envoy

Envoy

  • Acting as the data plane under a service mesh or Gateway API implementation, which is how the overwhelming majority of deployments use itnot Acunetix
  • An edge or API gateway that needs per-route retry budgets, circuit breaking and outlier detection rather than round-robin proxyingnot Acunetix
  • Migrating traffic between service versions or between a monolith and its replacement, using weighted splits and shadow trafficnot Acunetix
  • 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 Acunetix

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Acunetix

  • Pricing available by quote only; no transparent pricing published online
  • Requires per-application licenses for comprehensive coverage
  • Scanning speed and feature depth depend on subscription tier
  • Advanced features like API security testing may require higher-tier plans

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

Pricing, plan by plan

Acunetix

On request
  • StandardFree
    • Single user
    • 5 targets
    • Scheduled scans
  • PremiumFree
    • Multiple users
    • Unlimited targets
    • CI/CD integration
  • Acunetix 360Free
    • Enterprise features
    • SDLC integration
    • Custom workflows

Envoy

Free

No published plan breakdown. See the Envoy review.

Which should you pick?

Choose Acunetix if

  • You need dast scanning.
  • You work on Windows, macOS, Web, API.
  • You also want iast technology.

Choose Envoy if

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

Questions people ask

Is Acunetix or Envoy better?
Neither clearly leads. Acunetix starts at On request and Envoy at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Acunetix or Envoy?
Envoy has a free tier; the other does not. Paid plans start at On request for Acunetix and Free for Envoy.
Does Acunetix or Envoy run on more platforms?
Acunetix runs on Windows, macOS, Web, API. Envoy runs on Web.
Can I use Envoy for free?
Yes. Envoy has a free tier, so you can try it without paying. Acunetix starts at On request.
What is Acunetix best used for?
Acunetix is most often used for scanning web applications for security vulnerabilities, testing apis for exploitable weaknesses and threats, automating dynamic application security testing (dast), finding and validating security issues in production environments. Of those, scanning web applications for security vulnerabilities and testing apis for exploitable weaknesses and threats are not what Envoy is typically brought in for.
What can Acunetix do that Envoy cannot?
Acunetix covers DAST scanning, IAST technology, AcuSensor, JavaScript security. Envoy covers xDS dynamic configuration, Protocol breadth, Filter chain architecture, Observability by default.

Answered from the vendors’ own pages

Acunetix: How much does Invicti (formerly Acunetix) cost?

Invicti pricing is available by quote based on your organization's needs, application count, and required features. The platform offers 8x faster scanning compared to competitors and detects 99.98% of exploitable vulnerabilities. Contact Invicti sales for a custom pricing proposal.

Source
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.

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.

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.

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.

Share

Related pages

Other head to heads