Cloudflare Serverless Registry vs Django-OCI
Cloudflare Serverless Registry
github.comDjango-OCI
vsoch.github.ioSide by side
| Figure | Cloudflare Serverless Registry | Django-OCI |
|---|---|---|
| Price from | — | Free |
| Free plan | — | Yes |
| Free trial | — | — |
| Open source | — | — |
| Windows | Yes | — |
| macOS | Yes | — |
| Linux | Yes | Yes |
| API | — | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 1 |
| Spec score · Container Registries | 7.8 (#15) | 8.6 (#4) |
| Authentication | It supports username/password and public-key JWT authentication. | Authentication uses a Docker-style OAuth 2.0 flow with username and token credentials and expiring JWT bearer tokens. |
| Deployment | The deployment instructions configure a Cloudflare Worker and an R2 bucket using Wrangler. | It can be deployed locally in a virtual environment or as part of a container orchestrated registry. |
| License | The repository is licensed under the Apache License 2.0. | Use is governed by the project license, which users are asked to read and agree to before using the software. |
| Purpose | The project provides a container registry implementation in Cloudflare Workers backed by R2. | Django-OCI is an open-source registry module for Python developers using Django to build OCI-compliant registries. |
Plans
Cloudflare Serverless Registry
- Cloudflare R2 usage-based chargesPrice not published
In their own words
Cloudflare Serverless Registry
Cloudflare Serverless 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.