Jfrog Container Registry Rate Limits
JFrog does not publish per-plan API request quotas or rate limits for the JFrog Platform. Subscription tiers are metered on consumption (GB), not on requests. The one documented throttling control is a CONCURRENCY cap on search/AQL requests, configurable by the operator on self-managed instances.
Jfrog Container Registry Rate Limits is the machine-readable rate-limit profile for JFrog Container Registry on the APIs.io network, in the API Commons Rate Limits shape.
It captures 1 rate-limit definition, measuring concurrent_requests.
Limit state is signalled in the published and note response headers, and an exhausted limit returns HTTP 429.
The profile also includes 1 backoff/retry policy defined and response codes documented for throttled.
Tagged areas include Container Images, Containers, Docker, Helm, and JFrog.
publishednote
Limits
Policies
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.