Website and applications
List the pages, forms, email accounts and applications included in the project. Note what will stay with another provider.
Canadian game developer
Run build tools, APIs, dashboards and test services on a self-managed VPS. DotMoose does not provide a managed game-server product.
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 build tools, APIs, dashboards, updates and test applications that you administer.
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
Separate your workloads by job: build agents, a test server for playtesters, backend APIs, and a dashboard for live builds. Each has a different load pattern, and a compile job should never starve the API your testers are playing against. List the tools in your pipeline, from version control to crash reporting, and note which ones need public endpoints.
Keep player-facing test servers patched and restartable, with player data treated as disposable unless you are testing persistence on purpose. Publish build updates through your normal pipeline and record which build each server runs. DotMoose VPS plans are self-managed with administrator access, so server configuration, ports for your game protocol, and update timing stay under your control.
Run compiles on their own server so build spikes never slow the APIs testers are playing on.
Record which build each test server runs, and note it in every bug report from playtesters.
Open only the ports your game protocol and dashboard need, and document each one.
Planning
This is infrastructure for your own applications and development tools, not a managed game-server offering.
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.