Perth, Australia
Server infrastructure for Ride-Hailing in Perth
What Ride-Hailing actually need from a server is predictable performance under load, and enough headroom to grow into. For a large Ride-Hailing business in Perth that is about 16 Cores, 196 GB of memory and 800 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 Perth. 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 Ride-Hailing
1–10 people · ~5,000 visits a month
$247.45 USD USD
per month · VDS
- 2 Cores
- 24 GB RAM
- 100 GB storage
About 0.4 requests a second at peak, holding roughly 14 GB of working data.
Configure this build →Medium Ride-Hailing
11–50 people · ~50,000 visits a month
$425.65 USD USD
per month · VDS
- 4 Cores
- 48 GB RAM
- 200 GB storage
- Managed
About 4.1 requests a second at peak, holding roughly 40 GB of working data.
Configure this build →Large Ride-Hailing Most likely here
51+ people · ~500,000 visits a month
$1,708.15 USD USD
per month · Dedicated Server
- 16 Cores
- 196 GB RAM
- 800 GB storage
- Managed
About 40.5 requests a second at peak, holding roughly 160 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 Ride-Hailing size up this way
Working from about 500,000 visits a month and roughly 500,000 requests a day, peaks run about 7× the average hour, so the build is sized for the busiest moment rather than the typical one; about 160 GB of data needs to stay in memory to keep queries fast; and each request costs real computation rather than a cache lookup, so cores matter more here than on a typical site.
- 40.5 req/sec at peak
- 160 GB working set
- 20 GB/month growth
- Linux
Which tiers suit Ride-Hailing
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 | Persistent connections and custom ports are exactly what a shared platform does not permit. |
| VPS Flexible virtual infrastructure with full root access | Workable | Enough for a small server or a test instance, though a noisy neighbour shows up immediately as jitter. |
| VDS Virtual server with resources pinned to you alone | Recommended | Pinned cores are what keep tick rate and call quality steady; on a contended instance they are not. |
| Dedicated Server An entire physical server, configured to your specification | Recommended | Single-tenant hardware removes the last source of variance, which is what these workloads are judged on. |
| Bare Metal Physical compute for sustained, demanding workloads | Workable | For operators running many instances at once on hardware they control. |
Ride-Hailing workloads you can host
Matching and live location are continuous real-time work whose cost scales with active drivers, not page views.
- Driver-rider matching
- Live location streaming
- Surge pricing
- Trip payments
- Rating system
Where your server runs
All 24 locations cost the same, so pick whichever sits closest to the people who will actually use the server.
Perth is closest to Sydney. Every marker costs the same per month.
Show all 24 locations and distances from Perth ▾
| Location | Distance | Est. round trip |
|---|---|---|
| Asia-Pacific · 7 locations | ||
| Sydney, Australia | 2,045 miles | 49–99 ms |
| Singapore | 2,432 miles | 59–117 ms |
| Hong Kong, China | 3,751 miles | 91–181 ms |
| Kolkata, India | 4,183 miles | 101–202 ms |
| Mumbai, India | 4,530 miles | 109–219 ms |
| Delhi NCR, India | 4,884 miles | 118–236 ms |
| Tokyo, Japan | 4,920 miles | 119–238 ms |
| Europe, Middle East & Africa · 8 locations | ||
| Tel Aviv, Israel | 6,893 miles | 166–333 ms |
| Bucharest, Romania | 7,710 miles | 186–372 ms |
| Stockholm, Sweden | 8,355 miles | 202–403 ms |
| Milan, Italy | 8,514 miles | 206–411 ms |
| Frankfurt, Germany | 8,604 miles | 208–415 ms |
| Amsterdam, The Netherlands | 8,788 miles | 212–424 ms |
| London, United Kingdom | 8,997 miles | 217–434 ms |
| Madrid, Spain | 9,082 miles | 219–438 ms |
| Americas · 9 locations | ||
| Santa Clara, United States | 9,180 miles | 222–443 ms |
| Seattle, United States | 9,246 miles | 223–446 ms |
| Los Angeles, United States | 9,335 miles | 225–451 ms |
| Dallas, United States | 10,538 miles | 254–509 ms |
| Chicago, United States | 10,976 miles | 265–530 ms |
| Atlanta, United States | 11,257 miles | 272–543 ms |
| Toronto, Canada | 11,280 miles | 272–545 ms |
| Miami, United States | 11,377 miles | 275–549 ms |
| New York, United States | 11,621 miles | 281–561 ms |
Distances are from Perth. Round trips are estimated from fibre distance, not measured — the figure your users see depends on where they are.
Ride-Hailing in Perth
We work with businesses across the CBD, Fremantle, Northbridge, Subiaco and Joondalup. Perth is a spread-out market where clear service areas and Google Business listings win jobs.
The closest of our 24 data centres to Perth is Sydney, about 2,045 miles away. Every kilometre between your users and the server is latency you cannot optimise away in software.
Perth has a population of about 2,384,371, which is why the large build above is the one most likely to fit a Ride-Hailing business here — though the other two are a click away if it does not. Local time is Australia/Perth, 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 1988. Pricing is quoted in AUD, and the figure is the same wherever the machine physically sits.
Network reach from Perth
Estimated from fibre distance rather than measured, and stated as a range. Your own access network decides the rest.
| Data centre | Distance from Perth | Estimated round trip |
|---|---|---|
| Sydneyapac | 2,045 miles | 49–99 ms |
| Singaporeapac | 2,432 miles | 59–117 ms |
| Hong Kongapac | 3,751 miles | 91–181 ms |
Perth sits in Western Australia, 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 500,000 requests a day crossing that link.
Ride-Hailing hosting in Perth — FAQs
What size server does a Ride-Hailing business in Perth, WA need?
Where would the server for my Perth, WA business actually run?
Is a VPS enough for Ride-Hailing, or do we need a dedicated server?
Can you host driver-rider matching for us?
Can we start smaller and grow?
Other industries in Perth
Same city, different workload.
Ride-Hailing hosting nearby
The same workload, in the nearest cities.