Credits
Credits are how GPU time is rationed. They flow down one level at a time and no level can hand out more than it holds.
| Page | What it covers |
|---|---|
| Allocating | Pools, handing credits down, reclaiming, monthly refills |
| Requests | The request chain, approving and rejecting |
| Settlement report | What was actually consumed, per tenant |
The hierarchy
Solid arrows are money moving; dashed arrows are asking for it. Nobody skips a level: a group administrator cannot mint credits, and a user's session is billed only to their own personal wallet.
| Tier | Who manages it | Can issue? |
|---|---|---|
| System | super_admin | Yes — this is where credits come into existence |
| Organization | org_admin | No; allocates what the system issued |
| Group | group_admin | No; allocates what the organization gave |
| User | the user | Spends only |
What is billed
Only GPU session time: rate × occupancy × runtime, where the rate belongs to the
offering and occupancy is the larger of the VRAM and core
fractions. A session holds credits when it starts, consumes as it runs, and settles
when it ends, refunding the unused part.
CPU sessions, volumes, and queued sessions that never started cost nothing. They are bounded by resource policies instead — if someone is running too much free work, the lever is quota, not credits.
Where to start
- Your pools and the people under them: Allocating.
- Someone is asking for more: Requests.
- "Where did the month go": Settlement report, or the audit log for who changed what.