We performed a comparison between Azure Container Registry and JFrog Container Registry based on real PeerSpot user reviews.
Find out what your peers are saying about Amazon Web Services (AWS), GoHarbor, Microsoft and others in Container Registry."Feature-wise, the security model and access controls are pretty straightforward and valuable"
"One of the benefits of this solution is that it's private and secure."
"The continuity screen is a valuable feature."
"It's great for storing images on containers."
"The solution has built-in resiliency and replication zone availability so it is very stable."
"Provides secure duplication and the option for service webhooks."
"The most valuable feature is that it's easy to download, install and manage."
"The scanning of Docker images is the most valuable feature."
"We use the solution to compile the codes before publishing them. We utilize third-party containers and codes, downloading them to the JFrog Container Registry. Developers then access it from the JFrog Container Registry, and there's a specific job responsible for running and validating all security checks, ensuring compatibility. If there are any issues or if packages require updates, we manage those updates through this system."
"It supports multi-cloud deployments across AWS, Azure, and GCP."
"The solution has become more popular in the last few years but I find that the technical support has not increased their knowledge base, so more knowledgeable support staff can help improve the solution."
"The solution has no areas that need improvement."
"They can improve their scalability."
"The deployment is an area that needs improvement, as it can take some time to deploy."
"The solution could always improve its security measures with regard to access."
"The accessibility of Azure Container Registry also has room for improvement because the solution is not always accessible 24 x 7. I experienced this three times when the service wasn't responding, so I could not push or pull images, and I had to decommission Azure Container Registry and redeploy it."
"It should be easier to use. It can have more graphical interfaces to manage containers. At present, the handling or management of the containers is very basic."
"The setup process is mildly complex. There is no straightforward management platform, so there's a level of complexity to it."
"In my experience, there was a bit of a learning curve at the beginning. It can be somewhat challenging to install and get started."
"One challenge we face is related to performance. Our integration involves GitHab and JFrog Container Registry, with pipelines fetching data from GitHub and JFrog Container Registry for third-party code. However, there are instances where this process can slow down the pipeline."
Azure Container Registry is ranked 3rd in Container Registry with 16 reviews while JFrog Container Registry is ranked 4th in Container Registry with 2 reviews. Azure Container Registry is rated 8.2, while JFrog Container Registry is rated 8.0. The top reviewer of Azure Container Registry writes "Configurations are quite simple with tokens that set folder structure or access levels". On the other hand, the top reviewer of JFrog Container Registry writes "Acts as a central repository and comes with code scanning feature ". Azure Container Registry is most compared with Amazon ECR, Harbor, Oracle Cloud Infrastructure (OCI) and Red Hat Quay, whereas JFrog Container Registry is most compared with Harbor, Amazon ECR, Red Hat Quay and VMware Harbor Registry.
See our list of best Container Registry vendors.
We monitor all Container Registry reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.