VPS Hosting: Do You Need One?

What a VPS actually is

VPS stands for virtual private server. One physical machine is divided into several separate servers, and you rent one of them. Yours runs its own operating system, holds resources set aside for it, and has its own administrator login.

The web hosting guide covers the shared and business plans a VPS sits above. The difference from shared hosting is worth stating precisely, because the marketing rarely does.

Shared hosting divides a pool. How much capacity you get depends a little on what everybody else is doing at that moment.
A VPS divides the machine. Your slice is set aside whether you are using it or not. The gain is predictability more than raw speed.
A dedicated server is the whole machine. A VPS still shares hardware with other virtual servers, walled off from each other by the virtualization layer.

The part that changes everything

On a VPS you generally get root access, the administrator account on the server itself. You can install software, choose your own versions, run background processes and change configuration a shared control panel never exposes.

That access is the reason to buy a VPS. It is also why one goes wrong. A server you can change is a server you can break, and a broken server needs somebody to fix it.

The real reasons people move off shared hosting

There are a handful, and they are specific. If none describes your site, a VPS costs more every month and changes nothing you could point at.

Sustained traffic, not a spike. A busy afternoon every weekday is a different problem from one good week after a mention in the news, which what a traffic spike actually does covers. A shared plan absorbs the good week. The pattern that repeats is what runs out of room.
A heavy database. Sites that are really applications: member logins, a booking calendar written to all day, product search across a large catalogue, reports built on demand. That work happens on every visit and cannot be cached away.
Software the host will not install. A particular PHP extension, a language runtime the plan does not offer, a search engine running alongside the site, a background job that has to stay running.
You need root. If what you need is only reachable from a command line as administrator, a shared plan cannot get you there.
An isolation requirement you did not choose. A client contract or an insurer occasionally asks for a server not shared with unrelated parties.

How to tell a real trigger from a bad afternoon

Read your control panel's usage history by shape, not height. A line that brushes the ceiling for minutes a week is a plan doing its job. One that sits along it every weekday has run out.

Then rule out the cheaper explanation. Time the same page first thing and again at your busiest hour. If it is slow both times, capacity is not the limit, and when a slow website is not your host's fault is the page to read first.

Self-managed or fully managed, which is the real decision

Both are sold as VPS hosting, and the hardware question is the same either way. The difference is who the system administrator is, and it decides more than any specification.

On a self-managed server you are handed a machine and the keys. Everything after that is yours:

Operating system security patches, on an ongoing basis, forever.
The firewall, remote login access, and shutting the doors nobody needs open.
The web server, PHP and the database, including versions and configuration.
A control panel, if you want one, which usually means installing and licensing it yourself.
Backups kept off the server, and a restore you have actually tested.
Monitoring, and being the person who gets up and fixes it.

The patching line is the one that gets skipped. Shared hosting quietly includes somebody keeping the operating system current, and that person disappears the day you buy your own server. An unpatched VPS is a worse position than a shared account, because the whole machine is yours to lose.

Who does the work under each arrangement
What changes	Shared hosting	Self-managed VPS	Fully managed VPS
Who patches the operating system	The host, invisibly	You	The plan, for whatever it covers
Who is awake when it breaks at midnight	The host	You	The provider, within its terms
Who keeps your own site's software current	You, or whoever built it	Unchanged, still you	Unchanged, still you
Suits	Most business websites	Teams with somebody who administers servers	A business that needs the server, not the job

Notice the second-to-last row. Neither kind of VPS maintains the website itself. Managed means the server. Your WordPress install and your own code stay as much your problem as before, which is what WordPress security is for.

What to pin down before you buy either one

Managed is a loose word in this industry, so the feature list decides what you get rather than the label. Ask these before you pay:

Does managed include operating system security patching, and how often? This is the most valuable thing managed can mean. If it is not on the list, the plan is self-managed with a support phone number.
Is a control panel included and licensed, or extra? Running a server without one is entirely possible and entirely a command-line job. What is cPanel explains what you would be doing without.
Are backups taken off the machine, and can you restore one yourself? A copy stored on the server it came from is not a backup. Website backups covers what to ask for.
How do you get a firewall rule changed? On a managed server you usually cannot do it yourself, and finding that out during a launch is a bad afternoon.
Who moves the site on, and is it included? Migration onto a new server is real work. See website migration.

