Private Docker Registry
Host private container images and OCI artifacts on the standard Docker Registry HTTP API V2. No egress fees, a generous transfer allowance included, and the same predictable pricing as every other repository you keep with us.
docker login YOUR_ORG.mycloudrepo.io
docker push YOUR_ORG.mycloudrepo.io/repositories/YOUR_REPO/my-app:1.0.0
docker pull YOUR_ORG.mycloudrepo.io/repositories/YOUR_REPO/my-app:1.0.0Everything you need for container images
A production Docker registry that speaks the specification your tools already speak, on a bill you can predict before your CI runs.
- Zero Egress Fees
- Every CI job pulls its base images. We do not meter transfer per GB: every plan includes a generous transfer allowance, with reach-out-first overage rather than a surprise bill.
- Standard Registry HTTP API V2
- docker, podman, nerdctl, Buildah, Kaniko and Skopeo all connect with nothing beyond a docker login. No plugin, no proprietary client.
- Repository Tokens, Not Portal Passwords
- Sign in with a repository-scoped token you can revoke on its own, separately from anyone’s portal password. Behind it the registry issues a short-lived, operation-scoped token per request, which the client holds in memory only.
- Helm Charts in the Same Repository
- Helm 3 stores charts as OCI artifacts, so your charts sit beside your images in the same repository, reached the same way. Nothing extra to enable.
- Group Repositories
- Give a team one registry address that resolves across several repositories in a priority order you set. Each member keeps its own permissions.
- Public or Private, Per Repository
- Mark a repository public for anonymous pulls, or keep it private so every read and write is gated and isolated to your organization.
Quick Setup Guide
Four steps from a fresh repository to an image your team can pull.
Create a Generic repository token
In the admin portal, open Repository Tokens and create one in the Generic format. Choose the repositories it may reach. The value is shown once.
# Admin portal -> Repository Tokens -> Create token
# Format: Generic
#
# Owners are not exempt: an organization owner's portal
# sign-in is refused at the registry. Mint a token.
Log in to the host
docker login takes the host and nothing more. The user name is the email of the account that minted the token; the token itself is what you paste at the prompt.
docker login YOUR_ORG.mycloudrepo.io
Tag and push
The image reference carries a literal repositories/ segment, the same segment your Maven, npm and PyPI repositories are addressed under.
docker tag my-app:1.0.0 YOUR_ORG.mycloudrepo.io/repositories/YOUR_REPO/my-app:1.0.0
docker push YOUR_ORG.mycloudrepo.io/repositories/YOUR_REPO/my-app:1.0.0
Pull from anywhere
Same reference, same sign-in. Public repositories serve anonymous pulls; private ones require the login above.
docker pull YOUR_ORG.mycloudrepo.io/repositories/YOUR_REPO/my-app:1.0.0
The one thing worth reading twice
docker login takes the host on its own. The image reference
is what carries
/repositories/YOUR_REPO/. Docker keeps one credential
per host and quietly drops any path you type at login, so adding the repository there still reports
Login Succeeded and gives you no hint it was discarded. Log in to the host; let the reference carry the
repository.
One Registry, Beyond the Basics
The same repository serves your images, your charts, and a team-wide address that spans several repositories.
Group Repositories
Point developers at one address and resolve it across several repositories in a priority order you set. A group holds no storage of its own, so it is read-only: push to the member repository and the image appears through the group at once. Permissions still apply per member, so a group never widens access.
# A group is addressed like any repository
docker pull YOUR_ORG.mycloudrepo.io/repositories/YOUR_GROUP/my-app:1.0.0Helm Charts over OCI
There is no separate Helm repository type and no
index.yaml to maintain. Push charts to a Docker repository
over
oci://. The push URL ends at the repository,
because Helm appends the chart name and version itself.
helm push my-chart-0.1.0.tgz \
oci://YOUR_ORG.mycloudrepo.io/repositories/YOUR_REPOFull walkthroughs, the CI/CD recipe, and the token model are in the Docker documentation.
Calculate Your Savings
See how much you can save compared to JFrog Artifactory and Nexus
Common Scenarios
JFrog Artifactory
Consumption25GB included. $1.25/GB (26-1204GB), $1.00/GB (1205-2024GB), $0.75/GB (2025+GB)
Nexus Repository
Consumption20GB included. $1.10/GB (first 1000GB), $0.90/GB (above 1000GB)
CloudRepo
PredictableNo egress fees — we never meter downloads per GB. Fair-use transfer with reach-out-first overage.
Your Savings with CloudRepo
Compared to the higher-priced competitor
Ready to host your container images?
Start your 14-day free trial. No credit card required.