Persistent Storage
Attach persistent NVMe volumes to your services.
By default, container storage is ephemeral — it's lost when the container restarts. For services that need to persist data to disk, SMLL supports attaching persistent NVMe storage volumes.
Adding persistent storage
- When creating or editing a service, enable Persistent Storage
- Set the volume size (1–100 GB)
- The volume is mounted at
/datainside your container
Volume characteristics
| Property | Value |
|---|---|
| Storage type | NVMe SSD |
| Mount path | /data |
| Filesystem | ext4 |
| Min size | 1 GB |
| Max size | 100 GB |
How it works
Persistent volumes are backed by Longhorn, a distributed block storage system. Volumes are replicated across nodes for durability and automatically reattached when a pod is rescheduled.
Resizing volumes
You can increase volume size from the service's Settings tab. Volume expansion happens online without downtime. Shrinking volumes is not supported.
Backups
Persistent volumes can be backed up using volume snapshots. See Volume Snapshots for details.
Pricing
Persistent storage is billed at $0.06/GB per month.
Best practices
- Use persistent storage for data that must survive container restarts
- For temporary files, use the container's ephemeral storage instead
- Take volume snapshots before risky deployments
- Don't store files that belong in object storage (user uploads, media files)