Build and test caching: Improve build and test performance by up to 10x

By acquiring the advanced caching and CDN technology of, Bitrise brings to market an uncontested build and test caching solution available nowhere else. The first of its kind, and fully managed by Bitrise requiring no setup or maintenance, you can use our out-of-the-box cache Steps containing all the code you need to perform build and test caching tasks at the highest velocity.

Ground-breaking technology. The combination of the Bitrise platform with tech results in a superpowered new CI platform that can easily and seamlessly cache the build actions of some of the most popular build tools, making your mobile CI pipelines so much faster.

A drop-in solution for most build tools

Advanced, yet easy to use, our build and test caching support is a drop-in solution for the most popular build tools, eliminating the need for costly additional setup and infrastructure. By using our Build Cache Steps*, previously compiled outputs from previous CI jobs can be reused in your next build.
*Steps: Ready-to-use, out-of-the-box build tasks that require no setup, no maintenance, and all the code you need.

Reduction in data transfer costs

By utilizing co-located CDN edge nodes in our data centers and the public cloud, build speeds increase greatly and your bandwidth costs are reduced or eliminated entirely.

Unmatched performance benefits

Speed up feedback loops, iterate faster, and multiply app build performance by up to 10x. The technologies of and Bitrise provides the backbone for powerful performance enhancements to your mobile application CI workflows running on Bitrise. Mobile teams using our technology have reported up to a 94% reduction in build times.

Supercharge developers and CI

Reliable, shared artifact cache. Local developer workstations and CI jobs both can share the same build outputs and test results, maximizing cache hit rates and keeping build and test times low both in CI and local development.

About build and test caching

Different from dependency caching that caches third-party dependencies, Bitrise’s advanced build caching functionality allows for faster build and test runs by intelligently caching the built outputs of the modules and libraries that make up your application, generated when compiling your first-party code.

Test runs, like unit test runs, can also be cached using this approach (test avoidance) in some build systems (such as Bazel or Gradle). This means that tests that are unaffected by your code changes can avoid being rerun at all — resulting in massively reduced build and test times.

Additionally, local build and test performance can be improved by allowing developers direct access to the shared caching infrastructure managed by Bitrise–provided you’re using a supported build system.

Supported build systems

Our Build Cache currently supports both seamless CI/CD integration as well as remote connectivity (supporting local development workflows) for the following tools:

Types of caching solutions from Bitrise

Bitrise offers two types of caching solutions:

Build and test caching

The first of its kind, and 100% managed by Bitrise requiring no setup or maintenance, you can use our out-of-the-box cache Steps to cache your build and test tasks or artifacts at the highest velocity. Our world-class CDN ensures that your cache is stored right next to where it is needed by the machines running those builds, which provides additional speed gains.
Talk to us

Dependency caching

Dependency caching is used to cache your third-party dependencies. Your workflow runs will save your dependencies for fast reuse so that they need not be downloaded off the internet every time the workflow is run. Bitrise supports preconfigured caching steps for major package managers and generic caching steps that allow you to customize your caching and support any package manager of your choice.
Learn more


Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum.

What are credits?

Credits represent the available buildtime associated with your Bitrise plan. One credit represents one minute of buildtime on our standard Linux compute option, or 30 seconds on our standard MacOS option. You can find a full breakdown of the compute options and their associate credit usage here.

How do I calculate how many credits my team will need?

On a Teams plan, you will receive a free trial for Teams and 500 credits to start building. When the Trial ends, we will suggest a credit bundle that will fit your needs. If you feel like 500 credits won’t be enough to sufficiently trial Bitrise, contact us and we’ll put together a custom trial for you.

What makes the Enterprise Build Platform different from the Teams or Velocity plans?

The Enterprise Build Platform is offered as a virtual private environment, and is designed to suit the needs of organisations with specific requirements for performance, resources, or security and control.Our other plans run on our multi-tenant cloud environment, where resources are shared among the user-base.

What’s the difference between Teams and Velocity?

On our Teams plan, smaller teams can quickly get started with our most popular compute options, and credit packages that are tailored to their specific needs. Here, you’ll easily selfserve an up- or downgrade as your needs evolve.

On Velocity, bigger teams find our full suit of features and functionality, designed to help them manage complex mobile engineering processes. Teams can run even more concurrent processes, and have additional, faster compute options available.

How do I upgrade to Velocity or the Enterprise Build Platform once I’ve signed up?

Talk to us. The team will make sure the plan fits your exact needs.

You might also be interested in

Increase your build speed by up to 10x