# Install flagd with Homebrew

Feature flag daemon with a Unix philosophy. Version 0.16.1 via Homebrew; verified 2026-07-27.

## Install

```sh
sudo av install brew:flagd
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install flagd
```

  Evidence: local Homebrew formula metadata

## Package facts

- **Package key:** brew:flagd
- **Package manager:** Homebrew
- **Version:** 0.16.1
- **Source summary:** Feature flag daemon with a Unix philosophy
- **Homepage:** <https://flagd.dev>
- **Repository:** <https://github.com/open-feature/flagd>
- **Last updated:** 2026-07-27T15:40:04Z
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- flagd (alias)

## Install behavior

- Bottle: not available

## Freshness

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

flagd is an OpenFeature-compliant feature flag evaluation engine and daemon designed around a Unix-style command-line interface rather than a bundled management UI.

### Project history

The public GitHub release stream begins in June 2022. Upstream positions flagd as a ready-made open-source OpenFeature backend system: a separate process, sidecar, central service, or in-process engine for evaluating feature flags.

The documentation explicitly says flagd does not include a UI, management console, or persistence layer. Instead, it is configured through a POSIX-style CLI and supplied with flag definitions from files, HTTP endpoints, Kubernetes custom resources, or proto-compliant gRPC services.

By 2023 and 2024 the release train had split into related components such as flagd, core, flagd-proxy, and Kubernetes-oriented proxy artifacts, reflecting the project's role inside the broader OpenFeature ecosystem.

### Adoption history

flagd's adoption path is tied to OpenFeature: applications use an OpenFeature SDK plus a flagd provider, while operations teams can run flagd as a binary, container image, service, sidecar, or Kubernetes-integrated component.

The quick-start workflow demonstrates containerized use on port 8013, JSON flag definitions, cURL evaluation calls, and live updates without restarting the daemon. This makes flagd attractive for teams that want vendor-neutral feature flag evaluation without committing to a hosted flag-management product.

### How it is used

Typical CLI use starts flagd with a URI pointing at a local or remote flag definition. The daemon exposes evaluation APIs over HTTP or gRPC, watches flag definitions for changes, and supports boolean, string, number, and JSON flag values, targeting rules, progressive rollouts, and pseudorandom assignments for experiments.

The CLI reference lists ~/.agent.yaml as the default config file. The main commands include flagd start and flagd version.

### Why package nerds care

flagd is package-nerd significant because it turns feature flags into a local daemon plus protocol boundary: install a binary, point it at flag data, wire it to OpenFeature providers, and keep flag evaluation independent of a SaaS control plane.

Its packaging also reflects contemporary cloud-native CLI distribution: GitHub releases, container images, Kubernetes integration, gRPC/HTTP APIs, OpenTelemetry-oriented observability, and a docs site generated from repository documentation.

### Timeline

- 2022: First public GitHub release.
- 2023: 0.3.x through 0.6.x releases expanded the early daemon and proxy release train.
- 2024: 0.11.x releases continued alongside core and flagd-proxy components.
- 2025: 0.12.x releases published for flagd, core, and flagd-proxy.

### Related projects

- OpenFeature, OpenFeature SDKs, flagd providers, OpenFeature Operator, Kubernetes custom resources, OpenTelemetry.

### Sources

- <https://github.com/open-feature/flagd>
- <https://raw.githubusercontent.com/open-feature/flagd/main/docs/index.md>
- <https://flagd.dev/>
- <https://flagd.dev/quick-start/>
- <https://flagd.dev/reference/flagd-cli/flagd/>
- <https://api.github.com/repos/open-feature/flagd/releases>


## Security Notes

narrow executable package without higher-risk signals.

- **Geiger risk:** green / low
- narrow executable package without higher-risk signals


## 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: ~/.agent.yaml

## Combined YAML source

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


## Sources

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