WordPress logo
CMS & Commerce

WordPress Hosting on a VPS You Control

WordPress on a server you control, with no plugin blocklist and your own PHP and caching stack.

Size a server for WordPress

Every stop is a real configuration you can deploy. Priced per 30 days, billed by the hour, exclusive of 18% GST.

2 vCPU
4 GB
40 GB
5 TB

What WordPress is

WordPress on a VPS is a different proposition from shared or managed WordPress hosting. You are not renting a slot in someone's tuned stack - you are running the web server, PHP and MySQL yourself, and every decision about them is yours.

That is worth doing when the constraints of managed hosting start to bite. Managed platforms commonly ban plugins that conflict with their caching, cap PHP workers, restrict cron, and disallow anything that writes outside the uploads directory. Those rules exist for good reasons at their scale, but they are someone else's trade-offs.

It is worth being clear about what changes: on a VPS, updates, backups and security patching become your responsibility. If you want WordPress core updated automatically and someone else on call for it, managed hosting is the better answer. If you want to run a plugin they will not allow, or a PHP extension they do not ship, this is how.

Why run WordPress on a VPS

No plugin blocklist. If it runs on PHP, you can install it.

Choose your PHP version and extensions - and run more than one if different sites need different ones.

Real Redis or Memcached object caching, not just a page cache.

WP-CLI over SSH, and cron driven by the system rather than by page views.

Databases stay local, so query latency is not crossing a network.

WordPress features

Any theme or plugin, including commercial and custom code

Object caching with Redis for logged-in and dynamic pages

Full WP-CLI access for migrations, search-replace and bulk updates

System cron for reliable scheduled posts and background jobs

Staging copies on the same server

Direct MySQL access for slow-query work

Recommended server

A starting point for WordPress, not a hard floor — size it on the sliders.

Memory4 GB for one busy site; 8 GB for several or for WooCommerce
CPU2 vCPU; 4 once traffic is sustained or checkout is busy
Storage40 GB for a typical site; media libraries grow faster than databases
Operating systemUbuntu 22.04 LTS or AlmaLinux 9

How deployment works

WordPress is installed on the server with PHP-FPM, MariaDB and a web server, plus Redis for object caching. TLS is issued for your domain. Nothing is locked - you can change PHP versions, add sites or replace any component over SSH.

It is your server. WordPress is installed directly on your VPS or VDS, not inside a container we manage. You get root over SSH, you can install anything alongside it, change its configuration, or remove it entirely. We do not hold a key to it.

What people run it for

Sites managed hosts refuse

Membership plugins, custom post types at scale, or anything that writes outside uploads.

Multisite networks

Run a network with its own domain mapping without per-site pricing.

Agency hosting

Several client sites on one machine, isolated by user and PHP pool.

WooCommerce

Checkout is uncacheable by nature, so it depends on PHP and database speed you control.

WordPress hosting questions

Control. You choose the PHP version, the caching layer and the plugins, and you are not sharing CPU with other tenants. The trade is that updates and backups become yours to manage.

Deploy WordPress on your own server

Root access, your choice of size, and no container between you and the application.