Django-OCI vs Volcengine Container Registry
Django-OCI
vsoch.github.ioVolcengine Container Registry
volcengine.comSide by side
| Figure | Django-OCI | Volcengine Container Registry |
|---|---|---|
| Price from | Free | 50 CNY/mo |
| Free plan | Yes | — |
| Free trial | — | — |
| Open source | — | — |
| Web | — | Yes |
| Windows | — | Yes |
| macOS | — | Yes |
| Linux | Yes | Yes |
| iOS | — | Yes |
| Android | — | Yes |
| API | Yes | Yes |
| Self-hosted | Yes | — |
| Plans published | 1 | 3 |
| Spec score · Container Registries | 8.6 (#4) | 7.3 (#39) |
| API | It provides distribution-spec API endpoints for pushing, pulling, and interacting with a registry. | The Container Registry OpenAPI lets developers manage service modules through HTTPS or HTTP requests. |
| Purpose | Django-OCI is an open-source registry module for Python developers using Django to build OCI-compliant registries. | Container Registry hosts OCI-compliant cloud-native artifacts such as container images and Helm charts for lifecycle management. |
Plans
Volcengine Container Registry
- Trial EditionFree
- Standard instance · Micro Edition subscription50 CNY a month
- Standard instance · Standard Edition subscription1,349 CNY a month
In their own words
Django-OCI
Django-OCI is free, open-source software for Python developers building registries that follow the OpenContainers Distribution Specification. The Django module exposes API endpoints for pushing, pulling, and interacting with container images, and can run in a virtual environment or within a container-orchestrated registry. Installation is available through pip or a GitHub checkout and includes Django Rest Framework. Filesystem storage is the default option, intended for smaller registries without external cloud storage. Authentication uses a Docker-style OAuth 2.0 flow with username and account-token credentials plus JWT access tokens. Configuration covers URL prefixes, specification version, content types, storage, authentication, token and session expiry, request limits, and manifest-tag deletion. There is no frontend for viewing containers. Private repositories and repository ownership or contributors are not implemented. The project is described as early development, with most goals still under development. Python tests and distribution-spec conformance testing are documented. Developers are asked to consider GDPR compliance, open an issue for help, and review the project license before use.
Volcengine Container Registry
Volcengine Container Registry stores OCI-compliant artifacts, including container images and Helm charts, and provides tools to manage their lifecycle. Users can push, pull, and clean up images with Docker, Nerdctl, or Helm. Image scans can report vulnerabilities, malicious or unexpected files, and possible remediation. The service also supports IAM policies for user authorization and resource-level permissions. Standard Edition instances can use server-side image encryption when enabled at creation. Standard Edition can replicate images and Helm charts across instances, regions, and repositories, with up to five enabled rules per account. Proxy caches can draw from Docker Hub, GHCR, and self-hosted Docker registries. The registry integrates with Volcengine Kubernetes Engine for internal-network image pulls, and Standard Edition supports P2P acceleration for large cluster pulls. Micro Edition provides five namespaces and 500 GiB of storage; Standard Edition provides 50 namespaces and unlimited namespace storage by default. A free Trial Edition costs nothing, but is quota-limited and cannot expand its quota. Subscription prices listed for Chinese mainland are 50 CNY a month for Micro Edition and 1,349 CNY a month for Standard Edition, per instance.