Cloudfleet Container Registry vs Django-OCI

Cloudfleet Container Registry, or CFCR, is a managed OCI-compliant registry for storing, sharing, and managing container images. It supports Docker images, multi-architecture images, Helm charts, and other OCI artifacts, and is included with every Cloudfleet organization without extra provisioning. Regions are available in Europe, North America, and Asia Pacific; the European region uses EU-based infrastructure. Teams can push and pull through the standard Docker CLI or Docker Registry HTTP API V2. Cloudfleet Kubernetes Engine clusters authenticate automatically with short-lived credentials, avoiding image pull secrets or service accounts. CI/CD examples cover GitHub Actions, GitLab CI, Jenkins, CircleCI, and Azure DevOps. Each organization receives an isolated namespace, with administrators able to push and pull while users have pull-only access. Authenticated users and Cloudfleet Kubernetes Engine clusters have no pull rate limits. The first 5 GB of storage is free, unlimited data transfer is listed as free, and Kubernetes Engine pulls have no egress fees.

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.