Git quotas

How many repositories, deploy keys, webhooks and access tokens your organization may have, and how to raise a limit.

Last updated 18 November 2026View as Markdown
QuotaDescriptionDefaultTrialApplies toAdjustable
RepositoriesGit repositories in the organization, imported ones and wikis included1.00050OrganizationYes
Deploy keys per repositoryDeploy keys added to one repository5010Per repositoryYes
Webhooks per repositoryWebhooks configured on one repository, active or not205Per repositoryYes
Access tokensPersonal Git HTTPS access tokens in the organization that have not expired50050OrganizationYes

Generated from the quota descriptors: the numbers are the ones the API enforces.

Repositories count imported repositories and the {name}.wiki repositories an import adds. Deploy keys and webhooks are counted per repository; access tokens count only those that have not expired. All four are enforced hard: a create over the limit is refused.

Other fixed limits, which cannot be raised: a single git push carries at most 2 GiB; a release holds up to 100 files of up to 2 GiB each; a SARIF upload is at most 12 MB; anonymous requests to a public repository are limited to a burst of 30, then one per second, per address.

Raise a quota

You need permission for quotas:RequestServiceQuotaIncrease. On a standard (not trial) account, a request for up to twice the standard default of one of these four quotas is usually approved at once; anything else is decided by Deutsche Cloud staff. Replace Monorepo split with what you need the higher limit for (at least 10 characters).

  1. Open Service quotas.
  2. On the quota's row, open the actions menu and choose Request increase.
  3. For New value, enter the limit you need.
  4. For What you need it for, enter Monorepo split.
  5. Choose Send request. The request appears under Increase requests.

See Quotas for how requests are decided.

Did this page help you?