Storage, memory and processor figures are the part sales pages lead with, and the easiest part of the decision. Settle responsibility first, then compare numbers.

Get Your VPS Hosting Plan Ask whether you need one

Who should not buy it

This is the product on the site with the biggest no attached, and the no applies to most of the people who ask about it.

Leave it alone if

The site is a brochure. Pages about what you do, where you are and how to reach you. Shared hosting is the right size for that, not a compromise.
It is a small WordPress site. WordPress runs perfectly well on a shared plan. If the real question is who does the updating, that is WordPress hosting, a different purchase.
The real problem is a slow theme. Oversized images, a page builder loading on every view, three analytics tools and a chat widget waiting on somebody else's server. All of it is slow on a VPS too, and now it costs more.
Nobody is going to administer it. If you cannot name the person responsible for patching a self-managed server, you are buying a liability. Buy managed or stay where you are.
You are buying ahead of growth. Moving up later is a straightforward job. Years of unused capacity is money you do not get back.

Worth having if

The site is really an application, and the load is steady rather than occasional.
You need software or a version the shared plan will not install, and you have checked that it genuinely will not.
The site is already lean and cached and still meeting limits under ordinary traffic.
Somebody administers servers for you, or you are buying fully managed and know what that covers.
A contract or an insurer requires a server not shared with unrelated parties.

Moving a site onto a VPS

This is not a plan upgrade. It is a migration onto a machine that starts out empty. The order that keeps email alive is on the website migration page. Four things are specific to a VPS.

The server does not arrive set up. Web server, PHP, database and control panel are installations, not settings. On a managed plan, ask which of them the provider does.
Reproduce the PHP version and its extensions first. A site that ran fine on shared hosting throws errors on a newer version, and a missing extension breaks one feature rather than the whole site, which is harder to spot.
Scheduled jobs do not come along. Backups, feed imports and mailing tasks are configured per server. Write down what runs and when before you leave the old account.
Do not run your own mail server. Deliverability is a specialism of its own. Keep mail with business email and leave it out of the move.

Then check the SSL certificate on the new server, submit every form, watch the site for a full week including your busiest hour, and leave the old account running until traffic has moved.

How AldoMedia helps

AldoMedia has been building and maintaining websites for Western New York businesses since 1999, and most of the people who have asked us about a VPS did not need one. We are an independent authorised reseller, so what we add is a straight read on whether the server is the problem and the migration if you go ahead. Call 716-771-2536 and tell us what the site does, or start with the support pages.

Common questions

VPS hosting questions

Does my small business website need a VPS?

Almost certainly not. A site of pages about what you do, where you are and how to reach you belongs on shared hosting, and moving it to a VPS changes nothing a visitor would notice. The businesses that genuinely need one can usually name the reason.

What is the difference between a self-managed VPS and a fully managed VPS?

Who the system administrator is. On a self-managed server you get root access and the whole job that comes with it: operating system patches, the firewall, the web server, backups, and being the person who fixes it at midnight. Fully managed means somebody else holds that job.

Will a VPS make my website faster?

Only if a shortage of capacity is what slows it. Large images, a long plugin list and slow third-party scripts are slow on any server, and a VPS makes them slow more expensively. Time the same page first thing and again at your busiest hour. If both are slow, the plan is not the problem.

Who installs the security patches on a VPS?

On a self-managed server, you do. That is the part nobody mentions at the point of sale. Shared hosting quietly includes somebody patching the operating system, and buying your own server takes that person away unless you buy a managed plan.

Can I go back to shared hosting if a VPS turns out to be too much?

Yes, and people do. Moving down is the same job as moving up: files and databases copied across, the site tested on the new account, then the switch. It is easier if you have not built the site around something a shared plan cannot run.

Related guides and services

Shared Hosting

The plan most sites should be on, and how to tell when you have outgrown it.

Is shared hosting enough?

When a Slow Website Is Not Your Host's Fault

The checks worth doing before you buy any larger plan.

Find the real cause

Website Migration

Moving a site onto a new server without taking the site or the email down.

How a migration works

Also useful: the web hosting guide for the shared and business plans, and website security for what protecting a server involves.