Hosting WordPress on a VPS, and when not to

Thinking about moving your WordPress site from shared hosting to a virtual private server (VPS)? This guide is for Australian site owners weighing that jump. It covers what running WordPress on a VPS genuinely involves, sketches the setup, and explains when staying on managed hosting is the better call.

What a VPS changes

A VPS is your own slice of a server: a private operating system with root access, meaning you can install and configure anything. That's the appeal: you choose the PHP version, tune the caching, run scheduled tasks on your own terms, and host several sites or applications side by side.

The flip side is that nobody manages it for you. On shared hosting, the provider keeps the server patched, secured and running; on an unmanaged VPS, those jobs transfer to you. Before anything else, be honest about whether you want them.

The jobs that become yours

Running WordPress is the easy part. These are the ongoing responsibilities that come with the server underneath it:

• Software updates: the operating system, web server, PHP and database all need regular patching, separate from WordPress's own core, plugin and theme updates.
• SSL: the certificate that puts the padlock in the browser. Free certificates from Let's Encrypt renew automatically once configured, but you set that up and you notice when it breaks.
• Security: a firewall, hardened SSH (the remote command-line login, secured with keys instead of passwords) and an occasional eye on the logs.
• Backups: copies stored off the server, on a schedule, that you've actually test-restored. A backup you've never restored is a hope, not a plan.

The setup, in outline

This isn't a full tutorial, but here's the shape of the work and what each step achieves:

• Deploy the VPS with a mainstream Linux distribution. Ubuntu LTS (the long-term support release) is the common choice because most documentation assumes it.
• Lock down access first: log in over SSH, switch to key-based authentication and enable the firewall, so the server isn't sitting open while you build.
• Install the stack, usually LEMP (Linux, Nginx, MySQL or MariaDB, PHP) or LAMP (the same with Apache as the web server). The web server answers browser requests, PHP runs WordPress's code, and the database stores your content.
• Create a database and a database user for WordPress to connect with.
• Install WordPress and set file permissions so the web server can run the site without owning everything on the machine.
• Point your domain at the server's IP address and configure the web server to answer for that domain.
• Issue an SSL certificate and set up automatic renewal.
• Configure backups and automatic security updates before you call it done. They are the two steps most people skip.

How big a VPS does WordPress need?

Smaller than the marketing suggests. A single WordPress site with a caching plugin runs comfortably on 1-2 GB of RAM, which covers the stack plus healthy traffic. Add memory when you're running WooCommerce, several busy sites, or plugins with heavy admin screens.

Disk space is rarely the constraint. WordPress plus a typical media library fits in a few gigabytes, so 20 GB leaves ample headroom. Watch the transfer allowance instead: VPS plans typically meter monthly traffic, and a site serving large images or video to a big audience can reach that cap sooner than expected.

When managed shared hosting is the smarter choice

For most single WordPress sites, it is. Managed hosting bundles the server maintenance, SSL, email and one-click WordPress installs into a few dollars a month, and for a typical small site the performance difference is negligible. Budget an afternoon for a first VPS build, plus a little time every month afterwards. That time has a cost too.

A VPS earns its keep when you need something shared hosting can't offer: a specific PHP setup, other applications running beside WordPress, several sites consolidated onto one server, or simply the learning experience. If none of those apply, or if terms like SSH felt foreign a few paragraphs ago, managed hosting will save you hours and spare you the 2am outage that's yours alone to fix.

Making the call

If you want the control and you're willing to own the maintenance, a small VPS is a genuinely good home for WordPress. Start small and let monitoring, not guesswork, tell you when to grow. If you'd rather your host handled the server, that's a valid choice, not a lesser one.

If you're comparing Australian options, OzVPS runs both from an Australian data centre: VPS plans from $10/month, and Enhance-based web hosting from $5/month, prices in AUD.