Nevada, United States

Software VPS in Nevada

Dedicated cores for builds, CI and compute that cannot wait its turn. Built by hand, usually the same day.

Configure your build server → Recommended from $305.50 USD / month
  • Dedicated cores throughout
  • Same price in all 24 locations
  • Root access, any toolchain
Closest location live
Nevada and its closest data centre Nevada joined by a link to the Dallas data centre, 339 km away. Nevada Dallas Texas, United States
339 km from Nevada
5–10 ms estimated round trip

Estimated from fibre distance, not measured from Nevada. Your real figure depends on your connection and route, and lands inside this range.

Choose how the processor is shared

Every class ships the same hardware menu and the same Ubuntu Server 24.04 (LTS) 64-bit image. What changes is how the processor is shared — and the price moves with it.

Availability

Budget friendly

Cheap for a build box that runs overnight and that nobody waits on.


$283.50USD

per month

Configure

General purpose

Recommended

Consistent processor time, which keeps build times roughly repeatable.


$294.50USD

per month

Configure
Hourly only

Burstable

Not for compilation

A poor fit. Throttles under sustained load, and compilation is sustained load throughout.


$0.5859USD

per hour — booked for a window, not subscribed

Book by the hour

Add cores for a heavy release week and take them off afterwards — the change is made by hand on the same server, usually within the hour.

Your toolchain, your runners

A build server is only useful if it can run what you actually build with. This is a machine with root on it, not a platform with a supported-language list.

Any runtime, any version

Install the compiler, SDK or interpreter you need, at the version you need, including the ones your CI provider stopped supporting.

Self-hosted CI runners

Point GitHub Actions, GitLab CI or Jenkins at it and stop paying per build minute. The machine is yours whether it is busy or idle.

Nothing else on your cores

On the Dedicated class no other customer shares the processor, which is what makes a build time repeatable rather than merely typical.

Where your server runs

All 24 locations cost the same, so pick whichever sits closest to the people who will actually use the server. Choose the region closest to the people pushing code and to whatever the build pulls from — package registries and your git host are the two round trips a build makes most.

Americas coverage 9 live
Americas data centre locations 9 locations across Americas, with Dallas marked as the closest to Nevada. Dallas Nevada

Nevada is closest to Dallas. Every marker costs the same per month.

Show all 24 locations and distances from Nevada ▾
Location Distance Est. round trip
Americas · 9 locations
Dallas, United States 339 km 5–10 ms
Atlanta, United States 825 km 12–25 ms
Chicago, United States 1,040 km 16–31 ms
Miami, United States 1,539 km 23–46 ms
Toronto, Canada 1,638 km 25–49 ms
New York, United States 1,875 km 28–56 ms
Los Angeles, United States 2,297 km 34–69 ms
Santa Clara, United States 2,615 km 39–78 ms
Seattle, United States 2,873 km 43–86 ms
Europe, Middle East & Africa · 8 locations
London, United Kingdom 7,350 km 110–221 ms
Amsterdam, The Netherlands 7,617 km 114–229 ms
Madrid, Spain 7,635 km 115–229 ms
Stockholm, Sweden 7,919 km 119–238 ms
Frankfurt, Germany 7,970 km 120–239 ms
Milan, Italy 8,274 km 124–248 ms
Bucharest, Romania 9,394 km 141–282 ms
Tel Aviv, Israel 10,906 km 164–327 ms
Asia-Pacific · 7 locations
Tokyo, Japan 10,543 km 158–316 ms
Delhi NCR, India 13,030 km 195–391 ms
Hong Kong, China 13,143 km 197–394 ms
Kolkata, India 13,759 km 206–413 ms
Mumbai, India 13,970 km 210–419 ms
Sydney, Australia 14,157 km 212–425 ms
Singapore 15,729 km 236–472 ms

Distances are from Nevada. Round trips are estimated from fibre distance, not measured — the figure your users see depends on where they are.

Root access and your choice of toolchain

Daily off-server backups

No shared CPU — dedicated cores throughout

Any Linux image, or Windows if you build for it

Included with every Software server, in every class, at every location.

Build hosting for Nevada

We host servers for companies throughout Nevada and the rest of United States. You tell us what the server is for, we build it by hand, and you get access and the login details the same working day.

Dallas is our closest location at 339 km, which makes it the usual starting point. If the people using the server are somewhere else, host it somewhere else — every location costs the same.

Software VPS in Nevada — FAQs

Can I run my own CI runners on it?
Yes. It is your server with root access, so self-hosted GitHub Actions runners, GitLab runners, Jenkins agents or anything else you want to install. No per-minute billing and no queue you are sharing with strangers.
Why does the hardware class matter so much for builds?
Compilation is sustained load from the first second to the last. Shared classes give you processor time when it is spare, which makes build times vary; dedicated cores do not, so a build takes as long as it takes and no longer.
Which runtimes and languages can I use?
All of them. You choose the image and install what you like — there is no supported-language list, because there is nothing between you and the machine.
How fast will it feel from Nevada?
An estimated 5–10 ms to Dallas at 339 km. For a build server what usually matters more is the round trip to your package registry and your git host, so pick the region closest to those and to the people pushing code.
How much does it cost in Nevada?
From $283.50 USD per month, with $305.50 USD on the Dedicated class for compilation work. The same prices apply in all 24 locations.

Other servers in Nevada

Same hardware, tuned for a different job.

Software hosting nearby

Other towns we host for in the region.