Limits
Limits are set in id on plans, teams and projects (People, teams and limits). A
missing value means no limit. Services check before creating anything and report usage every few minutes.
| Key |
Counts |
pages.deploys |
deploys kept |
pages.storage |
bytes of all deploys |
pages.deploy_size |
bytes of one deploy |
apps.apps |
apps, databases included |
apps.memory |
memory limits of running apps |
apps.cpu |
CPU limits of running apps (millicores) |
apps.nodes |
a team's own nodes |
env.sets |
variable sets |
env.vars |
variables across sets |
domains.zones |
DNS zones |
domains.attachments |
attached names |
tunnel.tunnels |
live tunnels |
tunnel.names |
reserved names |
tunnel.bandwidth |
bytes through tunnels per month |
hooks.endpoints |
webhook endpoints |
hooks.storage |
bytes of kept requests |
errors.events |
events per month |
analytics.sites |
sites |
analytics.events |
events per month |
ai.keys |
gateway keys |
ai.tokens |
tokens per month |
share.drops |
drops |
share.storage |
bytes of drops |
config.flags |
flags |
config.configs |
configs |
mail.domains |
mail domains |
mail.mailboxes |
mailboxes |
mail.storage |
bytes of mail |
Per-node quotas (memory, CPU, disk and workloads a team may use on a shared node) are set in apps, not
id, because they belong to one node.
A service that can't reach id keeps the last limits it had; on a fresh start it allows creation and logs
it, so an id outage doesn't stop deploys.