Website and applications
List the pages, forms, email accounts and applications included in the project. Note what will stay with another provider.
Canadian research VPS
Run your research tools on a Linux server you control. Keep datasets, results and recovery copies separate from disposable experiments.
Hosting options
Self-managed virtual servers with administrator access, NVMe disks, shared vCPU, dedicated IPv4 and IPv6. RAM uses ballooning. Backups are sold separately.
See VPS hosting →02Canadian SFTP storage for your backup software. Check physical separation from your source server before treating a copy as off-site.
See Backup storage →03Register or transfer a domain and manage DNS. Registration and renewal prices depend on the extension.
See Domains →04Tell us what you need to host and when it needs to be ready.
See Ask about your project →Your requirements
List the pages, forms, email accounts and applications included in the project. Note what will stay with another provider.
Check software versions, compute needs, durable datasets, results and separate backup copies.
Record who owns the domain and hosting account, pays renewals and approves changes. Use individual logins where supported, and keep recovery access available to the owner.
List the files, databases and mailboxes that need a backup. Agree who checks restores and who hands over access when a staff member or supplier leaves.
Field guide
Research computing fails quietly when versions drift: a library update changes a result and nobody can say when. Record the operating system, language runtimes, and package versions for each project, and freeze them once analysis starts. Note which datasets are irreplaceable, such as field recordings or survey responses, and which can be regenerated from sources.
Size compute for the real workload: a parsing job that runs overnight needs memory and patience, while model fitting may need every core you can give it. Store results with the code and the data version that produced them. Backups are a separate service, and irreplaceable datasets deserve copies in a second location, checked on a schedule.
Record and freeze runtimes and packages once analysis begins, so results stay reproducible months later.
Mark which datasets are irreplaceable and which can be regenerated. Protect the first group hardest.
Hold backup copies of irreplaceable data in a separate location and verify them on a schedule.
Planning
Keep durable datasets, results and notebooks backed up separately from environments that can be rebuilt.
Use the detailed checklist to plan setup, access, migration and recovery with your team.
Download PDF →Send us the software you use, your storage needs and your launch or moving date.
Ask about hostingYour current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.