Persistent storage volumes
Persistent Storage
By default, a service's filesystem is ephemeral — data written inside the container is lost when the pod restarts or redeploys. Persistent Storage attaches a Kubernetes PersistentVolumeClaim to your service so data survives restarts and redeploys. Use it for file uploads, SQLite databases, caches, or any workload that writes data it needs to keep.
Attaching a disk
Open the service settings and enable Persistent Storage under the Infrastructure section. Choose a size between 1 GB and 10 GB and set a mount path. The volume is created and attached on the next deploy.
Mount paths
The mount path is the directory inside the container where the volume is mounted. It must be an absolute path (starts with /), cannot be the root path /, must not contain path traversal sequences (../), and cannot target reserved system directories. Maximum length is 255 characters. A common choice is /app/data.
Detach vs. delete
When you remove a disk from a service you are asked whether to detach or delete. Detach unmounts the volume from the service but keeps the data — you can reattach it later. Delete permanently destroys the volume and all data it contains. This action cannot be undone.
Volume status
After enabling storage the volume goes through these states: pending (creation queued), provisioning (being allocated), available (ready to attach), attached (mounted to the service). If provisioning fails the status shows failed and a retry button is shown in the service detail view.
Constraints
Persistent Storage is not available for Static Website or Cron Job service types. It is also incompatible with replica regions — because a volume binds to a single region, enabling storage disables the replica region selector. To use replicas, remove the disk first. The deployment region is likewise fixed for as long as a disk is attached, since the underlying volume lives in that region; to move the service to a different region, delete the disk first — a detached volume stays in its original region and can only be reattached there. Disks can be resized larger at any time but never smaller: making one smaller means deleting it and creating a new, smaller disk, which loses its data.