Harbor vs Samsung Cloud Platform Container Registry

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.

Samsung Cloud Platform Container Registry stores, manages, and shares container images and OCI-standard artifacts in Samsung Cloud Platform. Stored content includes container images, Helm charts, and OCI artifacts, with Docker Registry V2 API support. Teams can create or delete registries, manage repository access, and push, pull, view, or remove image tags. Images are retrievable through the standard Docker CLI, and a disaster-recovery registry can provide repository redundancy. Object Storage integration allows registry capacity to be configured as unlimited. Repository security policies and image lifecycle policies include a simulation function. CVE-based scanning reports findings for images, packages, secrets, and language packages. Images are encrypted in Object Storage and transferred over HTTPS, while access follows Samsung Cloud Platform IAM resource-based policies. Interfaces include web UI, API, and CLI. Integrations cover IDP, IAM, Object Storage, Cloud Monitoring, and Logging/Audit. Usage monitoring and event logs are provided. Billing uses stored data and hours, plus scan counts; pricing is on request.