Django-OCI vs Harbor
Django-OCI
vsoch.github.ioHarbor
goharbor.ioSide by side
| Figure | Django-OCI | Harbor |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | — |
| Web | — | Yes |
| Linux | Yes | Yes |
| API | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 1 |
| Spec score · Container Registries | 8.6 (#4) | 7.9 (#13) |
| Authentication | Authentication uses a Docker-style OAuth 2.0 flow with username and token credentials and expiring JWT bearer tokens. | Harbor supports database, LDAP/Active Directory, and OIDC authentication; choosing database authentication and adding local users prevents switching to another mode. |
| Deployment | It can be deployed locally in a virtual environment or as part of a container orchestrated registry. | Harbor can be installed on Kubernetes or on a system with Docker support. |
| What it does | The Django module lets Python developers build OCI compliant registries with endpoints to push, pull, and interact with container images. | Harbor is an open source registry for securely managing artifacts across cloud native platforms such as Kubernetes and Docker. |
Plans
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.
Harbor
Harbor is an open-source registry for managing artifacts across cloud-native platforms such as Kubernetes and Docker. It offers a web UI and extensible API, and can be installed on Kubernetes or a system with Docker support. Security features include policies, role-based access control, vulnerability scanning, and image signing and validation. Image scanning uses Trivy when enabled during installation, and Harbor can connect to additional scanners. It replicates images and charts to or from other registries in pull or push mode; listed adapters include Docker Hub, Amazon ECR, Google Container Registry, Azure Container Registry, and GitLab Registry. Authentication options are database, LDAP/Active Directory, and OIDC, though choosing database authentication and adding local users prevents a later switch to another mode. Project storage quotas are unlimited by default but can be set globally or per project. Robot account secrets are not stored by Harbor, so they must be saved when created; robot accounts cannot log into the user interface. Harbor is a CNCF Graduated project. HTTPS is recommended for production use.