# Install func-e with Homebrew, winget

Easily run Envoy. Version 1.6.0 via Homebrew; verified 2026-07-26. Also installable with winget: winget install --id Tetrate.func-e -e.

## Install

```sh
sudo av install brew:func-e
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install func-e
```

  Evidence: local Homebrew formula metadata

### Windows

- winget (92%):

```sh
winget install --id Tetrate.func-e -e
```

  Evidence: Windows Package Manager source index: Tetrate.func-e from https://cdn.winget.microsoft.com/cache/source.msix

## Package facts

- **Package key:** brew:func-e
- **Package manager:** Homebrew
- **Version:** 1.6.0
- **Source summary:** Easily run Envoy
- **Homepage:** <https://func-e.io>
- **Repository:** <https://github.com/tetratelabs/func-e>
- **Last updated:** 2026-07-26T11:37:59+02:00
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- func-e (alias)

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-08-03
- Package-manager version: 1.6.0
## Project history and usage

func-e is a Tetrate command-line tool for running Envoy. It downloads and selects Envoy versions, runs Envoy with a supplied configuration, and stores supporting data, logs, and runtime files under documented func-e directories.

### Project history

The project presents itself as a small Envoy runner and version manager: install func-e, choose or resolve an Envoy build, and run it with a config file or inline YAML. Official releases show public versioned distribution beginning with v0.5.0 in July 2021, v1.0.0 in October 2021, and continued releases through the 1.x series.

### Adoption history

func-e is distributed from GitHub releases, through its install script at func-e.io, Homebrew, and winget package facts. Its audience is Envoy and service-mesh users who want a repeatable local way to try Envoy versions or validate production configuration.

### How it is used

The typical workflow is to run func-e with an Envoy config file or inline config, list available Envoy versions, select a version with func-e use, or override with ENVOY_PATH. It stores Envoy binaries under FUNC_E_DATA_HOME and logs under FUNC_E_STATE_HOME by default.

### Why package nerds care

func-e is a useful package-manager case because it packages not Envoy itself but a resolver and launcher around Envoy. The documented XDG-like directory variables and override URLs make it friendly to reproducible local testing while still depending on external Envoy release metadata.

### Timeline

- 2021: v0.5.0 appears in official GitHub releases.
- 2021: v1.0.0 appears in official GitHub releases.
- 2025: v1.2.0 appears in official GitHub releases.
- 2026: v1.6.0 appears in official GitHub releases.

### Related projects

- Envoy is the proxy that func-e downloads and runs.
- Tetrate's archive endpoint supplies the default Envoy versions JSON used by func-e.
- Service-mesh workflows are the operational context for validating Envoy configuration locally.

### Sources

- <https://func-e.io/>
- <https://github.com/tetratelabs/func-e>
- <https://github.com/tetratelabs/func-e#readme>
- <https://github.com/tetratelabs/func-e/blob/master/USAGE.md>
- <https://github.com/tetratelabs/func-e/releases>


## Security Notes

No matching local secret-handling manifest was found for func-e. Nucleus package metadata is still published here so future coverage has a stable package URL.



## Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.


## Configuration files

- Unix: ${HOME}/.config/func-e
## Other Package-Manager Records

- winget - Tetrate.func-e: normalized package name match | Windows Package Manager source index: Tetrate.func-e from https://cdn.winget.microsoft.com/cache/source.msix


## Combined YAML source

View the package source record on GitHub. [combined/func-e.yml](https://github.com/mxcl/pkgdb/blob/main/combined/func-e.yml)


## Sources

- pkg.so package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph