Envoy
Envoy is an open-source cloud-native edge, middle, and service proxy for managing, routing, and securing traffic in microservice architectures.
Platform availability
Available on 1 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
79/100 Good
- Maintained
- 100last commit 14 days ago
- Popular
- 8929,192 GitHub stars
- Easy to install
- 251 install platform, install notes
- Light to run
- No data
Based on 3 of 4 factors.
Availability: platform listings confirmed today
- GitHub stars
- 29,192
- Open issues
- 1938
- Last commit
- 2026-11-07
- Latest release
- v1.40.2
- License
- Apache-2.0
- Activity
- steady
Checked 14 days ago - source: GitHub (envoyproxy/envoy)
Resources & Compatibility
Requirements not published yet.
First-install notes
- Point Envoy at its config file Start Envoy with a config path, like `-c /path/to/config.yaml`, so it knows how to handle traffic; without a valid config file it will not start correctly. If you want, set `--concurrency` to choose how many worker threads it uses. source
- Run Envoy as a Windows service On Windows, use `sc create` from an administrator prompt and replace the example paths with your real `envoy.exe` and config file, then run `sc start EnvoyProxy`. The service will not run if those paths or the config file are wrong. source
- Install Envoy Gateway on Kubernetes If you are installing Envoy Gateway on Kubernetes, use the Helm install command, wait for the deployment to become available, then apply the quickstart manifest. Skipping the wait can make the example setup fail while Envoy Gateway is still starting. source
Fetched 41 days ago - each note links to its source
Variants
Alternatives (2)
- Haproxy - HAProxy is a TCP proxy and a HTTP reverse proxy.
- Træfik Proxy - The Cloud Native Application Proxy Simplify networking complexity while designing, deploying, and operating applications.
Checked 40 days ago - source: AlternativeTo
Common questions
Can Calico Envoy Gateway be used with a self-hosted Kubernetes cluster?
The snippet does not confirm a working result. It only records a Kubernetes user asking whether anyone has tried Calico Envoy Gateway in a self-hosted setup.
How should I diagnose a 503 Service Unavailable caused by no healthy upstream in Envoy?
Look for access log flag UH and check curl localhost:9901/clusters for health_flags and host counts. Common causes are all backends down, failing active health checks, wrong ports, or endpoints not registered.
What setup tasks are documented for ClonePartner Envoy?
The documentation covers installing, configuring, operating, and extending Envoy. It describes Envoy as a self-hosted data movement and workflow platform.
Do I need separate Envoy accounts for multiple workplaces?
No, you only need one Envoy account whether you plan to use it at a single workplace or multiple workplaces.
Answers sourced from docs.clonepartner.com, envoy.help, sadservers.com, www.reddit.com
Community
Collected 48 days ago - public community threads