bazel-remote vs EngFlow Remote Caching
bazel-remote
github.com
EngFlow Remote Caching
engflow.comSide by side
| Figure | bazel-remote | EngFlow Remote Caching |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | Yes |
| Open source | — | — |
| Web | — | Yes |
| Windows | — | Yes |
| macOS | Yes | Yes |
| Linux | Yes | Yes |
| API | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 2 |
| Spec score · Build Cache Software | 8.3 (#4) | 7.8 (#12) |
| Authentication | Authentication options include basic .htpasswd-style authentication and mutual TLS; LDAP authentication is experimental, and only one mechanism can be used at a time. | The pricing comparison lists HTTP basic authentication and mTLS for Free, with GCP IAM, Google OAuth, SAML, and custom options added for Enterprise. |
| Deployment | The project publishes Docker images on Docker Hub and Quay.io, documents Docker Compose and Kubernetes examples, and can be built as a standalone Linux binary. | The pricing page lists Free as self-hosted and Enterprise as self-hosted or managed, with deployment options that include bare metal, AWS, GCP, Kubernetes, and OpenStack for Free, plus Azure, MacStadium, and Orka for Enterprise. |
| 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. | Remote Caching is designed to speed builds, reduce developer workload and compute costs, and eliminate redundant rebuilds and test reruns. |
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.
EngFlow Remote Caching
EngFlow Remote Caching is a remote cache service for reducing repeated builds and test reruns, developer workload, and compute costs. It uses gRPC, cache compression, and Build without the Bytes to limit latency and unnecessary data transfers. A layered cache keeps frequently requested data available, while the Build & Test UI reports cache hit rates, build time, and status in real time. The Free tier supports Bazel and provides in-cluster caching on one machine with 32 CPU cores, running Linux. Enterprise supports Bazel, Goma for Chromium, and Soong for AOSP, as well as in-cluster or external storage such as S3 and GCS. Free is self-hosted; Enterprise can be self-hosted or managed. The service is available for Linux, macOS, Windows, web, and API use. EngFlow says builds run in isolated, encrypted environments with dedicated infrastructure by default, and its solutions receive regular third-party audits against the five SOC 2 principles. Free costs nothing; Enterprise pricing is custom quote. A trial request form is available, with no duration stated.