Quotas
View MarkdownQuotas keep one mistake from running away with your credits. See yours with:
nodus get quota default -o yaml| Quota | Default before your first purchase | After a purchase |
|---|---|---|
members (seats, including pending invites) |
10 | 10 |
apiKeys (live keys, including CLI logins and ServiceAccount tokens) |
50 | 200 |
liveSandboxes (stopped ones count until their delete completes) |
10 | 100 |
storageGiB |
50 | 1024 |
egressGiBPerDay |
20 | 100 |
nodusNodes |
1 | 10 |
gangNodes (multi-node jobs) |
0 | 8 |
inferenceRPM / inferenceTPM |
60 / 100,000 | 600 / 1,000,000 |
assistantUSDPerDay |
$1 | $10 |
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.
Owners and Admins of an org that has bought credits set their own seats, up to 1,000, under Team ›
Members › Change, or with PATCH /apis/nodus.dev/v1/quotas/default and {"hard": {"members": 25}}. Seats never go
below the members and pending invites you have. To raise any other org limit, or seats past 1,000, contact support.
To cap what one project or one person spends, use a Budget.