When you launch a website, one of the first questions is whether to take ordinary shared hosting or go straight to a VPS. Both put your site online, but they work differently and suit different projects. Below we explain the difference in plain terms and list a few signs that make the choice easier.
What shared hosting is
On shared hosting your site runs on a server together with other customers’ sites. CPU, memory and disk are shared, and each account has its own limits. The provider configures and updates the server. You manage the site from a control panel: add domains, email and databases, and install WordPress in a few clicks.
We covered how to pick a plan in our article on shared hosting.
What a VPS is
A VPS (virtual private server) also runs on a physical server next to others, but it gets its own share of resources that nobody else uses. Inside is a separate operating system with root access. You can install any software, change PHP and database versions, and tune the web server for your project.
That freedom has a cost: system updates, security and backups are the owner’s job unless you order administration separately. Our complete VPS guide goes into more detail.
Main differences
| Shared hosting | VPS | |
|---|---|---|
| Resources | Shared, with per-account limits | Dedicated to your server |
| Access | Control panel and FTP | Full root access |
| Server setup | Done by the provider | Done by you or your admin |
| Your own software | Only what the hosting allows | Anything that runs on the chosen OS |
| Skills needed | Basic | Linux or Windows Server administration |
| Price | Lower | Higher |
When shared hosting is enough
- You run a business card site, a blog, a landing page or a small online shop on WordPress, OpenCart or another popular CMS.
- Traffic is still modest and the site stays within its limits.
- You would rather not deal with server setup and updates.
For most new projects this is a sensible start. When the site grows, you can move it to a VPS.
When it is time to move to a VPS
- The site keeps hitting its limits: it slows down at peak hours, or the hosting reports that the load is too high.
- You need software that shared hosting does not offer: Node.js, a Python app, Docker, a separate database server.
- You need specific PHP or MySQL versions or non-standard web server settings.
- You host several client projects and want to isolate them from other people’s sites.
- You need a Windows remote desktop for accounting or office software.
How to avoid choosing wrong
Base the choice on what the site does today. Paying for resources you might need in a few years costs money and gives little back for now.
If you choose a VPS, decide in advance who will run it. When nobody on the team knows Linux, a server can easily go without updates. In that case, agree on help with administration from your provider, or start with shared hosting.
Once your VPS is running, go through our 15-step checklist. It covers basic security and backups.
Moving from shared hosting to a VPS
You will not have to rebuild the site. The files and the database are copied to the new server, and then the domain’s DNS records are switched. If you check the site on the new server before changing DNS, visitors will barely notice the move.
Not sure which option fits you? Open a ticket or use the form on our site, describe your project, and we will suggest a plan. You can compare the options on the shared hosting and VPS pages.
