Edmonton, Canada
Server infrastructure for Publishing in Edmonton
Sizing infrastructure for Publishing starts with the workload, then works back to cores, memory and disk. For a large Publishing business in Edmonton 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 Edmonton. 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.
Edmonton is closest to Seattle. Every marker costs the same per month.
Show all 24 locations and distances from Edmonton ▾
| Location | Distance | Est. round trip |
|---|---|---|
| Americas · 9 locations | ||
| Seattle, United States | 565 miles | 14–27 ms |
| Santa Clara, United States | 1,190 miles | 29–57 ms |
| Los Angeles, United States | 1,367 miles | 33–66 ms |
| Chicago, United States | 1,434 miles | 35–69 ms |
| Dallas, United States | 1,654 miles | 40–80 ms |
| Toronto, Canada | 1,680 miles | 41–81 ms |
| Atlanta, United States | 1,971 miles | 48–95 ms |
| New York, United States | 2,022 miles | 49–98 ms |
| Miami, United States | 2,568 miles | 62–124 ms |
| Europe, Middle East & Africa · 8 locations | ||
| Stockholm, Sweden | 4,187 miles | 101–202 ms |
| London, United Kingdom | 4,223 miles | 102–204 ms |
| Amsterdam, The Netherlands | 4,305 miles | 104–208 ms |
| Frankfurt, Germany | 4,527 miles | 109–219 ms |
| Madrid, Spain | 4,724 miles | 114–228 ms |
| Milan, Italy | 4,809 miles | 116–232 ms |
| Bucharest, Romania | 5,259 miles | 127–254 ms |
| Tel Aviv, Israel | 6,221 miles | 150–300 ms |
| Asia-Pacific · 7 locations | ||
| Tokyo, Japan | 4,891 miles | 118–236 ms |
| Hong Kong, China | 6,475 miles | 156–313 ms |
| Delhi NCR, India | 6,728 miles | 162–325 ms |
| Kolkata, India | 7,018 miles | 169–339 ms |
| Mumbai, India | 7,405 miles | 179–357 ms |
| Singapore | 8,082 miles | 195–390 ms |
| Sydney, Australia | 8,264 miles | 199–399 ms |
Distances are from Edmonton. Round trips are estimated from fibre distance, not measured — the figure your users see depends on where they are.
Publishing in Edmonton
We work with businesses across Downtown, Old Strathcona, Whyte Ave, Oliver and West Edmonton. Edmonton is an entrepreneurial market where local SEO and fast sites win jobs.
The closest of our 24 data centres to Edmonton is Seattle, about 565 miles away. Every kilometre between your users and the server is latency you cannot optimise away in software.
Edmonton has a population of about 1,010,899, 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 America/Edmonton, 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 PIPEDA. Pricing is quoted in CAD, and the figure is the same wherever the machine physically sits.
Network reach from Edmonton
Estimated from fibre distance rather than measured, and stated as a range. Your own access network decides the rest.
| Data centre | Distance from Edmonton | Estimated round trip |
|---|---|---|
| Seattleamericas | 565 miles | 14–27 ms |
| Santa Claraamericas | 1,190 miles | 29–57 ms |
| Los Angelesamericas | 1,367 miles | 33–66 ms |
Edmonton sits in Alberta, and 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 Edmonton — FAQs
What size server does a Publishing business in Edmonton, AB need?
Where would the server for my Edmonton, AB 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 Edmonton
Same city, different workload.
Publishing hosting nearby
The same workload, in the nearest cities.