Django-OCI vs Keppel
Django-OCI
vsoch.github.ioKeppel
github.comSide by side
| Figure | Django-OCI | Keppel |
|---|---|---|
| Price from | Free | — |
| Free plan | Yes | — |
| Free trial | — | — |
| Open source | — | — |
| Linux | Yes | Yes |
| API | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 0 |
| Spec score · Container Registries | 8.6 (#4) | 7.3 (#36) |
| Deployment | It can be deployed locally in a virtual environment or as part of a container orchestrated registry. | The project says to build with make, install with make install, or build a Docker image; server and client commands are in one binary. |
| License | Use is governed by the project license, which users are asked to read and agree to before using the software. | The repository lists the Apache-2.0 license. |
| Storage | Filesystem is the currently supported default storage backend, intended for smaller registries that cannot use an external resource such as cloud storage. | Each customer account gets separate backing storage, allowing storage quota and usage to be tracked by that storage. |
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.