Persistent Storage

Each app on a paid project plan gets a persistent storage volume mounted into the container. Files written to this path survive redeploys and container restarts.

This is useful for apps that write to disk — uploaded assets, SQLite databases, generated files, or anything else that needs to persist between deploys.

Where to write files

Any file your app saves to the /data folder will persist across deploys and restarts. Think of it as the one folder on the server that doesn't get wiped when your app updates. Write to /data/uploads, /data/cache, or wherever makes sense for your app — just make sure the path starts with /data.

What to store here

• User-uploaded files (images, documents, attachments)
• SQLite database files
• Generated or cached assets
• Any file your app writes at runtime that needs to survive a restart

What not to store here

Persistent storage is not a substitute for a database. For structured data, use a provisioned PostgreSQL, MySQL, or MongoDB instance instead. Storage is best suited for blobs and files.