Gitea · Rate Limits

Gitea Rate Limits

Rate limit definitions for the Gitea API surface across the open- source self-hosted distribution, Gitea Enterprise, and Gitea Cloud. The open-source Gitea distribution does not enforce a default per-user API rate limit; operators may configure rate limiting via reverse proxy or app.ini settings. Gitea Cloud applies platform- level fair-use throttles plus an outbound network traffic quota.

5 Limits Throttle: 429 Quota: 429
GitSource ControlDevOpsCI/CDCode HostingOpen SourceSelf HostedRate LimitingQuotasThrottling

Limits

Self-Hosted Default instance
requests_per_minute · minute
-1
Gitea Enterprise Default instance
requests_per_minute · minute
-1
Gitea Cloud Fair Use instance
requests_per_minute · minute
6000
Gitea Cloud Outbound Traffic Quota instance
gigabytes_per_month · month
-1
Gitea Actions Concurrent Jobs (Cloud) instance
concurrent_jobs · realtime
20

Policies

Backoff Strategy
Clients should implement exponential backoff with jitter on 429 and 503 responses, honoring the Retry-After header when present.
Burst Handling
Short bursts above the steady-state limit are tolerated up to the documented burst ceiling before throttling engages.
Webhook Delivery Retries
Gitea's webhook system retries failed deliveries on a backoff schedule; consumers should tolerate at-least-once delivery and verify signatures with the configured secret.
Operator Configurability
For self-hosted deployments, rate limiting is fully under operator control via reverse proxy and app.ini settings. Cloud tenants cannot tune the platform-level limits but may request adjustments via support.
Fair Use
Even on uncapped tiers, sustained usage that materially impacts shared Cloud infrastructure may be subject to fair-use throttling.