Quay
projectquay.io
- Free plan
- Linux
- Web
- API
- Self-hosted
What Quay is
Project Quay is an open source registry for building, organizing, distributing and deploying container images and OCI artifacts. It provides a web interface, private repositories and controls over who can view or change content. Teams can run it as a standalone component or an Operator on OpenShift Container Platform, and Kubernetes deployments are supported. Clair scans images for known vulnerabilities and can suggest remediation. Quay also supports repository mirroring, multi-region replication with client failover and disconnected deployments. CI/CD and Git-compatible integrations, including GitHub, GitLab and Bitbucket, can automate builds and deployments; an OAuth 2 REST API supports registry management and automation. Security capabilities include TLS, isolated builds, role-based access for teams and organizations, and encryption of sensitive fields at rest and at runtime. The open source community distribution is free under an Apache 2 license. A deployment requires image storage, a database and Redis. Local image storage is intended only for proof-of-concept or test installations because blob durability is not guaranteed.
Who it suits
Project Quay suits teams managing container images or OCI artifacts across development and production workloads, from small deployments to enterprise environments. It requires infrastructure for image storage, a database and Redis.
Good to know, and what to watch
- Clair scans images for known vulnerabilities.
- Supports mirroring and multi-region replication with client failover.
- Can run in disconnected environments.
- Includes an OAuth 2 REST API.
- Deployments require image storage, a database and Redis.
- Local image storage is intended only for tests or proof-of-concept.
- FIPS options require environment- and version-specific prerequisites.
Plans
Every plan and priceProject Quay (open source community distribution)
Free plan · 30-day trial
The verdict
Project Quay combines registry management with scanning, access controls and distribution options. Plan the required storage and services before deployment, and do not rely on local image storage for durable production data.
What the maker publishes
- API
- Project Quay provides an OAuth 2 REST API for managing the registry and automating tasks. source
- Build automation
- It integrates with CI/CD tools and Git-compatible systems, including GitHub, GitLab, and Bitbucket, for automated builds and deployments. source
- Compliance
- FIPS-compliant cryptographic functions can be enabled with prerequisites that vary by deployment environment and version. source
- Deployments
- It can run as a standalone component or as an Operator on OpenShift Container Platform, and supports Kubernetes deployments. source
- Distribution
- It supports repository mirroring, geographic replication with client failover, and deployment in disconnected environments. source
- Intended users
- Project Quay supports small-scale and enterprise deployments, including development and production workloads. source
- Notable limit
- Local image storage is intended only for proof-of-concept or test installations because blob durability is not guaranteed. source
- Purpose
- Project Quay is an open source container image registry for building, organizing, distributing, and deploying containers and OCI artifacts. source
- Security controls
- Security capabilities include TLS, isolated builds, organization and team role-based access, and encryption of sensitive fields at rest and at runtime. source
- Storage and infrastructure
- A deployment requires image storage, a database, and Redis; supported storage options include AWS S3, Google Cloud Storage, and Azure Blob Storage. source
- Support
- The overview states that Red Hat provides 24/7 support for Project Quay. source
- Vulnerability scanning
- Clair scans container images for known vulnerabilities and can suggest remediation. source
- Web interface and access
- It provides a web interface, private repositories, and controls for managing who can view or change content. source
Checked against the maker's pages on 30 Sept 2026.