Wellington, New Zealand
Server infrastructure for Publishing in Wellington
The right server for Publishing is decided by the work it has to do, not by the size of the plan you happen to land on. For a large Publishing business in Wellington that is about 6 Cores, 96 GB of memory and 3000 GB of storage on Dedicated Server.
- ✓ 5 infrastructure tiers
- ✓ Sized for your workload, not a plan name
- ✓ Same price in all 24 locations
Estimated from fibre distance, not measured from Wellington. Your real figure depends on your connection and route, and lands inside this range.
Choose the infrastructure for your workload
Three sizes of business, each sized from an assumed traffic figure rather than a measured one. If you know your own numbers, tell us and the estimate changes with them.
Small Publishing
1–10 people · ~5,000 visits a month
$131.15 USD USD
per month · VPS
- Single Core
- 10 GB RAM
- 250 GB storage
About 0.1 requests a second at peak, holding roughly 7 GB of working data.
Configure this build →Medium Publishing
11–50 people · ~50,000 visits a month
$309.55 USD USD
per month · VDS
- 2 Cores
- 24 GB RAM
- 600 GB storage
- Managed
About 1.5 requests a second at peak, holding roughly 20 GB of working data.
Configure this build →Large Publishing Most likely here
51+ people · ~500,000 visits a month
$1,161.40 USD USD
per month · Dedicated Server
- 6 Cores
- 96 GB RAM
- 3000 GB storage
- Managed
About 14.5 requests a second at peak, holding roughly 80 GB of working data.
Configure this build →These figures are assumptions stated out loud, not predictions about your business. Memory, cores and disk can all be raised on the same server later, usually within the hour, with no rebuild and no new IP address — so starting one size below the estimate is normally the cheaper mistake.
Which tiers suit Publishing
Including the ones that do not, and why — that is usually the more useful half.
| Infrastructure | Verdict | Why |
|---|---|---|
| Shared Hosting Managed space on a shared server | Recommended | A brochure site with light traffic runs comfortably on shared hosting, and the managed platform means no server to look after. |
| VPS Flexible virtual infrastructure with full root access | Recommended | A VPS gives you root, your own PHP and Nginx versions, and room for the site to grow past what shared hosting allows. |
| VDS Virtual server with resources pinned to you alone | Workable | Worth moving to once the site fronts an application rather than pages, or when a slow neighbour has cost you a lead. |
| Dedicated Server An entire physical server, configured to your specification | Workable | More machine than a brochure site needs, but the right answer when it sits alongside other systems on the same box. |
| Bare Metal Physical compute for sustained, demanding workloads | Not this one | Bare metal is sized for sustained heavy compute; a brochure site would leave almost all of it idle. |
Publishing workloads you can host
The archive is the asset, and it must stay searchable long after the issue stopped selling.
- Editorial CMS
- Digital editions
- Subscriber paywall
- Archive & back issues
- Rights management
Where your server runs
All 24 locations cost the same, so pick whichever sits closest to the people who will actually use the server.
Wellington is closest to Sydney. Every marker costs the same per month.
Show all 24 locations and distances from Wellington ▾
| Location | Distance | Est. round trip |
|---|---|---|
| Asia-Pacific · 7 locations | ||
| Sydney, Australia | 1,383 miles | 33–67 ms |
| Singapore | 5,301 miles | 128–256 ms |
| Tokyo, Japan | 5,764 miles | 139–278 ms |
| Hong Kong, China | 5,859 miles | 141–283 ms |
| Kolkata, India | 7,055 miles | 170–341 ms |
| Mumbai, India | 7,685 miles | 186–371 ms |
| Delhi NCR, India | 7,848 miles | 189–379 ms |
| Americas · 9 locations | ||
| Los Angeles, United States | 6,719 miles | 162–324 ms |
| Santa Clara, United States | 6,741 miles | 163–325 ms |
| Seattle, United States | 7,245 miles | 175–350 ms |
| Dallas, United States | 7,591 miles | 183–367 ms |
| Miami, United States | 8,121 miles | 196–392 ms |
| Atlanta, United States | 8,219 miles | 198–397 ms |
| Chicago, United States | 8,357 miles | 202–403 ms |
| Toronto, Canada | 8,785 miles | 212–424 ms |
| New York, United States | 8,950 miles | 216–432 ms |
| Europe, Middle East & Africa · 8 locations | ||
| Tel Aviv, Israel | 10,153 miles | 245–490 ms |
| Stockholm, Sweden | 10,838 miles | 262–523 ms |
| Bucharest, Romania | 10,845 miles | 262–524 ms |
| Frankfurt, Germany | 11,533 miles | 278–557 ms |
| Amsterdam, The Netherlands | 11,536 miles | 278–557 ms |
| Milan, Italy | 11,659 miles | 281–563 ms |
| London, United Kingdom | 11,690 miles | 282–564 ms |
| Madrid, Spain | 12,337 miles | 298–596 ms |
Distances are from Wellington. Round trips are estimated from fibre distance, not measured — the figure your users see depends on where they are.
Publishing in Wellington
We work with businesses across the CBD, Te Aro, Thorndon, Lower Hutt and Karori. Wellington is a compact, review-led market where local relevance and speed matter.
The closest of our 24 data centres to Wellington is Sydney, about 1,383 miles away. Round-trip time is set by physical distance more than by anything else, so the nearest site is usually the right one.
Wellington has a population of about 381,900, which is why the large build above is the one most likely to fit a Publishing business here — though the other two are a click away if it does not. Local time is Pacific/Auckland, so routine maintenance and backups are scheduled against your overnight rather than ours.
Data stays in the jurisdiction you choose, which matters if you are working to the Privacy Act 2020. Pricing is quoted in NZD, and the figure is the same wherever the machine physically sits.
Network reach from Wellington
Estimated from fibre distance rather than measured, and stated as a range. Your own access network decides the rest.
| Data centre | Distance from Wellington | Estimated round trip |
|---|---|---|
| Sydneyapac | 1,383 miles | 33–67 ms |
| Singaporeapac | 5,301 miles | 128–256 ms |
| Tokyoapac | 5,764 miles | 139–278 ms |
every one of our 24 locations costs the same — so the only thing worth optimising is which of them your users are closest to. At the large size assumed above, that is roughly 416,667 requests a day crossing that link.
Publishing hosting in Wellington — FAQs
What size server does a Publishing business in Wellington, Wellington need?
Where would the server for my Wellington, Wellington business actually run?
Is a VPS enough for Publishing, or do we need a dedicated server?
Can you host editorial CMS for us?
Can we start smaller and grow?
Other industries in Wellington
Same city, different workload.
Publishing hosting nearby
The same workload, in the nearest cities.