Pricing

Build storage. Unlimited collaborators.

Cache, Artifacts, and private images in one plan. Pay for the capacity your team needs, not the number of people using it.

Free

$0 /month No credit card required

For getting started, including open source.

50 GB build storage

Cache: 30 GB
Artifacts: 10 GB
Registry: 10 GB

7 days unused-cache retention

Unlimited collaborators and workspaces

500K build-storage requests included each month

All cache adapters and GitHub Actions

Insights and access controls

Community support

Install the CLI

For active teams

Standard

$19 /month

More storage and requests for active teams.

200 GB build storage

Cache: 150 GB
Artifacts: 20 GB
Registry: 30 GB

14 days unused-cache retention

Unlimited collaborators and workspaces

1M build-storage requests included each month

All cache adapters and GitHub Actions

Insights and access controls

Email support

Start with the CLI

Custom

Contract pricing Sized with you, then agreed in writing

For teams that need more storage, pinned locality, BYOC, replication, or high-read cache support.

1,100 GB build storage by default

Cache: 1,000 GB
Artifacts: 50 GB
Registry: 50 GB

Everything in Standard

Pinned storage locality near your busiest runners

More cache traffic, sized with you

Dedicated storage terms for high-read workloads

BYOC with your own S3-compatible bucket or Azure Blob container

Regional storage policies

Priority support

One plan. Separate product allowances.

Cache, Artifacts, and Registry each have their own storage allowance. The monthly request allowance is shared across all three.

Cache: Unused cache is reclaimed by retention or earlier when a workspace needs capacity.
Artifacts: Artifacts follow the retention you choose, including permanent retention, and are never reclaimed as cache.
Registry: Registry content remains until deletion; unreferenced data is garbage-collected after recovery windows.

Keep your existing CI and runners

Use Cache, Artifacts, and Registry with your existing build tools. Share build data across hosted CI, self-hosted runners, and local development.

What's included

Self-serve plans include Cache, Artifacts, private Registry storage, and one shared build-storage request allowance. No product activation, per-user pricing, remote compute bill, or metered storage overage charges.

Common questions.

What is included in the Free plan?

30 GB Cache, 10 GB Artifacts, and 10 GB Registry. 500K build-storage requests included each month. All cache adapters and unlimited collaborators are included.

What counts toward the request allowance?

Storage operations for Cache, Artifacts, and Registry share the account’s monthly allowance. You can inspect shared request usage in the workspace.

What happens when my cache storage is full?

BoringCache reclaims older or unused cache instead of charging an overage. New saves continue. Artifacts and container images are not deleted to make room for cache.

Which build tools can I use?

Cache directories with the CLI or use native cache integrations for tools such as Docker, Bazel, Turborepo, Nx, Gradle, Cargo, Go, ccache, sccache, and Xcode. Share cache across CI and local development.

What happens when Free or Standard exceeds its request allowance?

On Free and Standard, requests continue after you reach the monthly allowance. Reaching it does not block builds, require an immediate upgrade, or trigger request-overage charges. You can check usage on your account’s Usage page; automatic allowance warnings are not currently sent. If you consistently exceed the allowance, contact us to discuss a suitable plan or storage arrangement.

How is this different from actions/cache?

actions/cache is useful inside GitHub Actions. BoringCache shares cached results across compatible builds in GitHub Actions, other CI systems, and local development, with restore-only access for pull requests.

How is this different from a remote builder?

A remote builder runs the build somewhere else. With BoringCache, builds run on your existing CI and runners and reuse compatible cached results.

Do we need to change CI providers?

No. Keep the runners, workflows, and tools you already use. Use BoringCache to share cache across them.

Do you charge egress fees?

We do not charge egress fees. Storage operations across Cache, Artifacts, and Registry count toward the plan's shared request allowance.

What is BYOC storage?

BYOC (Bring Your Own Cloud) stores Cache and Artifacts in your own S3-compatible bucket or Azure Blob container on Custom. Registry storage stays managed. Your storage provider bills storage and transfers; BoringCache handles metadata, access, and reuse.

Start free with one repository.

Try the integration before deciding which plan fits your build volume.

curl -sSL https://install.boringcache.com/install.sh | sh
cd your-project
boringcache onboard

Get started Talk about Custom