Google Cloud: Artifact Registry vs Container Registry

Artifact Registry includes all the features of Container Registry (storing container images) as well as new features for language-specific artifact repositories.

From https://cloud.google.com/artifact-registry/docs/transition/transition-from-gcr

Artifact Registry is the evolution of Container Registry. As a fully-managed service with support for both container images and non-container artifacts, Artifact Registry extends the capabilities of Container Registry.

From https://cloud.google.com/blog/products/application-development/understanding-artifact-registry-vs-container-registry, the key improvements are:

• "A unified control plane for container, OS and language repositories" - AR is for storing language and OS packages as well
• "A more granular permission model with Cloud IAM" - permissions can be per-repository
• "Repositories in the region of your choice" - can choose individual regions for repositories instead of multi-regions
• "A pricing model that respects your region" - higher costs for storage, but potentially lower (or no) costs for network egress
• "Part of a secure supply chain" - works directly with other Google Cloud 'secure supply chain' products