Skip to main content
Every application you deploy gets a persistent storage directory mounted at /app/data. Its contents survive across deployments and restarts—everything outside it is rebuilt from your code on each deploy, so it is reset every time you push.

​
What to store there

Write anything you need to keep between deployments to /app/data:
  • User uploads (images, documents, avatars)
  • Generated or user-created content
  • SQLite databases or other file-based data
  • Caches you don’t want to lose on each deploy
Anything written elsewhere in the container is temporary and will be gone after the next deployment.

​
How to use it

Point your application at /app/data. For example:
  • Set your upload directory to /app/data/uploads.
  • Use a SQLite path like /app/data/app.db.
  • Managed WordPress already stores uploads, plugins, and themes here automatically.
No setup is required—the directory always exists and is ready to use.

​
Storage size

The amount of persistent storage is determined by your plan. If you need more space, upgrade to a plan with a larger storage allowance.

​
Accessing your files

Every project includes SFTP access to /app/data: browse, upload, and download files from the SFTP file access card on your service page or with any SFTP client—without redeploying.