Backups and Data Persistence for Small Apps
A hosting instance is not a backup. Keep independent copies of source code and important data, and know how to restore them. The consolex1 Free plan does not include automated backups or a database.
1. Separate code from runtime data
Store source code and configuration templates in a version-controlled repository. Keep secrets out of that repository and identify which files or database records are user data that must be backed up separately.
2. Keep copies outside the server
A copy on the same hosting instance will not help if the instance is lost. Store backups in a separate system you control and restrict access to sensitive data.
3. Choose a schedule and retention period
Back up data often enough to meet your recovery needs, and retain more than one recent copy when practical. The right schedule depends on how frequently data changes and how much loss is acceptable.
4. Test recovery
Periodically restore a copy into a test location and verify that the application can read it. A backup that has never been restored is an untested assumption.
5. Plan for the Free plan limits
The Free plan does not include a database or automated backups. Do not treat temporary files on the instance as durable storage; use an independent data store only if your project and service terms support it.