# Install go-feature-flag-relay-proxy with Homebrew Stand alone server to run GO Feature Flag. Version 1.55.1 via Homebrew; verified 2026-07-29. ## Install ```sh sudo av install brew:go-feature-flag-relay-proxy ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install go-feature-flag-relay-proxy ``` Evidence: local Homebrew formula metadata ## Package facts - **Package key:** brew:go-feature-flag-relay-proxy - **Package manager:** Homebrew - **Version:** 1.55.1 - **Source summary:** Stand alone server to run GO Feature Flag - **Homepage:** - **Repository:** - **Last updated:** 2026-07-29T16:05:03+02:00 - **Generated:** 2026-08-03T19:37:03+00:00 ## Executables - go-feature-flag-relay-proxy (alias) ## Install behavior - Bottle: not available ## Freshness - Page generated: 2026-08-03 - Package-manager version: 1.55.1 ## Project history and usage GO Feature Flag Relay Proxy is the server component of GO Feature Flag, an open-source feature flag system written in Go. The relay proxy exposes feature-flag evaluation APIs so applications in several languages can use GO Feature Flag through OpenFeature providers or direct HTTP calls. ### Project history The parent GO Feature Flag repository was created in 2020 as a Go-oriented feature flag library. Its README explains that the project began as a solution for the Go language and later expanded through OpenFeature standardization, with the relay proxy providing an API layer over the Go module so non-Go applications could share the same evaluation logic. ### Adoption history The project sits in the OpenFeature ecosystem and advertises provider support across backend, frontend, and mobile languages. Its adopters list includes organizations and open-source projects using it for backend services, frontend applications, OpenFeature-based flagging, and relay-proxy deployments. ### How it is used Practitioners run the relay proxy as the central flag-evaluation service, usually with a YAML configuration file passed through `--config` or mounted into a container. The proxy loads flag definitions from retrievers such as files, HTTP, S3, or Kubernetes, stores them in memory, polls for changes, and exposes APIs that OpenFeature SDK providers call from application code. ### Why package nerds care For package maintainers, the relay proxy is the packaged operational face of a library-first Go project. Shipping it as a Homebrew formula gives developers a database-free feature-flag daemon they can install locally for testing, wire into containers, or run as infrastructure beside services. ### Timeline - 2020: The GO Feature Flag repository was created. - 2024: v1.29.x and later releases appeared on GitHub's release stream. - 2026: v1.54.x releases showed the relay-proxy and provider ecosystem under active release management. ### Related projects - OpenFeature - GO Feature Flag Go module - GO Feature Flag OpenFeature providers ### Sources - - - - - - ## Security Notes No matching local secret-handling manifest was found for go-feature-flag-relay-proxy. 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: path passed with --config ## Credential files - Unix: path passed with --config ## Combined YAML source View the package source record on GitHub. [combined/go-feature-flag-relay-proxy.yml](https://github.com/mxcl/pkgdb/blob/main/combined/go-feature-flag-relay-proxy.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