Workspace storage
Every Aidin workspace includes persistent storage. Notebook home directories (/home/jovyan) live on a managed persistent volume, so code, datasets, and checkpoints survive notebook restarts.
Verified storage behavior
Section titled “Verified storage behavior”| Behavior | Status |
|---|---|
| Volume attaches and mounts at notebook start | Verified (2026-11-10) |
| File I/O through the mounted volume | Verified |
| Files preserved byte-identically across stop → start | Verified (live canary test) |
| Volumes survive notebook deletion (kept in your workspace) | Verified |
| Storage releases and reattaches cleanly as notebooks stop/start | Verified |
Storage budgets and quotas
Section titled “Storage budgets and quotas”Each project namespace carries a storage budget alongside its compute quota. When the platform’s per-project storage quotas for public tenants are finalized (they are being aligned with the public capacity model), the exact per-plan numbers will be documented on Storage and quotas. Until then, no specific storage number is published here.
Good practice
Section titled “Good practice”- Keep large, regenerable datasets outside
/home/jovyanwhen possible and load them on demand. - Use pipelines and the model registry for repeatable artifacts rather than notebook-local files alone.
- Keep a requirements file (or similar) on your volume so a recreated notebook can be re-provisioned quickly — custom images are not currently available (see Notebook environments and packages).
- Before deleting a notebook, confirm anything you need is on the volume — deleted notebooks keep their volumes, but there is no undelete for notebook sessions themselves.