Angos vs Cloudfleet Container Registry
Angos
angos.dev
Cloudfleet Container Registry
cloudfleet.aiSide by side
| Figure | Angos | Cloudfleet Container Registry |
|---|---|---|
| Price from | — | Free |
| Free plan | — | Yes |
| Free trial | — | — |
| Open source | — | — |
| Web | Yes | Yes |
| macOS | Yes | — |
| Linux | Yes | Yes |
| API | Yes | Yes |
| Self-hosted | Yes | — |
| Plans published | 0 | 1 |
| Spec score · Container Registries | 8.0 (#10) | 8.0 (#11) |
| Access control | CEL policies and optional webhooks control push, pull, and delete access per repository. | Administrators can push and pull images, while users have pull-only access; each organization has an isolated registry namespace. |
Plans
Cloudfleet Container Registry
- Cloudfleet Container Registry storageFree
In their own words
Cloudfleet Container Registry
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.