shc quota
manage resource quotas and limits
Reference for the quota CLI group. Source: modules/quota/commands/.
Subcommands
Section titled “Subcommands”| Subcommand | Description |
|---|---|
scan | scan and report resource usage |
set | set resource quotas |
status | show quota status |
unset | remove resource quotas |
shc quota scan
Section titled “shc quota scan”scan and report resource usage
No declared flags. The global -t, -e and -s name the tenant,
environment or deployment to measure. Every node measures the
deployments it holds.
Source: modules/quota/commands/
shc quota set
Section titled “shc quota set”set resource quotas
| Flag | Type | Required | Help |
|---|---|---|---|
--scope | str | yes | base, tenant, environment or deployment |
--cpu | str | no | cpu limit |
--memory / -m | str | no | memory limit |
--disk / -d | str | no | disk limit |
--max-deployments | int | no | maximum number of deployments |
--max-environments / --max-envs | cast(type[str], int) | no | maximum number of environments |
--max-apps | cast(type[str], int) | no | maximum number of apps |
--max-vdeployments | cast(type[str], int) | no | maximum number of vdeployments |
Source: modules/quota/commands/
shc quota status
Section titled “shc quota status”show quota status
No declared flags.
The text table carries a BASIS column saying what each USED cell is:
| Basis | Axes | What the figure is |
|---|---|---|
reserved | cpu, memory | The deploy-time reservation this scope is charged. Written by charge() from the compose reservations. Not live load: it does not fall when a deployment goes idle. |
measured / unmeasured | disk | A figure the daemon sampled, or the word unmeasured where no sweep has measured it. |
counted | deployments, environments, apps, vdeployments | An exact count of objects. |
Measured on bitspur compose01, 2026-09-09: shc quota status -t corp -s mailcow -e prod reported 8.1 cores and 10.8 GB, while docker stats over the
same 14 containers showed 1.30% of one core and ~273 MiB. Both figures
are correct; they answer different questions. For live per-container CPU
and RSS, use docker stats on the node.
Source: modules/quota/commands/
shc quota unset
Section titled “shc quota unset”remove resource quotas
| Flag | Type | Required | Help |
|---|---|---|---|
--scope | str | yes | base, tenant, environment or deployment |
--cpu | bool | no | remove CPU limit |
--memory / -m | bool | no | remove memory limit |
--disk / -d | bool | no | remove disk limit |
--max-deployments | bool | no | remove max deployments limit |
--max-environments / --max-envs | bool | no | remove max environments limit |
--max-apps | bool | no | remove max apps limit |
--max-vdeployments | bool | no | remove max vdeployments limit |
--all / -a | bool | no | remove all quota limits |
Source: modules/quota/commands/