Django-OCI vs IDIA Singularity Registry
Django-OCI
vsoch.github.ioIDIA Singularity Registry
sregistry.idia.ac.zaSide by side
| Figure | Django-OCI | IDIA Singularity Registry |
|---|---|---|
| Price from | Free | — |
| Free plan | Yes | — |
| Free trial | — | — |
| Open source | — | — |
| Web | — | Yes |
| Linux | Yes | Yes |
| API | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 0 |
| Spec score · Container Registries | 8.6 (#4) | 7.8 (#17) |
| API | It provides distribution-spec API endpoints for pushing, pulling, and interacting with a registry. | The registry API used by Singularity and sregistry clients is available through standard and Swagger schema views. |
| Authentication | Authentication uses a Docker-style OAuth 2.0 flow with username and token credentials and expiring JWT bearer tokens. | Users can obtain a user token from the registry interface for authenticated pushes, and API requests present tokens in an Authorization header. |
| Client integrations | There is no official client; the documentation describes Python Requests and the Reggie client as ways to interact with a registry. | The documentation describes pulling with the Singularity client and using the sregistry command line client to push, pull, list, and delete containers. |
| Support | The project asks users who need help to open an issue. | The About page directs registry software issues to GitHub and local registry support requests to [email protected]. |
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.
IDIA Singularity Registry
IDIA Singularity Registry has no write-up on Specifiction yet; its figures are above.