BuildFetch

BuildFetch Cache

Last updated: July 21, 2026

BuildFetch Cache is distributed cache product on top of BuildFetch's distributed file storage infrastructure. BuildFetch Cache speeds up Gradle, Bazel, and Ccache workflows for engineers, CI pipelines, and AI coding agents by keeping build artifacts close to the workloads that need them.

BuildFetch Cache is built to support both Gradle Build Cache and Bazel Remote Caching, and Ccache Remote Storage, with deployment options for BuildFetch Cloud, custom cloud, and on-premise environments.

What BuildFetch Cache is

BuildFetch Cache is designed to reduce build times from minutes to seconds by reusing build artifacts instead of recomputing them. It supports the standard Gradle Build Cache protocol, Bazel Remote Caching workflows, and Ccache Remote Storage, with deployment options for BuildFetch Cloud, Custom Cloud, and On-premise Kubernetes environments.

BuildFetch Cache Features

  • Cache APIs

    BuildFetch Cache implements the standard APIs used by Gradle Build Cache and Bazel Remote Caching, and Ccache Remote Storage, so BuildFetch Cache supports all three workflows.
    Gradle Build CacheBazel Remote CachingCcache Remote Storage

  • Fast Cache Storage

    Cache entries live on NVMe and SSD storage for low latency and high throughput. See the architecture docs for the cluster and storage layout that makes the cache fast.
    Architecture

  • Network Traffic

    BuildFetch Cache includes generous network traffic limits, which matter most for larger teams moving a lot of build artifacts. Compare plan limits on the pricing page.
    Pricing

  • Cache Requests

    Request volume scales with team size and CI activity, so the pricing page shows how included requests and overages are packaged for each plan.
    Pricing

  • LRU Cache Retention

    When storage fills up, BuildFetch clears the least recently used entries. The architecture docs explain the storage model that preserves Bazel AC/CAS consistency while eviction happens.
    Architecture

  • Observability Dashboard

    Visibility into cache hits, latency, and storage is built in so teams can tune usage and confirm the cache is doing its job. The pricing page shows which plans include the dashboard.
    Pricing

  • Cache Files Replication

    BuildFetch replicates cache files for durability and access speed. The surrounding cluster design is covered in the architecture docs.
    Architecture

  • Checksum Verification

    Every file is verified at access time so corrupted data is detected early. That integrity story sits alongside the security docs for at-rest and in-transit protections.
    Security

  • Bus-Bar Networking

    The cluster networking model spreads traffic across nodes with round-robin DNS and ingress. Read more in the architecture docs.
    Architecture

  • At-Rest Encryption

    Cache data is encrypted on disk, and the exact deployment guarantees depend on your plan and deployment model. See both the security docs and pricing page.
    SecurityPricing

  • Audit Logs

    Audit logging is available for stronger governance and troubleshooting on higher-tier plans. Compare the plan matrix on the pricing page.
    Pricing

  • Support

    Support response times and channels vary by plan. The pricing page has the full breakdown.
    Pricing

Pricing

Compare BuildFetch Cache plans and deployment options on the pricing page to choose the right fit for your team, workload, and infrastructure model.

Go to BuildFetch Cache Pricing

Docs in this category