Quotas
View MarkdownQuotas limit concurrent compute and retained resources across your organization. Use the CLI to see current usage and limits. Owners and Admins can update editable limits through the API, up to the account ceilings returned in the quota response. Read the current quota with:
nodus get quota default -o yamlYour current account tier determines the defaults and which limits you can edit. The quota response includes
hard limits, used amounts and a selfServe map of editable keys to their maximum values. Existing higher
operator-set limits are preserved. Trial payment and compute-access restrictions still apply; increasing a
quota does not reserve hardware or bypass funding and budgets.
| Limit | What counts |
|---|---|
Active instances and Workspaces (workspaces) |
Starting, running, resuming and stopping managed machines across every project. Confirmed-stopped machines do not count. |
GPUs (gpus) |
GPU capacity currently reserved by compute. |
Storage (storageGiB) |
Retained volumes, disks and regional Workspace slots, even after compute stops. |
Members (members) |
Members and pending invites. |
API keys (apiKeys) |
Live keys, including CLI logins and ServiceAccount tokens. |
Stopping an instance frees its active compute slot after cleanup is confirmed. Saved files in retained storage remain available and continue to use storage; an ephemeral home is deleted on stop. Delete retained storage only when you no longer need those files.
Direct-SSH Spot instances have their own Settings › Compute controls for maximum active nodes and maximum simultaneous starts. That page shows both current use and account ceilings. Nodes that are still being cleaned up remain counted until cleanup is confirmed. Available capacity remains a separate launch requirement.
Going over a count quota refuses the create with 429 QuotaExceeded, naming the quota. Nothing already running is
touched. Daily quotas (egressGiBPerDay, assistantUSDPerDay) reset at 00:00 UTC. Expired and revoked API keys
do not count against apiKeys.
Multi-node jobs are in Beta: your org needs the distributed training beta, and gangNodes counts the nodes of
running multi-node jobs. A job that would go over it waits in the queue instead of failing.
To update a limit through the API, use PATCH /apis/nodus.dev/v1/quotas/default with only the keys you are changing,
for example {"hard": {"workspaces": 20}} when that value is within the returned ceiling. Limits cannot be set
below current usage. Members and Viewers can inspect usage but cannot change organization limits. Seat limits
can also be changed on the Members page.
To cap what one project or one person spends, use a Budget.