VPS vs shared hosting: when to switch

The short answer: switch for a need, not for status

Plenty of people move to a VPS because "having your own server feels more professional," then pay more for resources they never touch. The right question is not which one is better. It is what you need that shared hosting does not give you.

Rule of thumb:

• Stay on shared for brochure sites, landing pages, standard WordPress, PHP and forms.
• Move to a VPS when you need your own process (Node, Next.js, Python), root access, software you install yourself, heavy scheduled jobs, or guaranteed resources for an app that grew.

What each one is, without jargon

Shared hosting is one server split among many sites. The provider handles the operating system, updates, machine security and the web server. You upload files, create databases and configure domains from a dashboard. It is cheap because the machine's cost is shared.

A VPS (virtual private server) is a slice of a physical server reserved for you, with its own memory, CPU and disk, plus root access. You install whatever you want. In exchange, updating, securing and monitoring it is on you, or on whoever you hire.

Signs you have outgrown shared hosting

1. You need to run an app, not just serve pages. A Next.js server, a Node API, a Python worker. Most shared plans were built for PHP and static files.
2. You need to install something. A system library, a different database, a specific runtime version.
3. Scheduled jobs or queues that run long and get killed by plan limits.
4. Resource limit errors showing up often, like "process limit reached" or "memory exceeded," even after optimizing.
5. A client with enough traffic to justify isolation, so their spike does not slow down everyone else.

If none of these apply, a VPS is probably extra cost.

What changes when you move to a VPS

A VPS solves resources and control, but it hands you a list that used to belong to the provider:

• Updates for the system and packages.
• Security: a firewall, SSH key login instead of passwords, services exposed only when needed.
• Backups: someone has to make sure copies exist and actually restore.
• Monitoring: knowing when the disk is filling up or a process died.
• Logs: where to look when something breaks at 2 a.m.

For a freelancer or a small agency, that list is the hidden cost of a VPS. Put it in the math next to the monthly price.

A middle path: each thing where it belongs

You do not have to pick one for everything. A common, sensible split:

• Client brochure sites, PHP and WordPress on managed hosting, where maintenance is not your job.
• The web app with signup, login and its own process in an environment built for that.
• A VPS only when an app needs dedicated resources or specific software.

The split also helps with billing: the client who needs a VPS pays for it, and the others do not carry that cost.

Common mistakes when switching

• Buying the VPS before measuring. Without real memory and CPU numbers, picking a plan is a guess. Look at what you already run before choosing a size.
• Moving every site at once. Move the app that triggered the change first. Sites that were fine on managed hosting can stay there.
• Forgetting backups on day one. A new server starts with no copies. Turn on backups before any client data lands on it.
• Leaving password login open. Use SSH keys and disable password login as soon as you can.
• Not agreeing on who pays. If the VPS is for a client, its cost belongs in the proposal from the start, not as a surprise on your own bill.

How to do it on Basely

On Basely, both worlds live in the same dashboard:

• Websites: HTML, PHP and WordPress with SSL and the client's domain, without you running a server.
• Web Apps: Next.js apps can be published on our server within your platform plan's limit, or on a VPS.
• VPS: a server in the region you choose, priced at the provider's cost plus our margin. SSH keys from the dashboard, backups and logs.

One detail that matters when you look after a client's server: on a Basely VPS the owner decides and the operator only does what is allowed. You can operate your client's server, deploy, read logs and run backups, while decisions like canceling or changing plans stay with whoever pays.

And if you work from the terminal, the Connector lets your agent read logs and run allowed commands on the server without leaving Claude Code.

Decide in five minutes

1. List what each site or app needs to run.
2. Mark anything that needs its own process, root or installed software.
3. Whatever is not marked stays on managed hosting.
4. Whatever is marked goes to the plan's app server or to a VPS.
5. Review every few months with real usage numbers.

Start with what you have, and change servers when a concrete signal shows up.