compare
Quay vs zot
The same facts for both, read from GitHub every night, and the relation a person reviewed.
| Fact | Quay | zot |
|---|---|---|
| Language | Python | Go |
| Licence | Apache-2.0 | Apache-2.0 |
| Stars | 2.8k | 2.8k |
| Latest | v3.17.5 | v2.1.21 |
| Last push | 2026-10-06 | 2026-10-06 |
| Release cadence | about 5 days between releases | about 35 days between releases |
| Active contributors | 32 commit authors on the default branch in the last 90 days | 31 commit authors on the default branch in the last 90 days |
| Flags | none | none |
How they relate
Both replace Docker Hub. Alternatives to Docker Hub →
Full replacementQuayOrganisations, robot accounts, builds and vulnerability scanning with Clair.
PartialzotAn OCI-native registry in a single binary, with a web UI and scanning as extensions.
Quay
- v3.17.52026-10-05[redhat-3.17] NO-ISSUE: fix(ci): pin s390x buildkit to v0.30.0 to avoid runc masking regression
- v3.16.62026-09-30[redhat-3.16] PROJQUAY-12275: chore(deps): upgrade pyasn1 from 0.6.3 to 0.6.4 to address CVE-2026-59885
- v3.14.92026-09-25[redhat-3.14] NO-ISSUE: fix(ci): use larger runner for build-and-publish multi-arch job
- v3.12.222026-09-11[redhat-3.12] NO-ISSUE: fix(ci): pin s390x buildkit to v0.30.0 to avoid runc masking regression
- v3.9.262026-09-09[redhat-3.9] NO-ISSUE: fix(ci): pin s390x buildkit to v0.30.0 to avoid runc masking regression
zot
- v2.1.212026-09-06fix(ci): use latest zot for upgrade tests
- v2.1.202026-08-04chore: bump zui version
- v2.1.192026-08-04fix(api): align blob, manifest, and referrers handling with OCI conformance
- v2.1.182026-06-24chore: fix dependabot alerts
- v2.1.172026-05-18fix(api): return 416 for bad upload range on PUT; fix GET upload Range at size zero
Quay
✓ signed The latest release, v3.17.5, carries a signature GitHub verified.
Loading the security report
zot
✓ signed The latest release, v2.1.21, carries a signature GitHub verified.
Loading the security report