Quick answer
Docker Hub documents private repositories as 1 private repository. The plan can host public repositories separately from the private-repository count.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| private repositoriesThe plan can host public repositories separately from the private-repository count. | 1 private repository | Personal | DockerAug 22, 2026 |
Why does this limit matter?
A second private image namespace requires a different plan or consolidation strategy.
This value is scoped to Personal; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Review repository visibility and owner plan before automating a new private image.
- Confirm the exact plan, model, runtime, endpoint, region, and account that serve the failing workload.
- Record the observed value, response headers or configuration, timestamp, and source without logging secrets.
Important caveats
- Organization plans and billing can change repository and collaborator capabilities.
- Treat the official source and live account configuration as authoritative if they differ from this verified snapshot.
HyperObserve reports the documented platform constraint. Your application, SDK, gateway, provider, region, or account can impose a lower effective limit.
Related