Website and applications
List the pages, forms, email accounts and applications included in the project. Note what will stay with another provider.
Developer VPS Canada
Install your runtime, run background workers and configure your own services on a self-managed Linux server.
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 runtime versions, installed packages, open ports, queues and background workers.
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
Write down every runtime your projects need, with exact versions: language, database, cache, and any system packages your builds depend on. Note which services listen on public ports and which should stay bound to localhost. A short inventory like this prevents the common failure where a deploy works locally and breaks on a differently configured server.
Run queues and background workers under a process supervisor so they restart after a crash or a reboot. Keep application secrets in environment files with tight permissions, never in the repository. DotMoose VPS plans are self-managed with administrator access, which means package updates, firewall rules, and service configuration stay in your hands.
Record exact language, database, and package versions per project so a rebuild matches production.
Use a process supervisor for queues and workers so jobs restart cleanly after crashes and reboots.
List every open port and its purpose. Databases and admin panels should not face the public internet.
Planning
Choose around the packages, processes, ports and workers the application needs. A developer portfolio and a running application do not need the same setup.
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.