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.

Gitea Rate Limits is the machine-readable rate-limit profile for Gitea on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 5 rate-limit definitions, across the open-source, enterprise, and cloud tiers, measuring requests_per_minute, gigabytes_per_month, and concurrent_jobs.

The profile also includes 5 backoff/retry policies defined and response codes documented for throttled, quotaExceeded, and serviceUnavailable.

Tagged areas include Git, Source Control, DevOps, CI/CD, and Code Hosting.

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.

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.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/gitea-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.