Storage and quotas
Every project namespace carries quotas: ceilings on CPU, memory, storage, and GPU usage that bound the whole project. Quotas protect you from runaway workloads and protect the platform from noisy neighbors.
What is quota’d
Section titled “What is quota’d”| Dimension | Bounds |
|---|---|
| CPU / memory | Total across your project’s running workloads |
| Storage | Total size of your project’s workspace volumes (storage budget) |
| GPU | Total GPU allocation, with an additional fair-share cap on GPU usage |
| Concurrency | Bounded provisioning protects the platform during signup spikes |
How quotas behave
Section titled “How quotas behave”- Workloads requesting more than the quota allows are not admitted until headroom exists (for example after stopping another workload). They do not error at creation; they wait.
- A notebook that is stopped consumes no compute quota, only storage.
- Storage counts against your budget even for stopped and deleted-notebook volumes (see the retention note in Workspace storage).
Requesting changes
Section titled “Requesting changes”Quota changes are entitlement changes: they are made by Aidin through your plan or an enterprise agreement, via the support channel provided with your account. There is no self-service quota editing — by design, so quota state stays authoritative.