Softwr

Developer Tools · head to head

Envoy vs GitHub Actions

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
GitHub Actions logo

GitHub Actions

Testing

Automate your software workflows

From
Free
Free plan
Yes

The short version

  • Envoy is free; GitHub Actions starts at $4/mo.
  • Where GitHub Actions falls short: private repository usage is capped at 2,000 minutes per month on GitHub Free and 3,000 on Pro and Team, with anything beyond billed.
  • Prices and features on this page were last checked on 20 November 2026.

How do Envoy and GitHub Actions differ?

Envoy and GitHub Actions differ on pricing model (Open-source against Subscription) and category (Developer Tools against Testing). Only the attributes on which Envoy and GitHub Actions actually diverge.

Attributes where Envoy and GitHub Actions differ
AttributeEnvoyGitHub Actions
Pricing modelOpen-sourceSubscription
CategoryDeveloper ToolsTesting

Identical on both: starting price (Free), free tier (Yes), platforms (Web).

Not yet recorded: founded for Envoy.

Which features does each one have?

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

Nothing recorded that Envoy does not also cover.

What is each one used for?

GitHub Actions is most often brought in for running CI builds and tests on pushes and pull requests. 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 GitHub Actions
  • An edge or API gateway that needs per-route retry budgets, circuit breaking and outlier detection rather than round-robin proxyingnot GitHub Actions
  • Migrating traffic between service versions or between a monolith and its replacement, using weighted splits and shadow trafficnot GitHub Actions
  • 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 GitHub Actions

GitHub Actions

  • Running CI builds and tests on pushes and pull requestsnot Envoy
  • Automating releases, container image builds and deployments from a repositorynot Envoy
  • Scheduled maintenance jobs and repository automationnot Envoy

Where do Envoy and GitHub Actions fall short?

GitHub Actions's most cited limit: artifact storage is only 500 MB on GitHub Free and 2 GB on Team, and it is shared with GitHub Packages storage. 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

GitHub Actions

  • Private repository usage is capped at 2,000 minutes per month on GitHub Free and 3,000 on Pro and Team, with anything beyond billed
  • Artifact storage is only 500 MB on GitHub Free and 2 GB on Team, and it is shared with GitHub Packages storage
  • Larger runners are always charged for, even on public repositories and even when plan quota remains
  • Windows runners cost $0.010 per minute against $0.006 for a 2-core Linux runner, so the same workflow costs more per platform
  • macOS runners are charged at a higher per-minute rate than Linux runners
  • Failed runs consume minutes, so a job that fails after 5 minutes and is re-run for 10 uses 15 minutes of quota
  • Storage is billed on hourly accrual in GB-Hours, so deleting artifacts stops future charges but does not remove charges already accrued in the cycle
  • Cache storage is a separate 10 GB per repository allowance and peak hourly usage above it is charged
  • Minutes are charged to the repository owner, not the person who triggered the run, and anyone with write access can trigger runs
  • Without a valid payment method on file, workflows are blocked as soon as the quota is exhausted

How much do Envoy and GitHub Actions cost?

Envoy is free to use; GitHub Actions has a free plan, with paid plans from $4/mo. Plan by plan below, from each vendor's own pricing page.

Envoy

Free

No published plan breakdown. See the Envoy review.

GitHub Actions

Free
  • FreeFree
    • 2,000 CI/CD minutes per month
    • Free for public repositories
  • Team$4/mo
    • 3,000 CI/CD minutes per month
    • Free for public repositories
    • First 12 months at promotional rate
  • Enterprise$21/mo
    • 50,000 CI/CD minutes per month
    • Free for public repositories
    • First 12 months at promotional rate

Which should you pick?

Choose Envoy if

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

Choose GitHub Actions if

  • You want to start without paying.

Questions people ask

Is Envoy or GitHub Actions better?
Neither clearly leads. Envoy starts at Free and GitHub Actions at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Envoy or GitHub Actions?
Envoy starts at Free and GitHub Actions at Free.
Does Envoy or GitHub Actions run on more platforms?
Both run on Web, so platform support will not decide this one for you.
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 GitHub Actions is typically brought in for.
What can Envoy do that GitHub Actions cannot?
Envoy covers xDS dynamic configuration, Protocol breadth, Filter chain architecture, Observability by default.

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.

GitHub Actions: How much does GitHub Actions cost?

GitHub Actions is free for public repositories. For private repositories, the Team plan costs $4 per user per month (first 12 months) with 3,000 CI/CD minutes, and the Enterprise plan costs $21 per user per month (first 12 months) with 50,000 CI/CD minutes.

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.

GitHub Actions: Is there a free version of GitHub Actions?

Yes, GitHub Actions is free for all public repositories. The Free plan for private repositories includes 2,000 CI/CD minutes per month. All tiers include free CI/CD minutes for public repository workflows.

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.

GitHub Actions: What does the Team plan add to GitHub Actions?

The Team plan provides 3,000 CI/CD minutes per month compared to 2,000 on the Free plan. It costs $4 per user per month for the first 12 months. Minutes apply only to private repository workflows.

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.

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