Choose the smallest hosting environment that actually fits.
This guide separates the project from the server. Use workload, control, persistence and isolation requirements to decide where to start.
Answer the technical questions. The result is a starting point, not an automatic purchase decision.
What each hosting tier is for
Use the “not for” column as seriously as the “best for” column. Prices shown are starting references from the current GreatHosts homepage; confirm live product pricing before ordering.
| Service | Best for | Not for / move higher when | Control model | Starting reference |
|---|---|---|---|---|
| Shared Hosting | Static sites, WordPress, conventional PHP/MySQL projects and ordinary business websites. | Avoid when you need root access, custom system services, persistent application processes or sustained dedicated CPU. | Managed hosting · GreatHosts CP | from $5.08/mo |
| Semi-Dedicated | Busy managed websites that need more CPU and memory headroom while keeping a hosting-control-panel workflow. | Not the right tier when you need root access, custom daemons or operating-system administration. | Managed hosting · GreatHosts CP | from $40/mo |
| KVM VPS | APIs, persistent Node.js/Python services, automation, private services and custom application stacks that need root access. | Unnecessary for a normal website if you do not need server-level control; it adds operating-system administration. | Root access · isolated virtual machine | from $24/mo |
| OpenVZ VPS | VPS workloads that need more control and resources than shared hosting and fit container-based virtualization. | Prefer KVM when stronger virtualization isolation or broader operating-system control is a requirement. | VPS · container virtualization | See live plans |
| Dedicated Server | Sustained high workloads, full-machine isolation, specialized stacks and production systems that justify physical resources. | Usually poor value for a small or early-stage website whose workload fits shared hosting or VPS. | Full physical server | from $70/mo |
A simple escalation path
- 01Start with Shared Hosting
If the project is a normal website, WordPress site or conventional PHP/database application and does not need server-level services.
- 02Use Semi-Dedicated for managed headroom
When the website needs more managed CPU/memory capacity but you still do not need root access.
- 03Move to KVM VPS for server control
When you need root access, persistent services, custom runtimes, APIs, automation or stronger virtual-machine isolation.
- 04Use Dedicated when physical resources are justified
When sustained load, isolation or specialized requirements make a full machine the sensible choice.
What this guide does — and does not do
This is GreatHosts’ own product-suitability guide, not an independent comparison. It is designed to help a customer or AI agent reject an unsuitable tier as well as select a suitable one.
- Current availability and final prices come from the live product pages and checkout.
- The guide never overrides checkout validation, billing or provisioning.
- No hosting tier is recommended merely because AI was used to create the project.
- Final order submission and payment authorization remain human-confirmed actions.
Structured facts for search engines and AI agents
The same suitability data is published as structured schema and a JSON catalogue. A concise llms.txt discovery map is also available as a supplementary index.
Still unsure? Start with the least complex sensible option.
You can inspect the live product pages and GreatHosts CP before committing to more infrastructure.