We use cookies to understand how people use Depot.
Cache

Depot Cache

Depot Cache is our remote caching service that speeds up your builds by providing incremental builds and accelerated tests, both locally and inside of your favorite CI provider.

One of the biggest benefits of adopting advanced build tools like Bazel is the ability to build only the parts of your codebase that have changed. Or, in other words, incremental builds. This is done by reusing previously built artifacts that have not changed via a build cache.

Supported tools

Depot Cache integrates with build tools that support remote caching like GitHub Actions, Bazel, Go, Turborepo, sccache, Pants, and Gradle. For information about how to configure each tool to use Depot Cache, see the tool documentation:

Don't see a tool that supports remote caching that you use? Let us know in our Discord Community!

How does it work?

Supported build tools can be configured to use Depot Cache, so that they store and retrieve build artifacts from Depot's remote cache. That cache can then be used from local development environments, CI/CD systems, or anywhere else you run your builds.

This speeds up your builds and tests by orders of magnitude, especially for large codebases, as those builds and tests become incremental. Instead of always having to rebuild from scratch, only the parts of your codebase that have changed are rebuilt, and only affected tests are re-run.

Cache retention policy

The default cache retention policy is to store the cache entries for 14 days with no limit on total cache size.

Configure the cache retention policy on your organization's settings page to control time based retention and cache size limits.

  • Available values for time based retention: 7 days, 14 days (default), 30 days
  • Available values for size based retention: 25 GB, 50 GB, 100 GB, 150 GB, 250 GB, 500 GB, No limit (default)

Note: Retention policy settings don't apply to Docker layer cache entries (shown as type docker in the Cache Explorer). To manage Docker cache retention, set cache policy per project in project Settings.

Where can I use Depot Cache?

Depot Cache is accessible anywhere you run your builds, in local development or from any CI/CD system. Additionally, all supported tools are pre-configured to use Depot Cache when using Depot GitHub Actions Runners.

This means that build artifacts are shared between different members of your team and sequential CI/CD jobs, making these builds and tests incremental.

Pricing

Depot Cache is available on all of our pricing plans. Each plan includes a block of cache storage. Each additional GB over the included amount is billed at $0.20 per GB of usage. We calculate usage by taking a snapshot every hour and then averaging out those snapshots over the month. For more information about plans and included usage, see the pricing page.