Volcengine Container Registry

Volcengine Container Registry hosts OCI-compliant cloud-native artifacts, including container images and Helm charts, and supports their lifecycle management. Developers can push, pull, and clean up images using Docker, Nerdctl, or Helm. Image scanning can report vulnerabilities, malicious or unexpected files, and remediation suggestions. IAM policies provide user authorization and resource-level permission controls. Standard Edition can replicate images and Helm charts across instances, regions, and repositories, with up to five enabled replication rules per account. It can also enable server-side encryption for image data when an instance is created. Proxy cache registries can cache external sources such as Docker Hub, GHCR, and self-hosted Docker registries. The service integrates with Volcengine Kubernetes Engine for internal-network image pulls; Standard Edition also supports P2P acceleration for large-scale cluster pulls. Micro Edition is aimed at individual developers, startup teams, and development or test environments, with five namespaces and 500 GiB of namespace storage. Standard Edition allows 50 namespaces and unlimited namespace storage by default. A free Trial Edition is quota-limited and does not support quota expansion.

Volcengine Container Registry covers artifact storage, scanning, access control, and distribution workflows. Edition limits matter: Micro has fixed namespace and storage caps, while Standard offers broader capacity and replication.

Micro Edition is positioned for individual developers, startup teams, development and test environments, and small image workloads. Teams needing broader namespace capacity or cross-region replication may consider Standard Edition.

Volcengine Container Registry is a managed home for container images, Helm charts, and other OCI artifacts. It fits developers and teams already building on Volcengine, particularly those deploying through Volcengine Kubernetes Engine. The feature set reaches from scanning to cross-region replication, but the most useful distribution controls sit in the much more expensive Standard Edition.

Overview

The service handles the core artifact cycle: push, pull, and clean up images. Docker, Nerdctl, and Helm are documented clients, and its OpenAPI lets developers manage service modules with HTTP or HTTPS requests. Support for OCI artifacts, immutable tags, retention policies, and lifecycle rules gives teams options for managing both artifact formats and repository hygiene.

Its clearest advantage is fit with Volcengine infrastructure. Volcengine Kubernetes Engine can pull images over the internal network, and Standard Edition adds peer-to-peer acceleration for large cluster pulls. Proxy cache registries can also cache external sources such as Docker Hub, GHCR, and self-hosted Docker registries. Teams operating across cloud platforms may find those ecosystem-specific strengths less decisive.

Key features

Security and access

Image scanning reports vulnerabilities, malicious files, unexpected files, and remediation suggestions. That makes it useful for surfacing image issues during registry workflows. IAM policies support user authorization and resource-level permissions. Standard Edition can enable server-side encryption for image data when an instance is created, so encryption must be part of the initial instance setup.

Replication and distribution

Standard Edition can replicate images and Helm charts across instances, regions, and repositories, with up to five enabled replication rules per account. This suits teams coordinating artifacts across multiple deployments, though the rule cap constrains how many replication paths can be active at once. P2P acceleration targets large-scale cluster pulls, where distributing images efficiently matters more than keeping registry costs low.

Interfaces and compatibility

The OpenAPI supports service management through HTTP or HTTPS requests, while Docker, Nerdctl, and Helm cover documented artifact push and pull workflows. The service also supports S3 compatibility and object versioning, alongside object immutability. These options broaden how teams can organize and manage stored data.

Pricing

The free Trial Edition costs nothing on a shared instance. It is quota-limited, does not support quota expansion, and has no stated duration, making it more suitable for a constrained evaluation than a workload that may grow.

Micro Edition subscription costs CN¥50 a month per instance in Chinese mainland regions; the published rate is 70 CNY/month/instance in China (Hong Kong) and other regions. It allows five namespaces and 500 GiB of namespace storage. That is a low-cost fit for individual developers, startup teams, development and test environments, and small image workloads, but its fixed capacity can become a boundary as repositories and teams expand.

Standard Edition subscription costs CN¥1,349 a month per instance in Chinese mainland regions, with a published rate of 1868 CNY/month/instance in China (Hong Kong) and other regions. It allows 50 namespaces and unlimited namespace storage by default, and adds replication and P2P acceleration. The higher price is easier to justify when those distribution capabilities or expanded capacity are operational requirements; smaller workloads may get little practical benefit for the added monthly cost.

Platforms

Volcengine Container Registry is listed for Android, iOS, Linux, macOS, Windows, web, and API use. Docker, Nerdctl, and Helm are the documented clients for working with artifacts.

Who it's for

Micro Edition is aimed at individual developers, startup teams, test environments, and small image workloads that can stay within five namespaces and 500 GiB. Teams using Volcengine Kubernetes Engine can benefit from internal-network image pulls. Standard Edition is a stronger fit for organizations that need multi-region replication, larger namespace capacity, or accelerated cluster pulls. A team seeking those controls at a lower recurring price, or one without a Volcengine deployment footprint, has less reason to choose it.

Pros and cons

• Useful image scanning: Reports vulnerabilities, malicious and unexpected files, and remediation suggestions.
• Strong Volcengine deployment fit: Kubernetes Engine pulls images over the internal network, with P2P acceleration available on Standard Edition.
• Broad artifact management: Supports OCI artifacts, Helm charts, immutable tags, retention policies, and lifecycle rules.
• Micro capacity is bounded: Five namespaces and 500 GiB may limit teams with growing repositories.
• Standard Edition costs substantially more: Its CN¥1,349 monthly mainland rate is a steep step up from Micro's CN¥50.
• Replication has a rule cap: Accounts can have up to five enabled rules at once.

Alternatives

Samsung Cloud Platform Container Registry is another paid registry, with usage-based billing tied to stored data and hours, plus scan charges by scan count; consider it if that billing structure better matches your usage.

PolyglotPiranha is a free option for API, iOS, Linux, macOS, and self-hosted environments.

8gears Container Registry has a free Individuals plan with 1 GB storage and unlimited private repositories, making it worth considering for a small private-repository footprint.

Chainguard Registry offers a free-images plan; consider it if that plan's image scope fits your needs.

Django-OCI is a free, self-hosted option for API and Linux use.

Docker Desktop includes Docker Engine and Kubernetes, Docker Hub, Docker Scout, and Docker Debug in its free Personal plan; it may suit readers seeking those tools together.

Inedo ProGet offers a free edition with unlimited feeds for private packages and Docker, alongside limited security and compliance features.

JFrog Container Registry has a free self-managed edition supporting Docker, OCI, Helm, Helm OCI, and Generic artifacts, without Xray.

Verdict

Choose Volcengine Container Registry if your team runs workloads on Volcengine and needs registry controls that extend to scanning, permissions, and—on Standard Edition—replication or high-volume cluster distribution. Micro keeps the entry price modest but caps namespace and storage capacity; Standard unlocks broader operations at a much higher monthly cost. Look elsewhere if those Volcengine integrations do not matter or if your workload cannot justify Standard Edition's price.