Skip to content

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.

Try BoringCache for 30 days

The trial includes BYOC and regional storage policies. Choose a paid plan to continue after the trial. Regional storage is available on every paid plan; BYOC requires Custom. Without one, you have seven days of read-only access before managed data deletion begins.

Plans

Standard

$19/month

For smaller projects and teams

200 GB shared storage

One namespace allowance for Cache, Artifacts and Registry.

1M build-storage requests included each month

14-day unused-cache retention

Unlimited collaborators and workspaces

All adapters, access controls and email support

Start 30-day trial

Large

$99/month

For larger projects and busy CI pipelines

1 TB shared storage

One namespace allowance for Cache, Artifacts and Registry.

5M build-storage requests included each month

14-day unused-cache retention

Unlimited collaborators and workspaces

All adapters, access controls and email support

Start 30-day trial

Custom

Contract pricing Managed storage and request allowances agreed in your contract

For teams that need contract storage terms, BYOC or high-read cache support.

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

Contact us

Extra storage and regions

Extra-storage budget

On card-billed Standard and Large, choose a monthly budget in Billing. The default is $0. Storage above the included pool costs $0.04/GB-month, measured daily and capped at your budget for each subscription billing period.

A $20 budget adds 500 GB to your storage limit. You pay for measured usage above the plan pool, up to $20. Lowering the budget keeps your data; new writes wait if usage exceeds the new limit. You cannot lower the budget below the charge already recorded in that billing period.

Regional storage

Automatic placement or one pinned region is included. A multi-region geography costs $0.03/GB-month of stored data. Specific regions cost $0.03/GB-month for each region after the first.

Regional storage is available on every paid plan and during the trial. On Standard and Large, regional usage is measured daily and billed monthly, separately from the extra-storage budget. Custom follows its contract. The no-card trial has no usage charges.

Shared storage and request allowances

Cache, Artifacts and Registry have separate retention and deletion controls. Storage and monthly requests are shared across the namespace.

Cache
Unused cache is removed after its retention period. When confirmed usage reaches the allowance, new uploads stop. Existing uploads can finish and stored content can be reused.
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. One storage pool serves all three products. Extra storage is optional and budget-capped; regional storage is billed separately.

Common questions.

What is included in the trial?
The 30-day trial includes the Large allowance: 1 TB shared storage and 5,000,000 storage requests for the whole trial. No credit card is required. Unused cache expires after 14 days. If the trial uses all of its requests, new saves stop and downloads continue. When you subscribe, billing starts and the plan you choose applies: 200 GB on Standard or 1 TB on Large. Existing data is kept; if it is above that allowance, new saves wait until usage fits.
What counts toward the request allowance?
Storage operations for Cache, Artifacts and Registry share one request allowance. One build or transfer can make several storage requests. The allowance counts requests reported by our storage provider; it is not a build limit or a count of CLI commands. Usage updates after the provider reports it.
What happens when my shared storage is full?
Writes that need more space in the shared allowance are rejected. Managed cache saves are skipped with a warning; managed Artifact uploads and Registry pushes that need more space are blocked. Existing caches, Artifacts, and images remain available. BoringCache does not delete data to make room. Writes can resume when retention or deletion frees enough space, or you increase your allowance. The extra-storage budget defaults to $0. On card-billed Standard and Large, you can set a budget in Billing to increase the storage limit. Extra storage is charged only within that budget; regional charges are separate.
Can I limit how much storage a product uses?
Workspace Settings for Cache, Artifacts and Registry let you cap new managed-storage writes within the shared allowance. A cap does not reserve space for that product. BYOC bytes are excluded from the allowance and write caps. Each product keeps its own retention and deletion rules.
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 I reach the request allowance?
During the trial, new saves, uploads and pushes stop when measured usage reaches the trial allowance, which covers the full 30 days. Downloads continue. Provider measurements arrive with a delay, so this is not an exact real-time cutoff. On Standard and Large, requests continue after the monthly allowance: reaching it does not block builds or add charges. Paid allowances reset each calendar month. You can check usage on your account's Usage page. If you consistently exceed the allowance, contact us to discuss a larger plan.
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) is available during the trial and on Custom. After the trial, BYOC requires Custom. Cache, Artifacts, and Registry can use your own S3-compatible storage. Cache and Artifacts support Google Cloud Storage with HMAC credentials and Azure Blob Storage. Your provider bills storage and transfers; BoringCache runs the hosted service for metadata and access control. BYOC storage has no BoringCache capacity limit and does not consume your managed storage allowance. Request policies and per-upload limits still apply.

Start a trial with one repository.

Try your own builds for 30 days. No card required.

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