Alibaba Cloud Container Registry vs Django-OCI
Alibaba Cloud Container Registry
alibabacloud.comDjango-OCI
vsoch.github.ioSide by side
| Figure | Alibaba Cloud Container Registry | Django-OCI |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | — |
| Web | Yes | — |
| Windows | Yes | — |
| Linux | Yes | Yes |
| API | Yes | Yes |
| Self-hosted | — | Yes |
| Plans published | 6 | 1 |
| Spec score · Container Registries | 9.0 (#2) | 8.6 (#4) |
| API | ACR exposes OpenAPI version 2018-12-01 with public endpoints in the form cr.{regionId}.aliyuncs.com and VPC endpoints in the form cr-vpc.{regionId}.aliyuncs.com. | It provides distribution-spec API endpoints for pushing, pulling, and interacting with a registry. |
| What it does | Alibaba Cloud Container Registry is a fully managed service for storing, securing and distributing container images and cloud-native artifacts. | The Django module lets Python developers build OCI compliant registries with endpoints to push, pull, and interact with container images. |
Plans
Alibaba Cloud Container Registry
- Personal EditionPriced on request
- Enterprise Basic EditionPriced on request
- Enterprise Advanced EditionPriced on request
- Personal EditionFree
- Enterprise Edition AdvancedPriced on request
- Enterprise Edition BasicPriced on request
In their own words
Alibaba Cloud Container Registry
Alibaba Cloud Container Registry has no write-up on Specifiction yet; its figures are above.
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.