High Frequency plans run on higher-clock processors with NVMe storage throughout. The distinction worth understanding is this: if your site is slow because each individual request takes too long, faster cores fix that and more cores do not. If it is slow because too many requests arrive at once, the opposite is true. This range answers the first problem.
That makes it a good fit for the ordinary shape of a busy website — a WordPress or WooCommerce install, a forum, an application with a chatty database layer. Those workloads spend their time in one thread waiting on one query, and clock speed is what shortens the wait.
If what you actually need is performance that never varies with other customers’ load, rather than performance that is simply faster, look at Optimized Cloud instead — those plans have dedicated cores. Speed and isolation are different problems, and it is worth knowing which one you have before paying to solve the other.
Faster Cores for Work That Waits on One
Deploys to 2 locations — choose from every location this plan offers at checkout; some cost more
| Select | Plan | vCPU | Memory | Storage | Bandwidth | Location | |
|---|---|---|---|---|---|---|---|
| 1 | 1 GB | 32 GB NVMe | 1 TB | Newark, US | $15.99/mo | ||
| 1 | 2 GB | 64 GB NVMe | 2 TB | Newark, US | $27.99/mo | ||
| 2 | 2 GB | 80 GB NVMe | 3 TB | Newark, US | $39.99/mo | ||
| 2 | 4 GB | 128 GB NVMe | 3 TB | Newark, US | $50.99/mo | ||
| 3 | 8 GB | 256 GB NVMe | 4 TB | Newark, US | $95.99/mo | ||
| 4 | 16 GB | 384 GB NVMe | 5 TB | Newark, US | $179.99/mo | ||
| 6 | 24 GB | 448 GB NVMe | 6 TB | Newark, US | $269.99/mo | ||
| 8 | 32 GB | 512 GB NVMe | 7 TB | Newark, US | $359.99/mo | ||
| 12 | 48 GB | 768 GB NVMe | 8 TB | Newark, US | $478.99/mo | ||
| 16 | 58 GB | 1024 GB NVMe | 9 TB | Seattle, US | $598.99/mo |
No plans in this family.
Built for Single-Thread Speed
Higher Clock Speeds
These plans run on higher-frequency processors than our standard range. For anything that spends its time in one thread — the typical web request, the typical database query — clock speed is what shortens it, and adding more cores does not.
NVMe Storage Throughout
Every plan is on NVMe rather than ordinary SSD, so the disk stops being the thing a page load waits for. It shows up most on database-backed sites, where reads are small, frequent and in the critical path.
Where It Shows
A busy WordPress or WooCommerce site, a forum, an application with a chatty ORM — anything where one request has to finish before the user sees anything. These are the workloads where a faster core is felt directly.
Full Root Access
Your own server, your own stack, your own tuning. Install what you need and configure it how you want; nothing is managed on your behalf.
Fixed Monthly Price
Billed monthly at the price shown, on a normal renewal invoice — not by the hour. The number in the plan table is the number on the bill.
Ready in Minutes
Provisioning is automated. The server is built and reachable within minutes of checkout rather than waiting on anyone.
Is This the Right Range?
More Cores Do Not Fix a Slow Request
This is the distinction worth getting right. If your site is slow because each request takes too long, faster cores help and more cores do not. If it is slow because too many requests arrive at once, the opposite is true. High Frequency answers the first problem.
A Good Default for Database-Backed Sites
Most content sites and shops are limited by a handful of queries and one PHP process at a time. That is precisely the profile these plans suit, which is why they are usually a better upgrade than moving to a larger shared-core plan.
If You Need Guaranteed Cores Instead
High Frequency plans are fast, but if your requirement is that performance never varies with other customers’ load, our Optimized Cloud range has dedicated vCPU. Speed and isolation are different problems and it is worth knowing which one you have.
FAQs
Have A Question?
If you can't find the answer you are looking for our support is just an email away.
Contact UsWhat makes these different from standard VPS plans?
The processors run at a higher clock speed and the storage is NVMe throughout. For work that happens one request at a time, that combination reduces how long each request takes — which is a different improvement from having more cores available.
Will my site actually feel faster?
If it is currently waiting on the processor or the disk for individual requests, yes, and noticeably. If it is idle most of the time, or limited by an external API, or by the amount of memory available, then a faster core is not the constraint and you should look at that instead.
How do these compare to Optimized Cloud?
High Frequency is about raw speed per core at a lower price. Optimized Cloud is about dedicated cores that never share with anyone. If your problem is that the site is slow, start here; if your problem is that performance is unpredictable, look there.
Are these billed by the hour?
No, these are monthly plans at the price shown. Our hourly ranges are Cloud GPU and VX Compute.
Can I upgrade later?
Yes. Moving up within the range adds cores, memory or disk to the server you already have rather than rebuilding it, so your data and configuration stay put.
Is a backup included?
Backups are a separate service rather than something bundled in. We offer scheduled backups as an add-on, and you can also take snapshots yourself at any time — worth setting up before you put anything important on any server.