# Install bazel-remote with Homebrew, Nix Remote cache for Bazel. Version 2.6.1 via Homebrew; verified from local package data. ## Install ```sh sudo av install brew:bazel-remote ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install bazel-remote ``` Evidence: local Homebrew formula metadata ### Linux - Nix (92%): ```sh nix profile install nixpkgs#bazel-remote ``` Evidence: nixpkgs package indexes: pkgs/by-name/ba/bazel-remote/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 ## Package facts - **Package key:** brew:bazel-remote - **Package manager:** Homebrew - **Package manager page:** - **Version:** 2.6.1 - **Source summary:** Remote cache for Bazel - **Homepage:** - **Repository:** - **Upstream docs:** - **License:** Apache-2.0 - **Source archive:** - **Generated:** 2026-07-08T07:18:31+00:00 ## Executables - bazel-remote (cli) - bazel-remote (alias) ## Build dependencies - go ## Install behavior - Post-install hook: not defined - Bottle: available on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux ## Freshness - Page generated: 2026-07-08 - Package-manager version: 2.6.1 - Local data: ok - Upstream repository: https://github.com/buchgr/bazel-remote - Upstream latest detected: v2.6.1 (current) - info: No package-manager update timestamp was available. ## Project history and usage bazel-remote is a standalone HTTP/1.1 and gRPC remote build cache for Bazel and other REAPI clients, optimized for teams that want remote cache performance without operating a full remote execution service. ### Project history The project began in August 2017 as a basic HTTP cache and grew into a production remote-cache server with disk storage, least-recently-used eviction, S3 and GCS backends, gRPC support, REAPI compatibility, and Prometheus-friendly operational endpoints. Its README reports that bazel-remote has served terabytes of cache artifacts per day since April 2018 on commodity hardware and AWS servers, which is unusually explicit operational history for a package-manager formula. ### Adoption history bazel-remote became useful as Bazel users adopted remote caching to make monorepo and CI builds faster without adopting remote execution at the same time. Homebrew and Nix packaging reflect its role as deployable infrastructure: users install a single binary, point Bazel at its HTTP or gRPC endpoint, and size local disk or cloud-backed storage for their build workload. ### How it is used Operators configure a cache directory, maximum cache size, HTTP and/or gRPC listener, optional TLS/authentication, and optional proxy backends through flags, environment variables, or a YAML config file. Bazel clients use bazel-remote for action-cache and content-addressable-storage reads and writes, while the server exposes /status, CAS test endpoints, metrics, and optional Remote Asset API support. ### Why package nerds care bazel-remote is package-nerd interesting because it packages build acceleration as a small Go service rather than a SaaS product or heavyweight cluster. It sits at the boundary between package manager convenience and fleet infrastructure: a Homebrew-installed binary can be enough for local experiments, but the same executable can serve multi-terabyte-per-day CI traffic. ### Timeline - 2017-08: Upstream git history starts with an initial HTTP cache implementation. - 2018-04: README reports bazel-remote serving terabytes of cache artifacts per day from this period onward. - 2020s: README documents HTTP/1.1, gRPC REAPI, cloud proxy backends, zstd compressed blobs, and operational endpoints. ### Related projects - Bazel is the primary client and provides remote cache flags used with bazel-remote. - bazelbuild/remote-apis defines the REAPI services that bazel-remote implements in part. - Remote execution systems can use bazel-remote as a cache component or as a simpler alternative when execution offload is unnecessary. ### Sources - Upstream git history for https://github.com/buchgr/bazel-remote starts in August 2017. - - source_facts.package-manager-url records the Homebrew packaging surface. ## 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: path passed with --config_file, $BAZEL_REMOTE_CONFIG_FILE ## Credential files - Unix: path passed with --htpasswd_file, $BAZEL_REMOTE_HTPASSWD_FILE ## Source Database Details - **Source Database:** Homebrew formula API - **Tap:** homebrew/core - **Full Name:** bazel-remote - **Version Scheme:** 0 - **Revision:** 0 - **Head Version:** HEAD - **Bottle Stable Root URL:** - **Deprecated:** no - **Disabled:** no - **Keg Only:** no - **URL Keys:** head, stable ## Other Package-Manager Records - Nix - bazel-remote: normalized package name match | nixpkgs package indexes: pkgs/by-name/ba/bazel-remote/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 ## Related links - [Source-control packages](https://www.automicvault.com/pkg/source-control-tools/) - Belongs to a source-control command family. - [Terminal utility packages](https://www.automicvault.com/pkg/terminal-utilities/) - Matched terminal and command-line workflow metadata. - [Text processing packages](https://www.automicvault.com/pkg/text-processing-tools/) - Matched text, document, or structured-data processing metadata. - [Developer build packages](https://www.automicvault.com/pkg/developer-build-tools/) - Matched build, compiler, generator, or developer workflow metadata. - [go](https://www.automicvault.com/pkg/brew/go/) - Build dependency declared by Homebrew. - [bazel-diff](https://www.automicvault.com/pkg/brew/bazel-diff/) - Shares av.db curated category or tags: bazel, cli, developer-tools. - [bazelisk](https://www.automicvault.com/pkg/brew/bazelisk/) - Shares av.db curated category or tags: bazel, cli, developer-tools. - [buildifier](https://www.automicvault.com/pkg/brew/buildifier/) - Shares av.db curated category or tags: bazel, cli, developer-tools. - [buildozer](https://www.automicvault.com/pkg/brew/buildozer/) - Shares av.db curated category or tags: bazel, cli, developer-tools. - [gflags](https://www.automicvault.com/pkg/brew/gflags/) - Shares av.db curated category or tags: bazel, cli, developer-tools. - [ibazel](https://www.automicvault.com/pkg/brew/ibazel/) - Shares av.db curated category or tags: bazel, cli, developer-tools. ## Combined YAML source View the package source record on GitHub. [combined/bazel-remote.yml](https://github.com/automic-vault/db/blob/main/combined/bazel-remote.yml) ## Sources - Nucleus package database - Geiger risk classifier - package-page enrichment - curated configuration and credential file locations - curated package history - package version freshness - av.db category and tag curation - package relationship graph - external package-manager database matches - cross-ecosystem install command graph