I have not used the image vulnerability scanning feature of Red Hat Quay yet; I'm going to learn about this. Regarding geo-replication in maintaining consistent access to container images, I have found no issues. If I store the image, I can easily pull the image without encountering any problems in Quay.io. I have no experience with how role-based access control has helped manage permissions in my organization. I usually measure the effectiveness of Red Hat Quay's extensibility with my existing systems, though I have not used that functionality. Red Hat Quay is not currently deployed on cloud or on-premises in my organization as it is only an institution with no use for cloud on-premises. I use Red Hat Quay only with the free version. I have used documentation for Red Hat Quay, as I have created extensive documentation myself because I am the trainer. I prepare many documents for the students on how to use it, how to manage the registry, and how to manage the images stored in Quay.io. My impression of the documentation that Red Hat provides for Quay is that it is improved; there is no need for further enhancement. The book contents are very structured, and the course name is Specialization in Containers, DO188. It is structured documentation to use the Quay.io account from the beginning to the end of the process. On a scale of 1-10, I rate Red Hat Quay an 8.
Sr. DevOps Engineer (OpenShift/Kubernetes) at a insurance company with 10,001+ employees
Real User
Top 5
Aug 18, 2025
I still have experience with Red Hat solutions, specifically with OpenShift and Red Hat Quay. I don't have experience with Red Hat AMQ, Satellite, or API Management, as those are handled by a platform team. My scope is only in the container platform and associated tools. Our experience with Red Hat Quay is measured by repositories rather than users. I don't get involved with licensing for Red Hat Quay as that's handled by a separate accounts team. We have an agreement with Red Hat where we receive everything in a bundle, so individual licensing costs aren't a concern. Based on my experience, I rate Red Hat Quay an 8 out of 10.
Cloud Specialist at a tech services company with 51-200 employees
Real User
Mar 16, 2021
I would recommend this solution to others who are interested in using it. We are system integrators and we provide support. I would rate Red Hat Quay an eight out of ten.
Red Hat Quay is a private container registry that stores, builds, and deploys container images. It analyzes your images for security vulnerabilities, identifying potential issues that can help you mitigate security risks.
I have not used the image vulnerability scanning feature of Red Hat Quay yet; I'm going to learn about this. Regarding geo-replication in maintaining consistent access to container images, I have found no issues. If I store the image, I can easily pull the image without encountering any problems in Quay.io. I have no experience with how role-based access control has helped manage permissions in my organization. I usually measure the effectiveness of Red Hat Quay's extensibility with my existing systems, though I have not used that functionality. Red Hat Quay is not currently deployed on cloud or on-premises in my organization as it is only an institution with no use for cloud on-premises. I use Red Hat Quay only with the free version. I have used documentation for Red Hat Quay, as I have created extensive documentation myself because I am the trainer. I prepare many documents for the students on how to use it, how to manage the registry, and how to manage the images stored in Quay.io. My impression of the documentation that Red Hat provides for Quay is that it is improved; there is no need for further enhancement. The book contents are very structured, and the course name is Specialization in Containers, DO188. It is structured documentation to use the Quay.io account from the beginning to the end of the process. On a scale of 1-10, I rate Red Hat Quay an 8.
I still have experience with Red Hat solutions, specifically with OpenShift and Red Hat Quay. I don't have experience with Red Hat AMQ, Satellite, or API Management, as those are handled by a platform team. My scope is only in the container platform and associated tools. Our experience with Red Hat Quay is measured by repositories rather than users. I don't get involved with licensing for Red Hat Quay as that's handled by a separate accounts team. We have an agreement with Red Hat where we receive everything in a bundle, so individual licensing costs aren't a concern. Based on my experience, I rate Red Hat Quay an 8 out of 10.
I would definitely recommend it. Overall, I would rate this product an eight out of ten.
I would recommend this solution to others who are interested in using it. We are system integrators and we provide support. I would rate Red Hat Quay an eight out of ten.