AI Developer Infrastructure Checklist
Host your API, workers and application data on a server you control. Check model and accelerator requirements before choosing a plan.
Free PDF guides
Download checklists for choosing hosting, moving websites and planning backups. No email address is required.
Download library
No email gate. Download a checklist, use it internally or with a client, and return to the matching live page to confirm current availability before buying.
Host your API, workers and application data on a server you control. Check model and accelerator requirements before choosing a plan.
Choose shared hosting for a website or a VPS for custom software. Keep control of deployment, data and access.
Choose hosting for client websites and agree who owns the domain, pays renewals and maintains each site.
Manage client websites, campaign domains and landing pages with clear access, billing and support responsibilities.
Keep access to hosting, DNS and site files so your team can make technical changes and plan safe migrations.
Organize client domains and websites without taking on server administration unless the project needs it.
Run your application, workers and database with a budget for launch and a plan for growth.
Keep your website, domain and email in accounts your business can access and renew.
Choose hosting around your catalogue, checkout, order volume and recovery needs.
Choose a repeatable hosting setup, then document the differences that matter for each client's site.
Choose shared hosting, VPS or dedicated services for client systems, with clear administration and recovery responsibilities.
Compare Canadian website hosting, servers, domains and storage for the services your business uses.
25 PDFs
Choose a checklist for the project you are planning.
Start with your business website, then add server resources as your product grows. Compare shared hosting and self-managed VPS options.
Run custom client applications on a Canadian VPS. Choose resources for each project and decide who will handle updates and backups.
Host your own tools, demos and client applications with root access. Keep each project's ownership and billing clear.
Install your runtime, run background workers and configure your own services on a self-managed Linux server.
Keep your business website, contact forms and email together. Compare server options for any custom client tools you also need to run.
Host your public website and email in Canada. Review donation services and sensitive records separately from the website.
Registered Canadian charities can apply for our charity-hosting program. Check eligibility and included services before choosing a paid plan.
Choose hosting for your shop's catalogue, checkout and database. Plan for order traffic, payment notifications and recoverable backups.
Show your work on your own domain. Choose space for the website and keep your original project files backed up separately.
Publish galleries and enquiry forms on your own website. Keep original photo archives separate from web-sized images.
Put your services, service area and contact details in one place. Keep enquiry forms and business email working when customers need you.
Host your menu, hours and reservation links on a website your team can update. Plan any booking and ordering integrations before moving.
Host your clinic's public website in Canada. Patient records and appointment systems need their own security and privacy review.
Host your accounting practice's public website in Canada. Keep client documents and financial records in separately secured systems.
Host your firm's public website and contact information in Canada. Confidential case files and client portals need separate security controls.
Publish listings, photos and lead forms on your own website. Check the requirements of your listing feeds and CRM integrations.
Host news, events and membership information. Keep account access and renewals documented as volunteers and committee members change.
Build a website around your work, newsletter and audience. Store large production files and archives outside your website account.
Choose a VPS for the client services you manage. Agree who handles access, patching, monitoring, backups and handover.
Run your application, workers and database on a self-managed VPS. Choose resources around normal demand and expected growth.
Learn Linux administration and deploy your projects with root access. These are self-managed servers, so plan time for updates and backups.
Run your research tools on a Linux server you control. Keep datasets, results and recovery copies separate from disposable experiments.
Move a public-facing service off your home connection or try a new Linux setup. Keep private services and recovery copies separate.
Run build tools, APIs, dashboards and test services on a self-managed VPS. DotMoose does not provide a managed game-server product.
Deploy your API on a Linux server with control over its runtime, ports and background processes. Plan authentication, logging and backups for your application.
25 PDFs
Choose a checklist for the project you are planning.
Plan a WordPress network with enough room for its sites, uploads and database. Check plugin compatibility and administration requirements before ordering.
Choose hosting for product browsing, carts and checkout. Size the database and background jobs for how your store actually runs.
Plan the PHP version, database, queue workers and scheduled jobs your Laravel application needs. Choose a VPS when it needs server-level services.
Run Django with your chosen Python environment, database and application server. A self-managed VPS gives you control over deployment and background tasks.
Deploy your Flask application with its Python dependencies and a production application server. Plan any database, upload storage and background work.
Run your Node.js application as a managed process on your own VPS. Configure environment variables, logs, ports and restarts for production.
A static React build and a server-rendered application need different hosting. Choose around the build output and any backend services your project uses.
Host a static Astro build or choose a VPS for server-rendered pages. Check the adapter and runtime your project needs before deployment.
Compare shared hosting for conventional PHP websites with a VPS for custom services. Check your PHP version, extensions, database and scheduled tasks.
Run your Ruby application with its required version, gems, database and workers. Use a self-managed VPS to control the server configuration.
Deploy your Go service on a Linux VPS. Configure its process, public endpoint, logs and persistent data.
Choose a VPS around your application's JVM, heap and database requirements. Leave room for the operating system and other services.
Plan a Linux-compatible .NET deployment with the runtime, database and background services your application needs. Check platform dependencies before choosing a VPS.
Run your own Docker containers on a Linux VPS. You manage images, updates, networking, volumes and backups; this is not a managed container platform.
Host repositories on a server you control. Plan SSH or HTTPS access, storage growth and backups for repositories and service configuration.
Run build jobs on your own Linux VPS. Choose CPU, memory and disk space for the jobs, and keep build secrets out of untrusted workloads.
Run your monitoring tools on a separate VPS. Plan data retention and alerts, and check whether it shares infrastructure with the systems being monitored.
Configure a private VPN on a Linux server with root access. Plan authentication, routing and firewall rules for the devices that need access.
Run your database on a server you administer. Size memory and storage for your data, then plan access controls, backups and restore testing.
Choose memory for your Redis dataset and operating overhead. Configure private access, eviction behaviour and persistence to suit the application.
Install and maintain your own panel on a Linux VPS. This is a self-managed server, not a DotMoose managed game-hosting service.
Keep your bot running as a service on a Linux VPS. Plan token storage, restarts, logs and any database it uses.
Run scheduled jobs and background workers on your own server. Plan retries, credentials and resource limits for each task.
Run a webhook receiver with a public HTTPS endpoint. Plan request validation, retries, logs and any queued work.
Test deployments in an environment separate from production. Keep staging out of search results and prevent real payments, emails and customer-data writes.
20 PDFs
Choose a checklist for the project you are planning.
Plan the website copy, destination tests and DNS change together. Keep the old service available until the move is checked.
Move applications and data to a Canadian Linux VPS. Review services, firewall rules, public addresses and the downtime your project can tolerate.
Transfer WordPress files and the database, test the new copy, then switch traffic. Plan a final sync for new orders and form submissions.
Check what your cPanel backup contains and what needs separate migration. Plan websites, mail, DNS and any paid software before the move.
Transfer registrar management while keeping your website and email in place. Check transfer eligibility, authorization and nameserver settings first.
Compare a move from HostPapa to DotMoose by inventorying website files, databases, email, DNS, domains and any VPS or WordPress services before changing traffic.
Plan a move from WHC to DotMoose by separating website files, databases, mailboxes, DNS, domains and server-specific settings that need a destination equivalent.
Identify which GoDaddy products currently provide your website, WordPress, email, DNS and domain registration, then plan the parts that actually need to move.
Plan a Bluehost-to-DotMoose move around the website and database copy, mail dependencies, DNS, redirects, SSL and a tested destination before cutover.
Plan a Hostinger-to-DotMoose move across files, databases, email, DNS, scheduled work, certificates and provider-specific settings that may need to be recreated.
Plan a SiteGround-to-DotMoose move across the site, database, email, DNS, caching, cron, TLS and backups, with destination testing before traffic changes.
Map your applications, volumes and managed-service dependencies before moving. A VPS migration may also need separate database and object-storage work.
Inventory your Vultr instance, disks, firewall rules and application data. Plan new network settings and a tested cutover.
Plan the server, storage and application services that need to move. Check DNS, address changes and backup access before cutover.
Review the OVHcloud services your application depends on before moving. A new host still needs an explicit plan for data, networking and access.
Identify the AWS services your application uses, including storage, databases and identity. Check replacements and transfer costs before committing to a move.
Review application runtimes, data, identity and network dependencies. Agree on replacements for Azure-specific services before migration.
Map your compute, storage, database and identity dependencies. Check which components can move directly and which need changes.
Document the software, services and data on your existing server. Test compatibility and recovery before moving a system you depend on.
Review websites, domains, email and servers across your providers. Move them in planned stages and keep ownership and renewals documented.
20 PDFs
Choose a checklist for the project you are planning.
Pay month to month for your website and email. Compare included features, current rates and cancellation terms before ordering.
Choose a self-managed Linux VPS with monthly billing. Compare resources and optional software costs without a multi-year prepayment.
Monthly hosting is available without buying several years upfront. Service terms, billing and cancellation rules still apply.
Choose monthly VPS billing without a long prepaid term. Review resource limits, optional licences and cancellation terms.
Compare your website hosting costs in CAD. Check the billing term, optional extras and taxes shown at checkout.
Choose a Canadian VPS with CAD pricing. Include optional software, extra storage and backups in your budget.
Every standard DotMoose VPS includes one dedicated IPv4 address and IPv6. Check any application-specific networking requirements before ordering.
Standard VPS plans include IPv6 alongside a dedicated IPv4 address. Configure your server, DNS and firewall for the protocols your application uses.
Run your Linux server with an NVMe root disk. Choose a storage size and any extra capacity at checkout.
Compare the full cost of a small VPS, including licences, backups and administration. Start with the resources your project needs.
Compare shared hosting for your website and email. Check regular prices, promotion expiry and renewal terms alongside the features.
Choose a small self-managed server for lightweight applications and development. Allow room for the operating system as well as your software.
Run custom business software with root access. Decide who handles updates, backups and incidents before the application goes live.
Size your server for databases, caches and other memory-heavy applications. Ask for a quote above the published plans; VPS memory uses ballooning.
Choose an NVMe root disk and extra storage at checkout. Contact us when your data needs more space than the listed options.
Choose a Linux server with root access, NVMe storage and public IPv4 and IPv6. You manage the operating system and applications.
Choose AlmaLinux for a self-managed VPS. Check application and control-panel compatibility before selecting your server size.
Deploy your software on an Ubuntu VPS with root access. Plan package updates, service configuration and backups.
Choose Virtualmin GPL as a free control-panel option. You still manage the VPS operating system, security and backups.
Add cPanel & WHM Admin for C$27/month on VPS 4 or larger, for up to five cPanel accounts. The VPS plan is charged separately.
19 PDFs
Choose a checklist for the project you are planning.
Choose storage for your backup software, data growth and retention schedule. Check capacity and recovery requirements before ordering.
Send backup copies to Canadian SFTP storage. Check that the destination is separate from the system and location you need to protect.
Upload and retrieve backup files using compatible SFTP software. You choose the backup schedule, retention and restore checks.
Store copies of your website files and databases. Include email or other data where needed, and test that a restore works.
Keep the data and configuration needed to rebuild your server. Check backup access and restore steps before an outage.
Organize client backup copies with clear access and restore responsibilities. Plan how each client receives their data if the relationship ends.
Keep recovery copies of application data, configuration and other irreplaceable work. Check encryption keys and restore access as part of deployment.
Manage the domain and DNS records behind your website and email. Review nameservers and existing records before making changes.
Search for a domain and compare the registration and renewal price. Eligibility and transfer rules vary by extension.
Check your domain's transfer eligibility and authorization requirements. Keep nameservers stable when you only need to change registrars.
Check the expiry date, renewal price and account contact details. Make sure the domain owner can still access the account before renewal is due.
Host your website and mailboxes together on Standard Virtualmin hosting. This is a shared-hosting plan, not a separate email-only service.
Choose Canadian server resources for your application. Review its runtime, data, external services and management requirements together.
Server location is one part of a privacy plan. Review application access, third-party services and backup locations as well.
Install packages and configure your own Linux services. Root access also makes you responsible for system updates, security and backups.
Every standard VPS includes one dedicated public IPv4 address plus IPv6. Configure your domains and services around that address.
Get help planning the copy, testing and cutover. Confirm the migration scope and ongoing support separately before ordering.
Transfer files and databases, test forms and logins, then change DNS. Keep a way back until the new site is checked.
Move WordPress files and data with a plan for plugins, email and new orders. Test the destination before switching traffic.
Use the product pages for current prices, included services and ordering details. The downloadable guides cover planning and setup.
Tell us what you run today, what is changing, and what you need to control.
Describe the project