What the service needs to cover
Check developer backup storage for application data, database dumps, configuration exports, build artifacts that truly need preservation, and restore tests that prove the copy is more than successful upload logs.
Developer backup storage
Backup storage for developers
Keep recovery copies of application data, configuration and other irreplaceable work. Check encryption keys and restore access as part of deployment.
Hosting options
Compare the services for your project.
01
Backup storage
Canadian SFTP storage for your backup software. Check physical separation from your source server before treating a copy as off-site.
See Backup storage →02Ask about your project
Tell us what you need to host and when it needs to be ready.
See Ask about your project →03Domains
Register or transfer a domain and manage DNS. Registration and renewal prices depend on the extension.
See Domains →Your requirements
What does your project need?
Ownership and access
Record the account owner, administrator and recovery contact. Keep passwords and keys in an appropriate secret store, not in this worksheet.
Recovery and retention
For backups, define the data-loss window and retention period. Check physical and account separation from the source, then restore a sample before relying on the copy.
Changes and renewals
Keep current configuration and renewal details. Review the plan when the data, software or people responsible for the service change.
Planning
Access, backups and handover
Confirm the current product specifications and service responsibilities. Record who can approve a change and how to recover the service if it goes wrong.
Free guide
Backup storage for developers: planning checklist
Use the detailed checklist to plan setup, access, migration and recovery with your team.
Download PDF →Help choosing
Tell us about your project.
Send us the software you use, your storage needs and your launch or moving date.
Ask about hosting