Website and applications
List the pages, forms, email accounts and applications included in the project. Note what will stay with another provider.
SaaS VPS Canada
Run your application, workers and database on a self-managed VPS. Choose resources around normal demand and expected growth.
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 application processes, workers, queues, database use, expected traffic and recovery needs.
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
Map the moving parts of your product: web processes, background workers, queues, scheduled jobs, and the database. Measure which one saturates first under load, because SaaS products usually stall on database writes or a backed-up queue while the web tier looks fine. Keep staging on its own server so load tests never compete with paying customers.
Plan recovery before you need it: how much data can you lose, how long can you be down, and who decides to fail over. Backups are a separate service, and database point-in-time recovery needs deliberate setup. Watch queue depth and job failure rates as product metrics, and alert on them the same way you alert on uptime.
Load test until something saturates, then record whether it was CPU, memory, database writes, or queue depth.
Run staging and load tests on a separate server so experiments never slow production for customers.
Monitor queue depth and failed jobs with the same urgency as uptime. Backlogs are silent outages.
Planning
Plan the application, workers, database and backups separately, even when several initially share one VPS.
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.