Depot Dev Rate Limits
Depot does not publish explicit numeric request-per-second rate limits for its Connect/gRPC API (api.depot.dev). In practice, account usage is governed by plan allotments and overage billing (Docker build minutes, GitHub Actions minutes, Depot CI minutes, and cache storage) rather than hard per-second request caps, with concurrency of in-flight builds bounded by plan and organization configuration. Standard gRPC/Connect error codes are returned on throttling or resource-exhaustion conditions.
Depot Dev Rate Limits is the machine-readable rate-limit profile for Depot on the APIs.io network, in the API Commons Rate Limits shape.
It captures 5 rate-limit definitions, measuring minutes, vcpu_seconds, storage_gb, and concurrent_builds.
An exhausted limit returns HTTP 429.
This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.
The profile also includes 2 backoff/retry policies defined and response codes documented for throttled and grpcResourceExhausted.
Tagged areas include Container Builds, Docker, BuildKit, Remote Cache, and CI/CD.
generated, dated 2026-06-20.
Limits
Policies
Sources
- https://depot.dev/pricing
- https://depot.dev/docs/container-builds/reference/api-overview
- https://depot.dev/docs/github-actions/overview
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.