Chainguard Images logo

    Chainguard Images

    Sold by
    Chainguard Images are a collection of minimal, hardened container images that are patched and rebuilt daily, and come with low-to-zero known CVEs, SLSA 2 compliance, signatures, and SBOMs.

    Ratings and reviews

    4.8
    60 ratings
    2 star
    1 star
    87%
    12%
    2%
    0%
    0%
    2 AWS reviews
    |
    58 external reviews
    External reviews are from G2  and PeerSpot .

    Filters

    Review type

    AWS Marketplace reviews
    External reviews
    Reviews (60)
    Keith B.

    Chainguard: Secure, Minimal Images with World-Class Support

    Reviewed on Jun 12, 2026
    Review provided by G2
    What do you like best about the product?
    What stands out most about Chainguard is the combination of technical excellence, operational maturity, and customer obsession that is rarely found in a single platform.

    First and foremost, the breadth and depth of their image catalog is exceptional. Chainguard provides one of the most comprehensive collections of secure, minimal, and production-ready container images available today. The catalog covers a wide range of modern workloads and significantly reduces the operational burden of building, maintaining, and securing custom base images internally.

    Equally impressive is their flexibility. When an image is not already available in the catalog, the Chainguard team demonstrates a willingness to engage directly with customers and evaluate adding new images based on real-world requirements. This level of responsiveness transforms the relationship from that of a traditional vendor into a true engineering partnership.

    From a security and reliability perspective, the quality of the images themselves is outstanding. The images are thoughtfully curated, continuously maintained, and designed with a strong security-first philosophy. They provide a substantial reduction in vulnerability exposure while preserving compatibility and operational simplicity. For organizations focused on supply chain security, compliance, and reducing risk, Chainguard represents a significant advancement over traditional container image strategies.

    The API they offer is also robust and very polished with a ton of features that are much needed from an operational standpoint that are often not present with other vendors. Chainguard has also curated many helpful tools to help with the process as well.

    The customer experience is equally noteworthy. Their onboarding process is among the best I have encountered. The team is highly knowledgeable, responsive, and capable of engaging at both strategic and deeply technical levels. Whether discussing platform architecture, implementation details, or organizational adoption, they consistently demonstrate expertise and a genuine commitment to customer success.

    The user experience deserves special recognition as well. The platform's UI and UX are exceptionally well designed—clean, intuitive, and efficient. Complex security and image management workflows are presented in a way that is approachable without sacrificing depth or functionality. It is clear that significant attention has been invested in making the platform easy to navigate and operationalize at scale.

    Overall, Chainguard has built a platform that excels across the dimensions that matter most to modern platform engineering and SRE organizations: security, reliability, usability, scalability, and customer partnership. Their extensive image ecosystem, willingness to adapt to customer needs, world-class support organization, and polished user experience make them one of the strongest solutions available for securing and managing containerized workloads.
    What do you dislike about the product?
    There are no real downsides to using chainguard that I've experienced.
    What problems is the product solving and how is that benefiting you?
    One of the biggest challenges Chainguard helps us solve is reducing the operational overhead associated with container image security and vulnerability management. Prior to adopting Chainguard, a significant amount of engineering effort was spent tracking, remediating, rebuilding, and validating container images in response to newly disclosed CVEs. While that work is necessary, it is rarely a differentiating activity for an engineering organization and can quickly consume valuable platform engineering resources.

    Chainguard dramatically shortens the time between vulnerability disclosure and remediation. Their ability to rapidly rebuild and publish updated images allows us to address security findings much faster than we could through internal processes alone. As a result, we are able to maintain a significantly lower vulnerability footprint across our containerized workloads while reducing the operational burden on our teams.

    This has been particularly valuable from a compliance and regulatory perspective. As an organization pursuing and maintaining FedRAMP compliance, minimizing CVE counts and demonstrating strong vulnerability management practices is critical. Chainguard has helped us consistently reduce the number of vulnerabilities identified in our environments, making audits, security reviews, and continuous compliance efforts substantially easier to manage.

    Beyond the direct security benefits, Chainguard allows our engineers to focus on higher-value initiatives rather than spending cycles maintaining base images and chasing vulnerability remediation work. The platform effectively shifts a large portion of the container security lifecycle to a team whose core competency is maintaining secure software supply chains, which improves both our security posture and operational efficiency.

    Ultimately, Chainguard is not just helping us reduce CVEs—it is helping us build a more scalable, secure, and sustainable approach to software supply chain security while freeing engineering resources to focus on delivering business value.
    Information Technology and Services

    Simplifies Container Image Vulnerability Management

    Reviewed on Jun 12, 2026
    Review provided by G2
    What do you like best about the product?
    The product meets expectations and easily removes the headache of vulnerabilities in container images with simply migration and product adoption.
    What do you dislike about the product?
    There is a learning curve for developers to understand how to transform their current image but once they understand what is required, it is relatively simple process.
    What problems is the product solving and how is that benefiting you?
    For my current company, container image vulnerabilities but it's having high trust in their build processes and SLAs which enable true speed of remediation.
    Anonymous

    Effortless Vulnerability Reduction with Chainguard

    Reviewed on Jun 11, 2026
    Review provided by G2
    What do you like best about the product?
    Chainguard reduces the total number of vulnerabilities that our team has to spend time patching, both in container images and from open-source libraries. The features that ensure the image dependencies are minimalized and hardened to FIPS and FedRAMP standards are very valuable for us. The initial setup was very easy, allowing us to switch over 50 containers to Chainguard within less than a month.
    What do you dislike about the product?
    It takes the team a while to create a new image for a 3rd party tool, if they do at all.
    What problems is the product solving and how is that benefiting you?
    I use Chainguard to reduce the total number of vulnerabilities in our images and cut down the time my team spends patching vulnerabilities, as well as to meet FedRAMP and FIPS requirements.
    Manufacturing

    Comprehensive Software Supply-Chain Security That Covers Most of Our Needs

    Reviewed on Jun 09, 2026
    Review provided by G2
    What do you like best about the product?
    They have the ability to execute on their mission to secure the entirety of the software supply-chain. I appreciate that they have products that cover most of our needs and are working on more to fill the gaps.
    What do you dislike about the product?
    Attacks on the supply-chain are such a growing problem that it’s not possible for them to move fast enough
    What problems is the product solving and how is that benefiting you?
    Having a trusted source for our open-source allows us to continue to move as fast as the business wants to, not injecting friction into our processes unnecessarily all in the name of "security". The threats that we face from supply-chain compromise seemingly grow into new domains and scope every day with impact that we can't keep up with. Now that Chainguard can help us with libraries, container images, actions, skills and more, we know that we can meet the challenge that we face in securing our supply-chain, reducing churn on security engineers and keeping the business happy.
    Udit Parekh

    Minimal images have reduced vulnerabilities and save significant time in securing containers

    Reviewed on Jun 09, 2026
    Review from a verified AWS customer

    What is our primary use case?

    Chainguard Containers is primarily used for securing containerized applications, reducing vulnerabilities in the software supply chain, and meeting compliance requirements. The SaaS platform is built on Java and React, so Java images are directly pulled from Chainguard Containers, which reduces the vulnerability in that image to attack the application and gives hackers a very small attack surface to the application.

    What is most valuable?

    After switching to Chainguard Containers, it was noticed that if you pull any open-source image, such as Java OpenJDK, you have to do the dependency patching yourself, but Chainguard Containers regularly updates the images with patched dependencies, making it very useful and less vulnerable to hackers.

    The best features of Chainguard Containers are the strong focus on software supply chain security, the provision of minimal container images with a very small attack surface, and the practice of regularly updating images with patched dependencies, which is very useful for a secure application.

    The most impactful features are the minimal container images and the patched dependencies, which reduce manual effort to patch the image every time a vulnerability comes, saving engineers' time, and if there are already patched dependencies, then it is very secure and reduces the vulnerability of the image.

    Chainguard Containers are very positive for the SaaS platform. Before switching, dependencies were regularly patched and open-source tools were used to detect vulnerabilities. Vulnerabilities in the base image would be found and fixed. However, after switching to Chainguard Containers, it has significantly impacted the effort and time required. Now, the latest image of whatever language is used for building the application is pulled directly from Chainguard Containers, resulting in a very secure and compliant image.

    Specific outcomes and metrics show that before this, every month there would be 15 to 20 vulnerabilities, but after switching to Chainguard Containers, there are now only one or maybe two vulnerabilities. Time is saved by 60 to 70% because previously it was necessary to first find the vulnerabilities in the base image, then find the patched version and manually patch that version in the base image, which took a lot of effort from engineers. The improvement is very good, and 70% of the time on securing the base image has been reduced.

    Chainguard Containers are the best in minimal container images, and they regularly update their images, making it very easy to integrate with existing container platforms. They have a strong focus on software supply chain security.

    What needs improvement?

    The biggest challenge in Chainguard Containers is that they provide minimal images, which can make troubleshooting difficult because common debugging tools are also not included. More documentation and troubleshooting guidance for teams transitioning from traditional container images would be helpful.

    Chainguard Containers would receive a 10 out of 10 rating, with the only improvement needed being documentation for minimal images. In minimal images, not all commands are working, making troubleshooting for teams a struggle. More documentation for troubleshooting applications in minimal images would be very helpful.

    For how long have I used the solution?

    Chainguard Containers has been used for about eight to nine months in production and development environments.

    How are customer service and support?

    The features are very great, and the support is also very good, so there is no need for improvements in this area.

    What other advice do I have?

    If you are struggling with vulnerabilities and compliance management and looking for a secure base image solution, Chainguard Containers can be used, which has a catalog of thousands of images, so whatever you are building, you can directly pull images from Chainguard Containers, and it will be very helpful for you. I would rate this product 10 out of 10.

    Which deployment model are you using for this solution?

    Public Cloud

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Computer Software

    Resolving CVEs in Minutes with a Vast Catalog of Certified Package Checks

    Reviewed on Jun 08, 2026
    Review provided by G2
    What do you like best about the product?
    Since we work with a lot of classified data, being able to resolve CVEs in minutes through your vast catalog of certified package version checks has saved our developers time. It lets us focus on what really matters: the end product, rather than compliance.
    What do you dislike about the product?
    I’m working on onboarding all of our packages to use Chainguard services, and I’m realizing that there are some packages you don’t currently provide. Because of that, finding a workaround is taking some time.
    What problems is the product solving and how is that benefiting you?
    Cve remediations, it allows me to spend less time struggling with finding solutions and more time reaching out to customers and resolving their feedback
    ParthasarathyT

    Secures container builds, has simplified compliance audits and reduced vulnerabilities dramatically

    Reviewed on Jun 08, 2026
    Review provided by PeerSpot

    What is our primary use case?

    My main use case for Chainguard Containers is for every container deployment as a best practice, and it has been applied at the compliance level. The use case is specifically for compliance checks and best practices.

    A quick, specific example of how I use Chainguard Containers for compliance checks or best practices in my workflow is that it replaces our normal Docker images with secure, low-CVE images in production. Traditional images like Docker Alpine have many vulnerabilities, while Chainguard Containers does not have them. It is minimal, with near to zero CVEs. Teams can use it for API, backend services, and microservices in Kubernetes. The matter here is that it drastically reduces the CVEs, and no manual patching or effort is needed. The practical use case is where it is in Kubernetes, specifically where GKE workloads use Chainguard Containers for Cloud Run and all the popular services.

    What is most valuable?

    The benefit of Chainguard Containers is that it makes development simpler. It makes the development team confident there will not be any bugs or vulnerabilities in the image they are using. It is mainly needed for vulnerabilities, SLAs, security audits, and SOC 2, ISO, and PCI compliance. The image includes SBOM, signature, and provenance metadata, which makes audits much easier.

    The best features Chainguard Containers offers include a reduced image size. It removes the shell and the package manager, resulting in a significantly smaller image size compared with a normal image. We can deploy production workloads directly without worrying about security concerns. If we want a strong supply chain for security, we will be using it. Many users are already tired of scanning alerts, so this will be a great thing.

    Removing the shell and package manager has positively impacted my team's workflow and deployment speed by making it quite user-friendly, where the developer can touch it without any hesitation. Chainguard Containers are built and pushed from non-patched binaries, with the packages compiled directly from the source. No dependencies or pre-built distro packages like Debian or Alpine are required, so there are no hidden vulnerabilities. The developer gains full control over what goes inside, and the image size is smaller with fewer vulnerabilities, in fact, zero. It has built-in processes like SBOM, which is Software Bill of Material generated. The image is cryptographically signed, and provenance is tracked, leading to faster patching, minimal footprint, and best supply chain control.

    Chainguard Containers has positively impacted my organization by reducing constant CVE fixing, resolving security versus DevOps conflicts, and minimizing compliance headaches. After implementing secured-by-default containers, there is less effort on fixing vulnerabilities, faster delivery, and better compliance. The impact on security teams includes a lower risk of attack, less panic during audits, and significantly fewer security noises.

    A specific outcome we have noted since implementing Chainguard Containers is that for a client who uses more than 200 containers, they previously received vulnerability warnings for every deployment. Once we implemented Chainguard Containers, the vulnerability ratio drastically decreased, from 100 to 30. Nearly 70% of the vulnerability checks have passed. Chainguard Containers are CVE-resistant, which is significant as CVEs represent Common Vulnerabilities and Exposures.

    What needs improvement?

    Regarding improvements for Chainguard Containers, during build time, it is fine, but at runtime, there should be something reported. It is not a runtime-friendly solution, and if a service is running, vulnerability attacks can still occur, which it does not prevent.

    Many potential improvements are needed, such as integrating AI to detect vulnerabilities. They can manage it in a way that vulnerabilities are resisted during runtime.

    What do I think about the stability of the solution?

    Chainguard Containers is stable.

    What do I think about the scalability of the solution?

    Its scalability allows us to push between 1,000 to 2,000 images, completely dependent on our subscription.

    How are customer service and support?

    We have not tried Chainguard Containers' customer support, so we have not encountered any errors to report.

    Which solution did I use previously and why did I switch?

    Before using Chainguard Containers, we did use Sonar and Trivy, but wanted to move beyond that due to hosting and scanning each in the pipeline, which has too many bugs and can corrupt our images. To avoid this, we planned to adopt Chainguard Containers.

    What was our ROI?

    I am uncertain about the return on investment with Chainguard Containers. I have heard it costs nearly $13,000 per year. When factoring in the setup of tools like Sonar scanning and Trivy, which costs over $6,000 to $7,000, investing an additional $5,000 for Chainguard Containers provides good support and granular checks on each image, so I do not see it as wasteful; rather, it is a good investment for our startup.

    What's my experience with pricing, setup cost, and licensing?

    My experience with pricing, setup cost, and licensing is that while I work on implementation and do not manage billing, it is open source and developer-friendly. Although I am not the right person to speak on pricing, the free trial is excellent for up to five container images per organization for production use, without SLA guarantees. This is good for POC, learning, and small workloads. For enterprise, you pay based on the number and type of images, including CVE, SLA patch timelines, full image versioning, and support. Costs depend on those factors, and the most used firms often engage in catalog subscriptions to access the entire catalog. Licensing for images generally falls between 1,000 to 2,000 images, with unlimited pulls and pull standardization.

    Which other solutions did I evaluate?

    I did not evaluate other options before choosing Chainguard Containers.

    What other advice do I have?

    Regarding Chainguard Containers' AI capabilities, my thoughts on its governance and security are that not much is in place, as we have to use other tools to catch vulnerabilities during runtime. Although it has AI, it does not effectively catch all the vulnerabilities.

    The accuracy and reliability of the output from Chainguard Containers are below average, but I still give it an average rating of 6.5 to 7 because of its capabilities and its functionality for a developer-friendly approach.

    My advice for others looking into using Chainguard Containers is that as a firm working for an insurance company, everything we deploy and provision matters. If you want security at a granular level, Chainguard Containers is a great option. I would rate Chainguard Containers an 8 out of 10 because it is a simple tool, but it can still be enhanced in the future. Even though it is great, there are some lags. We are confident that there will not be any issues during build time, but in runtime, there are some hacks that cannot be tracked, changed, or prevented. If Chainguard Containers can address those runtime issues, that would be great. My overall review rating for Chainguard Containers is 10.

    reviewer2014131

    Pre-hardened container images have reduced vulnerabilities and improve our security posture

    Reviewed on May 31, 2026
    Review provided by PeerSpot

    What is our primary use case?

    Chainguard Containers was a tool brought into my enterprise as a proof of concept that we evaluated, but we have not rolled it out for enterprise usage.

    Our main use case for Chainguard Containers during the evaluation period was for hardened images, as we do not have a central source of hardened images for all use cases in the enterprise. Chainguard was a solution that proposed we could use their offering as a source of pre-hardened or pre-vetted images.

    During our evaluation, we were trying to use Chainguard Containers for hardened images such as various types including Debian, UBI, Dynatrace, Nginx, and other similar images. We were attempting to see what Chainguard offers and then run a scan on them with their tools to see how hardened they are in terms of vulnerabilities.

    What is most valuable?

    Based on my evaluation, the best features Chainguard Containers offers are pre-hardened images. They are now adding pre-hardened libraries as well, but the pre-hardened base operating systems are what we were looking for, and Chainguard offers this and does a pretty good job except for the fact that many of their images are Alpine-based, which are not that friendly with Kubernetes native environments.

    I find the quality and security of those pre-hardened images compared to what we were using before to be absolutely solid, as they are minimal images, small in size, and clean.

    Chainguard Containers has positively impacted my organization even during the proof of concept phase by improving our security posture. Some of our groups ended up using Chainguard base operating systems for their container images, and that led to improved security posture and fewer vulnerabilities. There was a reduction in vulnerabilities for the teams that were using Chainguard.

    What needs improvement?

    The only limitation or challenge that stood out during my evaluation of Chainguard Containers was the fact that it is primarily based on Alpine, which can be tricky to use in native Kubernetes environments, as we use Tecton primarily, which is a CI/CD pipeline that runs on native Kubernetes.

    What other advice do I have?

    I am not familiar with Chainguard Containers' AI capabilities.

    Regarding the governance and security of those AI features, I was not and am not familiar with the AI features of Chainguard Containers.

    I did not have any experience with the accuracy and reliability of output of Chainguard Containers' AI capabilities.

    Chainguard Containers is primarily based on Alpine, and most of their images follow this pattern.

    I would rate this review an eight overall.

    Moshika S.

    Great Product Innovation Backed by Outstanding Customer Service

    Reviewed on Mar 17, 2026
    Review provided by G2
    What do you like best about the product?
    Great Customer service, our account manager is so on top of things! Great product and continued innovation
    What do you dislike about the product?
    .Net availability for Chainguard libraries isn’t available yet and not sure if it’s on the roadmap.
    What problems is the product solving and how is that benefiting you?
    Low resource needs for CVE resolution
    Financial Services

    Seamless CI/CD Integration and Transparent SBOMs with Chainguard Libraries

    Reviewed on Mar 17, 2026
    Review provided by G2
    What do you like best about the product?
    The seamless integration with our existing CI/CD pipeline, along with Chainguard’s transparency through SBOM and the overall Chainguard Libraries experience.
    What do you dislike about the product?
    I antipate Chainguard's capability to audit which JS Libraries appear from Chainguard vs NPM even after they're drawn through JFrog/Arctifactory.
    What problems is the product solving and how is that benefiting you?
    Transparency and risk mitigation.