Run your servers as you run your local development environments: Standard, servers with dedicated cores and servers with a memory-hungry load as separate tiers, all on KVM, all on NVMe RAID10 storage, and published benchmarks, in Amsterdam and New York.
This is NOT a case of artificial sub-tiers created for a 'Pro' or 'Scale Up' version of existing gear, to support specific workloads. It's three different hardware generations (3 tiers of CPU) created to support 3 different types of workloads. Scale up within a tier as needed, rather than scaling up between tiers.
We publish every component and every measurement from our public benchmark results page.
Database & HTTP, measured
Top of compared
Here the medians of the measured metrics of pgbench TPS and wrk requests/second for the Database & HTTP workloads on 2 vCPU / 4 GB / Dedicated hosts in Amsterdam and New York. All runs can be found here.
Multi-homed transit routers exist in both regions. Serve your users from the region that is closest to them or failover to both regions.
This environment supports a number of distros and you can upload the ISO for the desired distribution to install the server in seconds. Then you can switch to another distro in a couple of seconds in the control panel or via API. You just need to reinstall the server in the chosen distribution.
Windows Server support is coming. We're starting with the Linux variants and will add Windows Server support at a later point. Linux-first.
A web panel for humans, a documented REST API for everything else. Console access in-browser for emergencies. Use it in your Terraform, your CI or your own dashboard.
What you can drive from the panel API:
# Reboot a VPS via the panel API
$ curl -X POST https://api.buyvps.com/v1/instances \
-H "Authorization: Bearer $TOKEN" \
-d '{"region": "ams", "plan": "D-16", "image": "ubuntu-22"}'
{
"id": "vps-2k9x7p",
"status": "provisioning",
"region": "ams",
"plan": "D-16",
"ipv4": "203.0.113.42",
"ipv6": "2001:db8::42",
"ready_in": 38
}
For a long time now overcommit has been the industry standard to sell servers. Virtually all Virtual Private Servers are sold based off the sales chart for all of the vCPU and RAM that are available on servers, many of which are actually sold under capacity. Then when a customer buys more vCPU and RAM than a single physical node has available then only one customer at any time can be fully utilizing a customer's funds for a server. That customer will get low latency for packets and high performing applications until other customers start to take over the server. At that time the other customers will have to wait for their packets to arrive and their applications will perform poorly due to the increased competition for resources from the other customers on the server.
As said above all 3 "node-policies" / "density" tiers are build with the same basis as for the memory (hard capped for the usable memory per node) but then differing designs for CPU sharing / vCPU "time-slicing" between the boxes as well as differing box placements in respect to each other on the respective tier.
No introductory pricing (no tricks), no price hike around renewal time, signed up price in year 5, cancel anytime.
