Public storefront
The generated DotMoose storefront runs separately from the billing system. The public web VM does not need registrar, payment, WHMCS or customer-hosting credentials.
Infrastructure
Separate the jobs. State the limits.
DotMoose uses separate workload boundaries for the public site, billing, standard shared hosting, premium cPanel capacity and backup service. The launch architecture is Canadian, intentionally modest, and is not marketed as multi-datacentre high availability.
Launch location
Canadian infrastructure in Beauharnois, Quebec.
The launch platform is built around a Canadian bare-metal host in OVHcloud's Beauharnois region. Customer-facing product claims must continue to match the infrastructure that is actually deployed and tested.
WHMCS and billing
Client accounts, billing automation, provider integrations and the billing database run on a separate workload from the public static site.
Standard Virtualmin hosting
Standard shared-hosting accounts run in the AlmaLinux/Virtualmin pool with separate service identities and public addresses. A separate cPanel premium node is preserved for demand-triggered cPanel service and is not the default shared-hosting platform.
Backup storage workload
Customer backup storage is isolated in its own restricted SFTP workload and quota namespace. Customer backup storage is not mixed with general shared-hosting accounts.
Storage boundaries
Mirroring improves resilience; it is not an off-site backup.
The launch host uses mirrored fast storage for system/customer workloads and mirrored bulk storage for the backup service. A mirror can tolerate a disk failure, but it does not create a geographically independent copy.
Fast workload storage
The operating platform, storefront, billing and shared-hosting workloads use mirrored NVMe storage with reserved free capacity for maintenance, recovery and migrations.
Bulk backup storage
The backup workload uses mirrored HDD-backed storage with enforced customer quotas. DotMoose must stop new orders before sold quotas can exceed safely usable capacity.
Independent DotMoose control backups
Business-critical configuration and billing data require an independent recovery copy outside the same local storage mirror. The customer backup pool does not satisfy that requirement by itself.
What this does not mean
No invented high-availability story.
One physical launch host is not multi-site HA
A single physical server can be a reasonable starting platform, but it is not fault-tolerant across independent hosts or datacentres. DotMoose does not describe this launch topology as multi-datacentre high availability.
Availability claims need an approved commitment
This page does not create an uptime SLA or guarantee. Any contractual availability commitment must appear explicitly in the applicable service terms and be supported operationally.
Canadian web hosting does not place every provider in Canada
A website can still use payment processors, DNS, analytics, email delivery, CDNs or support systems with their own processing locations. Review the complete service chain when data location is a formal requirement.
Operational proof
Products open only after their complete path works.
A page existing is not enough to make a product launch-ready. Payment, provisioning, login/use, monitoring, backup/recovery and cancellation/refund behavior must be tested for the service before automated sales are enabled.
How orders are handledBenchmarks
Reproduce the VPS measurements.
DotMoose publishes the guest shape, OS, tool versions, exact fio/sysbench settings, node context, network endpoint context and raw JSON for its current VPS 2 and VPS 4 observations. Short synthetic tests are evidence, not a workload guarantee.
Security
See the public security boundaries.
Authentication, secrets, management access and public-service hardening are described separately from infrastructure marketing.