WordPress on a VPS: how to set it up and when it pays off

VPS vs managed WordPress hosting

Managed WordPress hosting runs the server for you: updates, caching, backups and support are part of the price, but you get less control and pay more per resource. Shared hosting is cheap but you share the machine with many other sites.

A VPS sits in between. You get dedicated resources, root access, and the freedom to install anything - Redis, a second site, an n8n instance next to the blog. It suits people who are comfortable with a terminal or willing to use a control panel, and sites that have outgrown shared hosting.

If you never want to think about the server, managed hosting is the honest recommendation. If you want speed per dollar and control, a VPS wins.

The WordPress VPS stack

WordPress needs a web server, PHP and a database. A proven modern stack looks like this:

• Web server: Nginx, or OpenLiteSpeed if you want the LiteSpeed Cache plugin to do the heavy lifting.
• PHP-FPM with a current, supported PHP version and OPcache turned on.
• Database: MariaDB or MySQL on the same server for most sites.
• Redis as an object cache, so repeated database queries come from memory.
• A free Let's Encrypt certificate for HTTPS, renewed automatically.

Control panel or command line

You can build the stack by hand, but a panel saves time and mistakes. Free options such as CloudPanel, HestiaCP or the OpenLiteSpeed-based CyberPanel install WordPress in a few clicks and handle certificates, databases and PHP versions. Paid panels like cPanel or Plesk add polish and support but cost a monthly licence on top of the server.

Some providers offer a WordPress or panel template when you create the server - check the provider's OS list before you install from scratch. A panel also uses some RAM, so leave headroom on small plans.

Caching and speed

Most WordPress slowness comes from PHP building the same page over and over. Page caching serves a finished HTML file instead, which is the single biggest speed win. Use your web server's cache (FastCGI cache on Nginx, LiteSpeed Cache on OpenLiteSpeed) or a caching plugin, plus Redis for logged-in users and WooCommerce carts.

Choose a data center close to your visitors - the provider cards below list locations where the data shows them - and put a CDN in front for images and static files if your audience is spread across continents.

Backups and security

On a VPS nobody backs up your site unless you arrange it. Some providers include backups - according to their pages, Hostinger includes free weekly backups and OVHcloud's newer VPS range includes a daily backup - but keep your own copy off the server as well: a nightly database dump plus the wp-content folder, sent to object storage or another machine.

• Log in with SSH keys and disable password logins.
• Turn on a firewall and open only ports 22, 80 and 443.
• Enable automatic security updates for the OS; update WordPress, themes and plugins weekly.
• Install Fail2ban or a similar tool to block brute-force attempts on wp-login.
• Test a restore once - a backup you have never restored is only a hope.

Picking a plan

Start from RAM: 1–2 GB for a small blog, 4 GB for a typical business site or a few WordPress installs, 8 GB+ for WooCommerce or busy sites with many plugins. NVMe storage helps database-heavy sites. The plan table below compares current prices; look at the renewal price too, because some providers show a low first term that rises later. Our server finder picks the spec for your traffic.