Australian WordPress hosting for a market far from every server.
Australia is a long way from the rest of the internet and a long way from itself. Both distances show up on every request a cache cannot answer.
Distance twice over.
There is the distance to the rest of the world, and the distance between Perth and Sydney. Both are real and they are addressed differently.
Cached pages answered locally
Static and full-page cache is served from the nearest edge, which is what stops a page load being a trip across an ocean for content that never changes.
The origin still decides the rest
Checkout, admin and signed-in pages cannot be cached, so their speed depends on where the origin sits. That placement is a decision rather than an accident.
Privacy Act questions answered as facts
Australian organisations must know where personal information is held and whether it leaves the country. We answer with a location, not with a network diagram.
A market with three time zones and one peak
Australian traffic concentrates in the eastern evening, so capacity is planned around that window rather than a flat average.
Backups you can point at
A backup is another copy of the same information, and it needs an answer as specific as the live site does.
Caching solves half of it.
Edge delivery makes marketing pages fast anywhere. The half it cannot touch is everything behind a login, and that is where Australian sites feel their location.
- Cached content served from the nearest edge
- Origin placement chosen deliberately, not defaulted
- Storage location stated for Privacy Act purposes
- Capacity planned around the eastern evening peak
The logged-in page is the honest one.
Any Australian site looks fine on a cached homepage. Load a dashboard and the distance to the origin is the entire measurement.
What we change for Australian sites
Two distances and one privacy question, and the configuration follows each of them separately.
| Setting | What we do | Why |
|---|---|---|
| Edge coverage | Cached content answered from the nearest point of presence | Australia's distance from the rest of the internet is unavoidable, so the aim is to stop most requests having to travel it at all. |
| Origin placement | Chosen deliberately and disclosed | Signed-in and transactional pages always reach the origin, so its location is the difference between a fast dashboard and a slow one for every Australian user. |
| Storage disclosure | Location given for both site and backups | Australian privacy obligations require knowing whether personal information leaves the country, and that has to be answered with a place. |
| Peak planning | Sized for the eastern evening rather than a daily mean | Most of the population sits in two eastern time zones, so national traffic peaks in one window rather than spreading across the day. |
| Domestic routing | Kept as short as the network allows | The distance between Perth and Sydney is comparable to crossing Europe, so intra-Australian latency is a real number rather than a rounding error. |
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.
Do I need an Australian server?
Does data leave Australia?
Why does my site feel fast until customers log in?
How should I plan capacity for an Australian audience?
Close the distance that can be closed.
Move the site across. Migration is free, placement discussed first.