Quotas for Apps
How many apps and scheduled jobs you may have, and how to raise a limit.
| Quota | Description | Default | Trial | Applies to | Adjustable |
|---|---|---|---|---|---|
| Apps | Apps that are not being deleted, per region | 100 | 5 | Region | Yes |
| Scheduled jobs per app | Scheduled jobs of one app, enabled or not | 50 | 10 | Per app | No |
Generated from the quota descriptors: the numbers are the ones the API enforces.
An app that is being deleted no longer counts; a scheduled job counts whether it is enabled or not.
Creating an app, or adding a job, over the limit is refused with 409, code QuotaExceeded, and a
message that starts "Quota exceeded:" and names the limit and the usage.
Raise a quota
An adjustable quota is raised up to its ceiling: open Service quotas in the Deutsche Cloud Console, then choose Request increase on the quota. A quota that is not adjustable cannot be raised. An organization on trial quotas asks support to move it to standard quotas instead. See Service quotas.
Other limits
These are fixed rules of the service, not quotas:
| Limit | Value |
|---|---|
| Machines per app | 1–10 |
| Locations per app | at most 3 |
| Environment variables per app | 1000 |
| Variables a compose service names | 1000 |
| Registry credentials per app | 20 |
| Compose file | 128 KiB |
| Release command timeout | 10–3600 seconds |
| Job timeout | 10–86400 seconds |
| Runs kept per job | the newest 500 |
| Output kept per run | the last 100 lines |
| Repository build | 15 minutes |
| Deployments kept | see Deployments |