install

Additional install commands

macOS

Homebrewverified · 100%

brew install bazel-remote

local Homebrew formula metadata

Linux

Nixverified · 92%

nix profile install nixpkgs#bazel-remote

nixpkgs package indexes · pkgs/by-name/ba/bazel-remote/package.nix · source: api.github.com

overview

Package summary

Remote cache for Bazel

Project links

Commands and aliases

bazel-remote

history

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.
https://github.com/buchgr/bazel-remote#readme documents project purpose, production-use history since April 2018, APIs, storage backends, configuration, and auth.
source_facts.package-manager-url records the Homebrew packaging surface.

security posture

Risk level: green

narrow executable package without higher-risk signals.

Risk classifier

green risk · low confidence · appliance

Why

narrow executable package without higher-risk signals

Signals

metadata:no-higher-risk-signals

Install behavior

No Homebrew post-install hook is recorded in formula metadata.
Homebrew bottle metadata is available for 6 platform targets.
Build metadata lists 1 build dependencies.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

local files

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

Config paths the tool may read or write during local use.

Unix: path passed with --config_file$BAZEL_REMOTE_CONFIG_FILE

Credential files

Credential-bearing paths to review before unattended agent runs.

Unix: path passed with --htpasswd_file$BAZEL_REMOTE_HTPASSWD_FILE

executables

Installed executables

Command	Kind	Exposure	Note
`bazel-remote`	cli	global executable

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-07-08

manager version2.6.1

manager updated

local dataok

upstreamcurrent

latest detectedv2.6.1

https://github.com/buchgr/bazel-remote

infoNo package-manager update timestamp was available.low confidence

install metadata

Package metadata

Package key	brew:bazel-remote
Version	2.6.1
Package manager	Homebrew
Package manager page	https://formulae.brew.sh/formula/bazel-remote
Homepage	https://github.com/buchgr/bazel-remote/
Repository	https://github.com/buchgr/bazel-remote
Upstream docs	https://github.com/buchgr/bazel-remote#readme
License	Apache-2.0
Source archive	https://github.com/buchgr/bazel-remote/archive/refs/tags/v2.6.1.tar.gz
Build dependencies	go
Bottle	available (on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-install	not defined
Service	none declared

registry facts

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	https://ghcr.io/v2/homebrew/core
Deprecated	no
Disabled	no
Keg Only	no
URL Keys	head stable

source database matches

Other package-manager records

Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.

Nix95%

bazel-remote

nix profile install nixpkgs#bazel-remote

normalized package name match
Matched by: Bazel Remote

nixpkgs package indexes · api.github.com · 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 graph

Links come from deterministic package relationships, av.db category and tag curation, ecosystem matches, and package hub membership.

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Combined YAML source

View the package source record on GitHub.

combined/bazel-remote.yml

Used sources

Geiger risk classifier
Nucleus package database
av.db category and tag curation
cross-ecosystem install command graph
curated configuration and credential file locations
curated package history
external package-manager database matches
package relationship graph
package version freshness
package-page enrichment

Install bazel-remote with Homebrew, Nix