Canadian WordPress hosting that does not mean North American.
Most providers answer a Canadian residency question with a US datacentre and the word continent. For a lot of Canadian organisations that answer is the reason they cannot sign.
In Canada, not near it.
The distinction that matters here is one letter of geography and a great deal of procurement.
Data that stays inside the border
Public sector, health and education buyers in Canada frequently cannot use storage that sits in the United States, however close it is. The origin and its backups stay in Canada.
Routing that does not detour south
Canadian traffic has historically been routed through US exchanges even when both ends are domestic. Delivery is arranged so a domestic request is served domestically.
French and English served as equals
A bilingual site is two full versions, not a translated menu. Both are cached separately and declared to search engines properly, so neither is treated as a copy of the other.
Quebec's rules taken seriously
Law 25 goes further than the federal baseline on consent and on what has to happen when data leaves the province. We will tell you where things sit rather than describing a network.
Backups under the same rule
There is no point pinning the site to Canada and letting the backups replicate elsewhere. Both stay in the same place.
Procurement asks a specific question.
Not is it fast, and not is it secure. Is the data in Canada - and a Canadian buyer has usually been told no by three suppliers before they ask a fourth.
- Origin and backups inside Canada
- Domestic traffic kept on domestic paths
- French and English cached and declared separately
- Storage location stated, not implied
Toronto to Toronto, not via Chicago.
A Canadian visitor reaching a Canadian site should not leave the country on the way. When they do, the extra distance shows up on every request the cache cannot answer.
What we change for Canadian sites
Two threads run through all of it: the border is not a formality, and half the country reads in French.
| Setting | What we do | Why |
|---|---|---|
| Origin country | Canada specifically, not North America | Public sector, health and education buyers routinely cannot accept storage in the United States, and continent-level answers are what disqualify a supplier at the first question. |
| Backup replication | Constrained to the same country as the origin | Pinning the live site and letting its copies replicate across the border defeats the requirement while appearing to satisfy it. |
| Traffic routing | Domestic requests kept on domestic paths | Canadian traffic has long been routed through US exchanges even when both endpoints are in Canada, which adds distance and a jurisdiction nobody asked for. |
| Bilingual caching | French and English cached as separate entries with language declared | A bilingual site is two complete versions, and serving one from the other's cache entry is how a translated site gets treated as duplicate content. |
| Location disclosure | Written statement of where data sits | Quebec's Law 25 asks specific questions about data leaving the province, and an answer that describes a network rather than a place is not one procurement can file. |
Simple, transparent pricing.
Every plan includes free migration, daily backups, SSL and 24/7 support.
- 1 WordPress site
- 10 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Support tickets
- 5 WordPress sites
- 50 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Priority support tickets
- 20 WordPress sites
- 200 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Dedicated support
Questions, answered.
Is my data actually in Canada, or just in North America?
Does that include backups?
How are French and English versions handled?
Can you help with Law 25 questions?
Give procurement the answer it wants.
Move the site to a Canadian origin - migration is free, backups included.