bazel-remote vs Ccache

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.

Ccache is a build tool that can reduce repeated compilation work by storing prior results and recognizing when a single-file compilation recurs. It supports compilers such as GCC, Clang and MSVC, and languages including C, C++, assembler, CUDA, Objective-C and Objective-C++, with support varying by compiler and language. Runtime support includes Linux, macOS and native Windows at support level A, and Windows with MSYS2 and other Unix-like platforms at level B. Direct and depend modes can avoid running the preprocessor. Remote caching is possible through adaptable storage backends, with listed helpers for HTTP, HTTPS and Redis protocols. Ccache records cache hit and miss statistics, manages cache size, supports Zstandard compression, and uses BLAKE3 and XXH3 in its hashing and corruption checks. It works with Make, CMake, Ninja and Visual Studio. It is free software under the GNU GPL version 3 or later. Its scope has limits: multi-file compilation, linking and compilations with unsupported flags fall back to the real compiler. The project also cautions that cache misses add overhead and recommends measuring typical workloads.