Registry Overview

Chainguard Registry hosts more secure container images with two access tiers: public starter images available to everyone, and production images that require authentication for enterprise features like SLAs and version pinning. The registry integrates with standard container tools while providing enhanced security through signed images and comprehensive metadata.

While all public Chainguard Containers are freely available, logging in with a Chainguard account and authenticating when pulling from the registry provides a mechanism for Chainguard to contact you if there are any current or known upcoming issues with images you are pulling.

If you would like to learn more about Chainguard Containers, you can review our documentation, and you can request further information through our inquiry form.

Status

You can check the status of Chainguard’s registry at https://status.cgr.dev.

Network Requirements

Refer to our Network Requirements reference page for details about how to ensure access to Chainguard’s registry in environments using firewalls, access control lists, and proxies.

Using a Caching Proxy with Chainguard’s registry

Chainguard does not offer an SLA for uptime for the Chainguard’s registry. In order to minimize production dependency on the Chainguard’s registry, we recommend that customers use a pull-through proxy for maximum reliability.

We currently provide documentation on how you can set up a pull-through cache for the Chainguard’s registry on the following platforms:

• Google Artifact Registry
• JFrog Artifactory
• Sonatype Nexus
• Cloudsmith