UpCloud Managed Container Registry is in beta. It is fully functional, but standard UpCloud SLAs do not apply during the beta period. See Limitations for what isn't available yet.
Managed Container Registry
UpCloud Managed Container Registry is a private registry for your container images and any other OCI-compliant artifacts, such as Helm charts and WebAssembly (Wasm) modules. Push images from your workstation or CI pipeline and pull them to your Cloud Servers, Managed Kubernetes clusters, or any other container runtime.
The registry is fully managed and OCI-compliant, so it works with the Docker CLI and other standard tools. Access is controlled with registry users and their permissions, an IP allowlist, and optional anonymous pulls. On the Pro plan, servers and clusters can reach the registry over SDN Private Networks.
In this section
- Availability: the regions where you can create a registry, and how they relate to locations and private networks.
- Plans: the Starter and Pro plans, their limits, and how to change plan.
- Billing: how the plan price and additional storage are billed.
- Access control: registry users and their permissions, the IP allowlist, and anonymous pulls.
- Networking: reaching the registry over its public endpoint or, on the Pro plan, over SDN Private Networks.
- Repositories and tags: how repositories, tags, and digests work, and how to promote and delete them.
- Webhooks: sending registry events to your own HTTP endpoint.
- Limitations: what isn't available during the beta.
- FAQ: answers to common questions about users, networking, storage, and webhooks.
Latest changelog entries
Guides
How to get started with UpCloud Container Registry
How to use Container Registry with Managed Kubernetes
How to deploy automatically with Container Registry webhooks
How to store OpenTofu modules and other files in Container Registry