bazel-remote vs zccache
bazel-remote
github.comzccache
github.comSide by side
| Figure | bazel-remote | zccache |
|---|---|---|
| Price from | Free | — |
| Free plan | Yes | — |
| Free trial | — | — |
| Open source | — | — |
| Windows | — | Yes |
| macOS | Yes | Yes |
| Linux | Yes | Yes |
| API | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 0 |
| Spec score · Build Cache Software | 8.3 (#4) | 6.8 (#22) |
| License | The repository identifies the project as licensed under Apache-2.0. | The repository identifies its license as AGPL-3.0. |
| Purpose | bazel-remote is an HTTP/1.1 and gRPC server for use as a remote build cache for Bazel and other REAPI clients, or as part of a remote execution service. | zccache is a local-first compiler cache for C/C++ and Rust, described as a drop-in replacement for sccache and ccache. |
| Storage | Cache contents can be stored on disk with a configurable maximum size, and least recently used files are deleted to enforce the limit. | The feature comparison lists local filesystem storage and GitHub Actions Cache support, but marks S3, Google Cloud Storage, Redis, Memcached, Azure Blob, and distributed build farms unsupported. |
Plans
In their own words
bazel-remote
bazel-remote is free, Apache-2.0-licensed open-source software that runs as a self-hosted HTTP/1.1 and gRPC server for Bazel remote caching and other REAPI clients. Cache data can stay on disk with a configured maximum size; least recently used files are removed when that limit is reached. Storage backends include S3, Google Cloud Storage, and an experimental Azure Blob Storage proxy. The server exposes HTTP REST endpoints and REAPI v2 ActionCache, ContentAddressableStorage, Capabilities, and Byte Stream services over gRPC. Zstandard-compressed CAS blobs can reduce network use and increase effective cache capacity. Prometheus metrics are available for HTTP and gRPC endpoints. Deployment options include Docker images, Docker Compose, Kubernetes examples, or a standalone Linux binary, including ARM64 Docker deployments such as Raspberry Pi. Authentication supports .htpasswd-style credentials or mutual TLS; LDAP is experimental, and only one mechanism can be active. TLS settings are configurable. The default permits unauthenticated access, so operators must configure protection.