bazel-remote
brew install bazel-remote
v2.6.1
Apache-2.0
Remote cache for Bazel
17
30-day installs · #7215
25
90-day · #9176
165
365-day · #7836
751
★ GitHub stars · updated 2mo ago
Build dependencies
GitHub topics
bazel
build
build-tool
caching
continous-integration
docker-container
goma
remote-caching
Links
- https://github.com/buchgr/bazel-remote/
- GitHub: buchgr/bazel-remote
- Brew formula source: Formula/b/bazel-remote.rb
Raw metadata
{
"aliases": [],
"alternatives": [],
"build_dependencies": [
"go"
],
"categories": [],
"caveats": null,
"conflicts_with": [],
"dependencies": [],
"deprecated": 0,
"deprecation_reason": null,
"desc": "Remote cache for Bazel",
"disable_reason": null,
"disabled": 0,
"enrichment_fetched_at": "2026-06-20T23:35:47+00:00",
"first_seen": "2026-06-20T23:34:18+00:00",
"full_name": "bazel-remote",
"github_default_branch": "master",
"github_last_commit_at": "2026-06-18T09:36:36Z",
"github_readme_excerpt": "\n\n# bazel-remote cache\n\nbazel-remote is a HTTP/1.1 and gRPC server that is intended to be used as a\nremote build cache for [REAPI](https://github.com/bazelbuild/remote-apis)\nclients like [Bazel](https://bazel.build) or as a component of a remote\nexecution service.\n\nThe cache contents are stored in a directory on disk with a maximum cache size,\nand bazel-remote will automatically enforce this limit as needed, by deleting\nthe least recently used files. S3, GCS and experimental Azure blob storage\nproxy backends are also supported.\n\nNote that while bazel-remote is consumable as a go module, we provide no\nguarantees on the stability or backwards compatibility of the APIs. We do\nattempt to keep the standalone executable backwards-compatible between\nreleases however, and cache directory format changes are only allowed in\nmajor version upgrades.\n\n**Project status**: bazel-remote has been serving TBs of cache artifacts per day since April 2018, both on\ncommodity hardware and AWS servers. Outgoing bandwidth can exceed 15 Gbit/s on the right AWS instance type.\n\n## HTTP/1.1 REST API\n\nCache entries are set and retrieved by key, and there are two types of keys that can be used:\n1. Content addressed storage (CAS), where the key is the lowercase SHA256 hash of the entry.\n The REST API for these entries is: `/cas/\u003ckey\u003e` or with an optional but ignored instance name:\n `/\u003cinstance\u003e/cas/\u003ckey\u003e`.\n2. Action cache, where the key is an arbitrary 64 character lowercase hexadecimal string.\n Bazel uses the SHA256 hash of an action as the key, to store the metadata created by the action.\n The REST API for these entries is: `/ac/\u003ckey\u003e` or with an optional instance name: `/\u003cinstance\u003e/ac/\u003ckey\u003e`.\n\nValues are stored via HTTP PUT requests, and retrieved via GET requests.\nHEAD requests can be used to confirm whether a key exists or not.\n\nIf GET requests specify `zstd` in the `Accept",
"github_repo": "buchgr/bazel-remote",
"github_stars": 751,
"github_topics": [
"bazel",
"build",
"build-tool",
"caching",
"continous-integration",
"docker-container",
"goma",
"remote-caching"
],
"homepage": "https://github.com/buchgr/bazel-remote/",
"homepage_og_description": null,
"homepage_og_image": null,
"homepage_title": null,
"installs_30d": 17,
"installs_365d": 165,
"installs_90d": 25,
"keg_only": 0,
"keg_only_reason": null,
"last_seen": "2026-06-20T23:34:18+00:00",
"license": "Apache-2.0",
"llm_generated_at": null,
"llm_model": null,
"name": "bazel-remote",
"oldnames": [],
"one_liner": null,
"optional_dependencies": [],
"rank_30d": 7215,
"rank_365d": 7836,
"rank_90d": 9176,
"raw_hash": "621faf83ce4d2fae",
"recommended_dependencies": [],
"revision": 0,
"ruby_source_path": "Formula/b/bazel-remote.rb",
"tap": "homebrew/core",
"test_dependencies": [],
"uses_from_macos": [],
"version_head": "HEAD",
"version_stable": "2.6.1",
"versioned_formulae": [],
"why_use_this": null
}