Drone Ci Rate Limits
Drone is self-hosted; the open-source server does not enforce a managed rate quota. Operational limits are configured via DRONE_* environment variables (queue length, concurrent runners, log buffer size) and by the capacity of the host. The upstream Git provider (GitHub/GitLab/Bitbucket/ Gitea) imposes its own rate limits on Drone's webhook/SCM client.
Drone Ci Rate Limits is the machine-readable rate-limit profile for Drone on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 3 rate-limit definitions, measuring concurrent_jobs, bytes, and requests.
The profile also includes 2 backoff/retry policies defined.
Tagged areas include DevOps, CI/CD, Container-Native, Open Source, and YAML.
Limits
Policies
Sources
- https://docs.drone.io/server/reference/
- https://docs.drone.io/runner/overview/
- https://github.com/harness/drone
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for rate limits
4 MCP tools reach this
find_rate_limitsBrowse and filter every rate limit in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/drone-ci-rate-limits"curl "https://apis.io/api/v1/rate-limits?limit=25"Discovery needs no key. Ratings and market analysis are Pro.