Home / Storage
Quay.io public repositories (Red Hat)
quay.ioRegistrystorage/quay-io-public-repositoriesJSONcomparereport an errorprovider JSON
- Free allowance
- "We offer unlimited storage and serving of public repositories" — Red Hat's own support article.
- Verdict
- ★ qualifiesusable as stated; the read path was probed
- Cost
- free tier
- Identity
- anonymous?placeholder, not evidence; card unknown, phone unknown
- Binding limit
- noneno named constraint binds
- Evidence
- reported4 sources; a third party said so
- Freshness
- stale on 2026-11-05checked 2026-10-21 (inherited); stale on 2026-11-05
| Free tier | "We offer unlimited storage and serving of public repositories" — Red Hat's own support article. Every paid plan is priced only by private-repo count and lists 'Unlimited public repos'; a free account gets unlimited public repos, private repos require a 30-day trial then a paid plan. unit unlimited; metered on stored-bytes |
|---|
| Price | none stated |
|---|
| Identity | anonymous (inferred, not read) not published |
|---|
| Egress | Included in 'unlimited storage and serving of public repositories' — no per-GB line item exists for public repos on any plan. Served over quay.io's own CDN edge. |
|---|
| Per-object cap | not stated |
|---|
| Retention | Every paid plan is priced only by private-repo count and lists 'Unlimited public repos'; a free account gets unlimited public repos, private repos require a 30-day trial then a paid plan (30 days) |
|---|
| Interface | oci oci |
|---|
| Tooling | oras push / docker push / skopeo; Cosign/notation signing supported natively. |
|---|
| Composes with | N public repos x N free Red Hat accounts. Repos are namespaced per user/org, so one account already gives effectively unbounded blob count; orgs are free to create. |
|---|
| Reliability | Hosted multitenancy means a noisy-neighbour throttle is possible but not documented; no data-expiry policy on public repos, so blobs persist indefinitely. |
|---|
| Parsed numbers | |
|---|
Evidence 4
Unknown values 3
- per object cap notes: the field may be stated in a source that was not read
- per object cap stated: the field may be stated in a source that was not read
- retention notes: the field may be stated in a source that was not read