$0
Egress fees
Pull images across your build and deployment environments without BoringCache transfer charges.
Registry
Publish private images.
Deploy them anywhere.
Keep container images alongside your cache and build outputs. Push with the BoringCache CLI, then pull with Docker or any OCI client from the environments where you deploy.
acme/shop/web
Private repository
v1.2.0
linux/amd64
linux/arm64
Development
Staging
Production
Private image storage is already part of your plan.
Use one workspace for Cache, Artifacts, and Registry. There is no separate Registry activation or BoringCache egress charge.
30 days
Free trial
Try Cache, Artifacts and Registry. No credit card required.
Expand when you choose
Registry shares the namespace storage pool with Cache and Artifacts. On Standard and Large, an optional extra-storage budget adds capacity at $0.04/GB-month, capped at your budget. Regional storage is billed separately.
Build once. Deploy the image you tested.
Docker and OCI clients
Pull with Docker or any OCI client. Push from a BoringCache Docker build or from the local Docker engine with the BoringCache CLI.
Multi-platform images
Publish multi-platform images under one tag. Pull the image that matches your deployment.
Tags and exact digests
Name your releases with tags. Pin deployments to a digest to use the exact image you tested.
Keep versions without duplicating every layer.
Images in the same workspace Registry share matching layers. Keep more versions without storing a new copy of every unchanged layer.
Keep tagged images until you remove them. Cache cleanup does not touch your releases.
v1.1.0
App v1
v1.2.0
App v2
Shared base layers
Check who published an image before you pull it.
With a publisher policy, boringcache docker push records a signed attestation for the image digest. boringcache docker pull verifies the publisher, then pulls that exact digest. Docker and OCI clients that pull directly do not check the policy.
-
Publish
boringcache docker push signs the image digest
-
Verify
boringcache docker pull checks the pinned publisher
-
Pull
Docker pulls the verified digest
Give deployments read access. Keep publishing in CI.
Give deployments permission to pull and trusted builds permission to publish. Manage image access alongside Cache and Artifacts in your workspace.
Explore access controls →Scoped credentials
- Trusted builds Push images from CI Pull + push
- Deployments Pull the image you tested Pull only
Keep access limited to the workspaces a job needs, with repository-scoped grants for image pulls and pushes.
See what you publish
Browse repositories, tags, image details, storage usage, and pull activity from your workspace.
Managed Registry storage
BoringCache provisions and runs your Registry storage. Use it with the runners and deployment platforms you choose.
Benchmark
Push images 1.8× faster than GHCR. Pulls take about the same time on all four registries.
PostHog
GitHub · 4 vCPU · Linux amd64Push
Pull
Publish an image from your existing build.
Choose an image you already build. Push it to your workspace, then pull it with Docker or any OCI client when you deploy.
boringcache docker push app:latest --as app:latest