Root access, and a slice that is actually yours
A guaranteed allocation of CPU, memory and NVMe, with full system access. Install what the application needs instead of asking whether you are allowed to.
- Access
- Full root
- Resources
- Guaranteed
- Storage
- NVMe
- Admin
- Managed or not
The things shared hosting will not let you do
This is the whole reason the tier exists. If none of it applies to you, save the money and stay where you are.
Choose your runtime
A specific Node, Python, Ruby or PHP version, held there while the rest of the world moves.
Install system packages
Image libraries, a headless browser, a search engine, a message broker.
Run background work
Queues, workers and schedulers, instead of hoping a web request finishes in time.
Tune the web server
Your own nginx or Apache config, cache rules and limits.
Guaranteed resources
The allocation is reserved. A neighbour's spike is not your problem.
Your own firewall
Ports, rules and access policy set the way your security review wants.
Managed or unmanaged
Unmanaged is cheaper and it is a job. You own patching, hardening, monitoring and the 2am restart. Managed means we do all of that on your server and you keep root anyway. Most businesses buying their first VPS want managed and do not know it is an option.
- UnmanagedYou administer it. Right if you have someone who wants to.
- ManagedWe patch, harden, monitor and back up. You still get root.
- Either wayFree migration in, daily backups, free restores.
Start smaller than you think
Resizing will be prorated and quick. Over-buying on day one is the expensive mistake, not under-buying.
One busy WordPress site with a cache
Start around2 vCPU · 4 GB
Watch: PHP worker count before CPU
A Node or Python application
Start around2 vCPU · 4 GB
Watch: Memory, first and always
App plus its own database
Start around4 vCPU · 8 GB
Watch: Disk I/O and connection limits
Several client sites on one box
Start around4 vCPU · 8 GB
Watch: Memory, then storage
Queues or media processing
Start around4 vCPU · 16 GB
Watch: CPU during the burst, not the average
Starting points for a conversation, not a quote. The honest way to size is to measure for a couple of weeks after you move.
Do you actually need root?
If the honest answer is no, cloud hosting gives you the headroom without the administration, and it is available today. If the answer is yes and the load is sustained, a dedicated server may be cheaper per unit of work.
Before you buy
The things people actually ask us, answered plainly.
What is the difference between a VPS and shared hosting?
On shared hosting you get a slice of a server's resources that flexes with what your neighbours are doing, and no system-level access. On a VPS the slice is guaranteed and you get root, so you can install packages, choose runtime versions and run background processes. You are also responsible for keeping it patched unless you buy it managed.
Managed or unmanaged — which do I need?
If nobody in your organisation is going to apply security updates, read a system log or restart a service at an inconvenient hour, buy it managed. Unmanaged is genuinely cheaper and genuinely a server administration job. There is no shame in either answer; there is real risk in choosing wrong.
Can I run Node, Python or a background worker?
Yes. That is most of the reason to move to a VPS. You choose the runtime and version, you can run queues, cron jobs and long-lived processes, and you can install whatever the application needs.
What happens if I get the sizing wrong?
You resize. Moving between VPS sizes is a resource change rather than a migration, and billing is prorated to your cycle. Start smaller than you think and watch the numbers for a fortnight.
A plan that still makes sense in year two
Free migration, free SSL and daily backups on every plan, with a 30-day money-back guarantee.
Prefer the phone? (305) 671-1272 · Existing customer? Client login