What the service needs to cover
Check choosing a VPS specifically because root access is required for packages, ports, services, firewall rules, runtimes, mounts, or system configuration that shared hosting cannot expose safely.
Root access VPS
Install packages and configure your own Linux services. Root access also makes you responsible for system updates, security and backups.
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
Check choosing a VPS specifically because root access is required for packages, ports, services, firewall rules, runtimes, mounts, or system configuration that shared hosting cannot expose safely.
Record the account owner, administrator and recovery contact. Keep passwords and keys in an appropriate secret store, not in this worksheet.
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.
Keep current configuration and renewal details. Review the plan when the data, software or people responsible for the service change.
Field guide
Root access gives full control of the server: install packages, open ports, run custom services, set firewall rules, and change system configuration. Shared hosting cannot expose those controls safely across many accounts. Choose a VPS when the work itself needs that level of system access.
Control carries the maintenance with it. The owner applies system updates, watches logs, manages the firewall, and fixes what breaks at the operating system level. Plan the hours for that work before ordering, because an unpatched server with open services becomes a problem on a schedule.
Disable password login for root and use SSH keys. Add a named user with sudo for daily work and keep root login for recovery.
Set a weekly window for system updates and reboot when kernel updates require it. Record what changed so a bad update can be traced.
Start with all ports closed and open only what each service needs. Review the open list monthly against the services actually running.
Planning
Confirm the current product specifications and service responsibilities. Record who can approve a change and how to recover the service if it goes wrong.
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.