Oldham, United Kingdom
Server infrastructure for Banks in Oldham
The right server for Banks is decided by the work it has to do, not by the size of the plan you happen to land on. For a medium Banks business in Oldham that is about 8 Cores, 128 GB of memory and 450 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 Oldham. 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 Banks
1–10 people · ~5,000 visits a month
$425.65 USD USD
per month · VDS
- 4 Cores
- 48 GB RAM
- 200 GB storage
- Managed
About 0.6 requests a second at peak, holding roughly 33.6 GB of working data.
Configure this build →Medium Banks Most likely here
11–50 people · ~50,000 visits a month
$1,066.90 USD USD
per month · Dedicated Server
- 8 Cores
- 128 GB RAM
- 450 GB storage
- Managed
About 5.7 requests a second at peak, holding roughly 96 GB of working data.
Configure this build →Large Banks
51+ people · ~500,000 visits a month
$3,793.90 USD USD
per month · Bare Metal
- 28 Cores
- 448 GB RAM
- 2000 GB storage
- Managed
About 56.7 requests a second at peak, holding roughly 384 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 Banks size up this way
Working from about 50,000 visits a month and roughly 140,000 requests a day, about 96 GB of data needs to stay in memory to keep queries fast.
- 5.7 req/sec at peak
- 96 GB working set
- 8 GB/month growth
- Linux
Which tiers suit Banks
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 | Not this one | Shared hosting gives you no control over where data sits or who else is on the machine, which regulated records cannot accept. |
| VPS Flexible virtual infrastructure with full root access | Workable | Workable for a small practice, with the caveat that you own the patching and audit trail unless you add management. |
| VDS Virtual server with resources pinned to you alone | Recommended | Isolated, pinned resources in a data centre you choose, which is usually what a data-residency obligation actually requires. |
| Dedicated Server An entire physical server, configured to your specification | Recommended | A single-tenant physical machine is the clearest answer to "who else can reach this data" — nobody. |
| Bare Metal Physical compute for sustained, demanding workloads | Workable | For larger estates running several regulated systems on hardware you control end to end. |
Banks workloads you can host
The ledger has to balance and be provably durable, so this is the workload least tolerant of a lost write.
- Core banking ledger
- Online & mobile banking
- Payment rails
- AML & fraud screening
- Statement generation
- Regulatory reporting
Where your server runs
All 24 locations cost the same, so pick whichever sits closest to the people who will actually use the server.
Oldham is closest to London. Every marker costs the same per month.
Show all 24 locations and distances from Oldham ▾
| Location | Distance | Est. round trip |
|---|---|---|
| Europe, Middle East & Africa · 8 locations | ||
| London, United Kingdom | 163 miles | 4–8 ms |
| Amsterdam, The Netherlands | 303 miles | 7–15 ms |
| Frankfurt, Germany | 518 miles | 12–25 ms |
| Milan, Italy | 752 miles | 18–36 ms |
| Stockholm, Sweden | 864 miles | 21–42 ms |
| Madrid, Spain | 910 miles | 22–44 ms |
| Bucharest, Romania | 1,413 miles | 34–68 ms |
| Tel Aviv, Israel | 2,343 miles | 57–113 ms |
| Americas · 9 locations | ||
| New York, United States | 3,340 miles | 81–161 ms |
| Toronto, Canada | 3,417 miles | 82–165 ms |
| Chicago, United States | 3,810 miles | 92–184 ms |
| Atlanta, United States | 4,085 miles | 99–197 ms |
| Miami, United States | 4,325 miles | 104–209 ms |
| Dallas, United States | 4,612 miles | 111–223 ms |
| Seattle, United States | 4,622 miles | 112–223 ms |
| Santa Clara, United States | 5,206 miles | 126–251 ms |
| Los Angeles, United States | 5,285 miles | 128–255 ms |
| Asia-Pacific · 7 locations | ||
| Delhi NCR, India | 4,240 miles | 102–205 ms |
| Mumbai, India | 4,554 miles | 110–220 ms |
| Kolkata, India | 4,995 miles | 121–241 ms |
| Tokyo, Japan | 5,862 miles | 142–283 ms |
| Hong Kong, China | 5,973 miles | 144–288 ms |
| Singapore | 6,791 miles | 164–328 ms |
| Sydney, Australia | 10,555 miles | 255–510 ms |
Distances are from Oldham. Round trips are estimated from fibre distance, not measured — the figure your users see depends on where they are.
Banks in Oldham
The closest of our 24 data centres to Oldham is London, about 163 miles away. The price is the same in all 24 locations, so distance is the only variable worth optimising.
Oldham has a population of about 237,110, which is why the medium build above is the one most likely to fit a Banks 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 Oldham
Estimated from fibre distance rather than measured, and stated as a range. Your own access network decides the rest.
| Data centre | Distance from Oldham | Estimated round trip |
|---|---|---|
| Londonemea | 163 miles | 4–8 ms |
| Amsterdamemea | 303 miles | 7–15 ms |
| Frankfurtemea | 518 miles | 12–25 ms |
Oldham 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 medium size assumed above, that is roughly 140,000 requests a day crossing that link.
Banks hosting in Oldham — FAQs
What size server does a Banks business in Oldham, England need?
Where would the server for my Oldham, England business actually run?
Is a VPS enough for Banks, or do we need a dedicated server?
Can you host core banking ledger for us?
Can we start smaller and grow?
Other industries in Oldham
Same city, different workload.
Banks hosting nearby
The same workload, in the nearest cities.