Derby, United Kingdom
Server infrastructure for Headless CMS in Derby
What Headless CMS actually need from a server is predictable performance under load, and enough headroom to grow into. For a large Headless CMS business in Derby that is about Single Core, 6 GB of memory and 50 GB of storage on VPS.
- ✓ 5 infrastructure tiers
- ✓ Sized for your workload, not a plan name
- ✓ Same price in all 24 locations
Estimated from fibre distance, not measured from Derby. 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 Headless CMS
1–10 people · ~5,000 visits a month
On request
Shared Hosting
- Single Core
- 3 GB RAM
- 30 GB storage
About 0.2 requests a second at peak, holding roughly 0.2 GB of working data.
Configure this build →Medium Headless CMS
11–50 people · ~50,000 visits a month
On request
Shared Hosting
- Single Core
- 3 GB RAM
- 30 GB storage
- Managed
The same build as small — at 2.4 requests a second this workload still fits comfortably, so there is nothing to gain by paying for more.
Configure this build →Large Headless CMS Most likely here
51+ people · ~500,000 visits a month
$78.50 USD USD
per month · VPS
- Single Core
- 6 GB RAM
- 50 GB storage
- Managed
About 24.1 requests a second at peak, holding roughly 2 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.
Why Headless CMS size up this way
Working from about 500,000 visits a month and roughly 416,667 requests a day, peaks run about 5× the average hour, so the build is sized for the busiest moment rather than the typical one.
- 24.1 req/sec at peak
- 2 GB working set
- 2 GB/month growth
- Linux
Which tiers suit Headless CMS
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. |
Headless CMS workloads you can host
Rebuilds are the spike: an editor saves a page and the whole site regenerates.
- Content API
- Build & deploy hooks
- Media transforms
- Preview environments
- CDN invalidation
Where your server runs
All 24 locations cost the same, so pick whichever sits closest to the people who will actually use the server.
Derby is closest to London. Every marker costs the same per month.
Show all 24 locations and distances from Derby ▾
| Location | Distance | Est. round trip |
|---|---|---|
| Europe, Middle East & Africa · 8 locations | ||
| London, United Kingdom | 113 miles | 3–5 ms |
| Amsterdam, The Netherlands | 270 miles | 7–13 ms |
| Frankfurt, Germany | 477 miles | 12–23 ms |
| Milan, Italy | 704 miles | 17–34 ms |
| Stockholm, Sweden | 868 miles | 21–42 ms |
| Madrid, Spain | 870 miles | 21–42 ms |
| Bucharest, Romania | 1,377 miles | 33–66 ms |
| Tel Aviv, Israel | 2,302 miles | 56–111 ms |
| Americas · 9 locations | ||
| New York, United States | 3,378 miles | 82–163 ms |
| Toronto, Canada | 3,458 miles | 83–167 ms |
| Chicago, United States | 3,852 miles | 93–186 ms |
| Atlanta, United States | 4,122 miles | 100–199 ms |
| Miami, United States | 4,357 miles | 105–210 ms |
| Dallas, United States | 4,654 miles | 112–225 ms |
| Seattle, United States | 4,672 miles | 113–226 ms |
| Santa Clara, United States | 5,255 miles | 127–254 ms |
| Los Angeles, United States | 5,333 miles | 129–257 ms |
| Asia-Pacific · 7 locations | ||
| Delhi NCR, India | 4,221 miles | 102–204 ms |
| Mumbai, India | 4,527 miles | 109–219 ms |
| Kolkata, India | 4,980 miles | 120–240 ms |
| Tokyo, Japan | 5,885 miles | 142–284 ms |
| Hong Kong, China | 5,974 miles | 144–288 ms |
| Singapore | 6,775 miles | 164–327 ms |
| Sydney, Australia | 10,557 miles | 255–510 ms |
Distances are from Derby. Round trips are estimated from fibre distance, not measured — the figure your users see depends on where they are.
Headless CMS in Derby
The closest of our 24 data centres to Derby is London, about 113 miles away. Round-trip time is set by physical distance more than by anything else, so the nearest site is usually the right one.
Derby has a population of about 270,468, which is why the large build above is the one most likely to fit a Headless CMS business here — though the other two are a click away if it does not. Local time is Europe/London, 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 UK GDPR and the Data Protection Act 2018. Pricing is quoted in GBP, and the figure is the same wherever the machine physically sits.
Network reach from Derby
Estimated from fibre distance rather than measured, and stated as a range. Your own access network decides the rest.
| Data centre | Distance from Derby | Estimated round trip |
|---|---|---|
| Londonemea | 113 miles | 3–5 ms |
| Amsterdamemea | 270 miles | 7–13 ms |
| Frankfurtemea | 477 miles | 12–23 ms |
Derby sits in England, 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.
Headless CMS hosting in Derby — FAQs
What size server does a Headless CMS business in Derby, England need?
Where would the server for my Derby, England business actually run?
Is a VPS enough for Headless CMS, or do we need a dedicated server?
Can you host content API for us?
Can we start smaller and grow?
Other industries in Derby
Same city, different workload.
Headless CMS hosting nearby
The same workload, in the nearest cities.