Utah, United States
Server infrastructure for Farms in Utah
Sizing infrastructure for Farms starts with the workload, then works back to cores, memory and disk. For a medium Farms business in Utah that is about 2 Cores, 24 GB of memory and 250 GB of storage on VDS.
- ✓ 5 infrastructure tiers
- ✓ Sized for your workload, not a plan name
- ✓ Same price in all 24 locations
Estimated from fibre distance, not measured from Utah. 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 Farms
1–10 people · ~5,000 visits a month
$116.30 USD USD
per month · VPS
- Single Core
- 10 GB RAM
- 100 GB storage
About 1.5 requests a second at peak, holding roughly 5.6 GB of working data.
Configure this build →Medium Farms Most likely here
11–50 people · ~50,000 visits a month
$262.30 USD USD
per month · VDS
- 2 Cores
- 24 GB RAM
- 250 GB storage
- Managed
About 14.8 requests a second at peak, holding roughly 16 GB of working data.
Configure this build →Large Farms
51+ people · ~500,000 visits a month
$992.65 USD USD
per month · Dedicated Server
- 12 Cores
- 96 GB RAM
- 800 GB storage
- Managed
About 148.2 requests a second at peak, holding roughly 64 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 Farms size up this way
Working from about 50,000 visits a month and roughly 213,333 requests a day, peaks run about 6× the average hour, so the build is sized for the busiest moment rather than the typical one.
- 14.8 req/sec at peak
- 16 GB working set
- 12 GB/month growth
- Linux
Which tiers suit Farms
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 | An ERP or practice-management system needs a database tuned to its own workload, which a shared platform will not allow. |
| VPS Flexible virtual infrastructure with full root access | Workable | Enough for a small team, though the working set of a records system tends to outgrow a modest instance quickly. |
| VDS Virtual server with resources pinned to you alone | Recommended | Guaranteed memory is what keeps the database in cache, which is the single biggest factor in how fast these systems feel. |
| Dedicated Server An entire physical server, configured to your specification | Recommended | The usual answer: a records system rewards a large, uncontended memory pool and consistent disk latency. |
| Bare Metal Physical compute for sustained, demanding workloads | Workable | For large deployments, or where the database and application tiers are virtualized onto one physical host. |
Farms workloads you can host
Harvest concentrates the year's data into a few weeks, and spray records are a legal obligation.
- Field records & cropping plans
- Machinery telemetry
- Yield mapping
- Input & spray records
- Compliance returns
Where your server runs
All 24 locations cost the same, so pick whichever sits closest to the people who will actually use the server.
Utah is closest to Los Angeles. Every marker costs the same per month.
Show all 24 locations and distances from Utah ▾
| Location | Distance | Est. round trip |
|---|---|---|
| Americas · 9 locations | ||
| Los Angeles, United States | 558 miles | 13–27 ms |
| Santa Clara, United States | 575 miles | 14–28 ms |
| Seattle, United States | 711 miles | 17–34 ms |
| Dallas, United States | 994 miles | 24–48 ms |
| Chicago, United States | 1,268 miles | 31–61 ms |
| Atlanta, United States | 1,584 miles | 38–76 ms |
| Toronto, Canada | 1,678 miles | 41–81 ms |
| New York, United States | 1,979 miles | 48–96 ms |
| Miami, United States | 2,086 miles | 50–101 ms |
| Europe, Middle East & Africa · 8 locations | ||
| London, United Kingdom | 4,882 miles | 118–236 ms |
| Stockholm, Sweden | 4,979 miles | 120–240 ms |
| Amsterdam, The Netherlands | 4,998 miles | 121–241 ms |
| Frankfurt, Germany | 5,224 miles | 126–252 ms |
| Madrid, Spain | 5,265 miles | 127–254 ms |
| Milan, Italy | 5,479 miles | 132–265 ms |
| Bucharest, Romania | 6,023 miles | 145–291 ms |
| Tel Aviv, Israel | 6,995 miles | 169–338 ms |
| Asia-Pacific · 7 locations | ||
| Tokyo, Japan | 5,486 miles | 132–265 ms |
| Hong Kong, China | 7,182 miles | 173–347 ms |
| Delhi NCR, India | 7,633 miles | 184–369 ms |
| Kolkata, India | 7,890 miles | 190–381 ms |
| Sydney, Australia | 8,005 miles | 193–386 ms |
| Mumbai, India | 8,312 miles | 201–401 ms |
| Singapore | 8,773 miles | 212–424 ms |
Distances are from Utah. Round trips are estimated from fibre distance, not measured — the figure your users see depends on where they are.
Farms in Utah
The closest of our 24 data centres to Utah is Los Angeles, about 558 miles away. Round-trip time is set by physical distance more than by anything else, so the nearest site is usually the right one.
Utah has a population of about 30,835, which is why the medium build above is the one most likely to fit a Farms business here — though the other two are a click away if it does not. Local time is America/Denver, 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 state privacy laws such as the CCPA. Pricing is quoted in USD, and the figure is the same wherever the machine physically sits.
Network reach from Utah
Estimated from fibre distance rather than measured, and stated as a range. Your own access network decides the rest.
| Data centre | Distance from Utah | Estimated round trip |
|---|---|---|
| Los Angelesamericas | 558 miles | 13–27 ms |
| Santa Claraamericas | 575 miles | 14–28 ms |
| Seattleamericas | 711 miles | 17–34 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 medium size assumed above, that is roughly 213,333 requests a day crossing that link.
Farms hosting in Utah — FAQs
What size server does a Farms business in Utah need?
Where would the server for my Utah business actually run?
Is a VPS enough for Farms, or do we need a dedicated server?
Can you host field records & cropping plans for us?
Can we start smaller and grow?
Other industries in Utah
Same city, different workload.
Farms hosting nearby
The same workload, in the nearest cities.