Website and applications
List the pages, forms, email accounts and applications included in the project. Note what will stay with another provider.
Canadian API hosting
Deploy your API on a Linux server with control over its runtime, ports and background processes. Plan authentication, logging and backups for your application.
Hosting options
Shared hosting for websites, email and PHP applications, with Virtualmin included.
See Web hosting →02Help moving websites, databases and email. We agree on the scope and cutover details before the move.
See Migration help →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 process supervision, TLS, authentication, logging, firewall rules and dependent services.
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
An API is a promise to other software, so treat uptime, versioning, and error behaviour as the product. Run the process under a supervisor that restarts it after crashes, terminate TLS properly, and require authentication on every endpoint that touches data. List your dependent services, such as databases, caches, and third party APIs, and know which failures each one causes.
Log requests with status codes and latency, and review the logs for repeated authentication failures and slow endpoints. Keep the database and cache off the public network, reachable only from the API server itself. DotMoose VPS plans are self-managed with administrator access, which puts firewall rules, TLS renewal, and process configuration in your hands.
Run the API under a supervisor with automatic restarts, and alert when restarts repeat.
Require keys or tokens on data endpoints, and log failed attempts so abuse shows up early.
Databases and caches listen only on private interfaces, reachable from the API server alone.
Planning
Plan process supervision, TLS, logging, authentication and rate limits for the API. Check how dependent services behave during an outage.
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.