WordPress VPS hosting puts your WordPress sites on a virtual private server (VPS) of their own: a fixed number of vCPUs, your own memory and NVMe disk, your own IP address and full control over PHP and the database. You need one when a site earns money, when several sites share one bill, or when plugins need more PHP workers, memory or extensions than shared hosting allows. For one small brochure site, shared or managed WordPress hosting is usually the easier buy. To size a server with numbers instead of guesses, we ran WordPress 7.1.3 with Nginx, PHP 8.4 and MariaDB on a 2 vCPU Debian 13 test server and measured it as a plain blog and as a WooCommerce shop. Our plans, in Amsterdam, Dublin and Prishtina, are on the WordPress VPS hosting page.
Key facts, checked on 14 October 2026:
- WordPress 7.1.3 is the current release, published on 6 October 2026, and only the newest 7.1 release is actively maintained (WordPress releases).
- WordPress recommends PHP 8.3 or greater, MySQL 8.0 or greater or MariaDB 10.11 or greater, and HTTPS support (wordpress.org requirements, last modified 7 May 2026). Debian 13 ships PHP 8.4, which gets security fixes until 31 December 2028 (php.net), and MariaDB 11.8.
- WordPress runs 40.0% of all websites, and 58.5% of the sites whose content management system is known (W3Techs, 14 October 2026).
- In our lab the whole server used 150 MB of memory at rest and 198 to 530 MB under load. Two vCPUs built about 28 uncached blog pages or 7.5 WooCommerce shop pages per second.
What a WordPress VPS is, and when you need one
A VPS (virtual private server) is a slice of a physical server that behaves like a computer of its own. At RS Computers each one is a KVM virtual machine with root access, so you choose every program that runs on it. WordPress needs three programs there: a web server such as Nginx, PHP to run WordPress's code, and a database, MariaDB or MySQL. A PHP worker is one PHP process that builds one page at a time; the number of workers decides how many visitors who miss the cache are served at once.
You probably need a WordPress VPS when:
- the site sells, books or takes sign-ups, so slow cart, checkout and account pages cost you money;
- you run several sites, your own or clients', and want one server and one bill;
- a plugin needs a PHP extension, a longer timeout, a real cron job or more memory than your host allows;
- you want the server in a chosen country, or your own IPv4 address for mail reputation or an API allow-list.
You probably don't when you have one small site, modest traffic and no wish to look after a server. Shared hosting costs less, and managed WordPress hosting takes the server work off your hands. A middle route is your own VPS with our managed WordPress care, described below.
Shared hosting, managed WordPress hosting or a WordPress VPS
| Shared hosting | Managed WordPress hosting | WordPress VPS | |
|---|---|---|---|
| Who it suits | First sites, small brochure sites, tight budgets | One or a few important sites whose owners want no server work | Shops, agencies, several sites, custom stacks, anyone who wants control |
| Example limits | Hostinger Web Premium: 2 GB RAM, 1 CPU core, 40 PHP workers and 400,000 inodes (files and folders) | Kinsta Single 35k: 1 site, 35,000 visits a month and 10 GB of disk; extra visits cost $0.50 per 1,000 | The plan's vCPU, RAM and disk. No visit cap; our plans include 1 to 100 TB of traffic a month |
| Plugins and software | What the host's stack supports | Some plugins are banned: WP Engine's list includes W3 Total Cache and several backup plugins | Any software that runs on Linux, within our acceptable use policy |
| Control | A control panel for your account, no root | WordPress and its files; the host runs the server | Root: PHP version, workers, database, firewall, cron |
| Who does the server work | The host | The host | You, with the commands below, or a panel |
The examples come from the vendors' own pages, checked on 14 October 2026: Hostinger's plan limits, Kinsta's pricing and overage rates (updated 9 March 2026), and WP Engine's disallowed plugins (updated 28 July 2025).
Shared hosting is the cheapest way to have a website, managed hosting the cheapest way to never touch a server, and a VPS the cheapest way to get memory, PHP workers and a database that serve nobody but your sites. If that last one is your need, compare the sizes on our WordPress VPS plans page.
What WordPress really uses: our lab numbers
On 14 October 2026 we built the test server as an Incus container on our Amsterdam lab machine: Debian 13, 2 vCPUs and a 2 GiB memory limit (the size of VPS Micro), Nginx 1.26.3, PHP-FPM 8.4.26, MariaDB 11.8.6 and WordPress 7.1.3 with the default theme and 100 sample posts. A second container sent traffic with ApacheBench 2.3 for 30 seconds per test, with no page cache, so PHP built every page. Then we added WooCommerce 11.2.1 with 50 products and Yoast SEO 28.7. "Peak memory" is the memory used by all programs on the server, without the disk cache Linux gives back when needed.
| Test | PHP workers | Visitors at once | Pages per second | Median wait | Peak memory |
|---|---|---|---|---|---|
| Blog homepage | 5 (Debian's default) | 20 | 27.8 | 0.71 s | 198 MB |
| Blog homepage | 10 | 20 | 23.2 | 0.79 s | 247 MB |
| Same homepage, WooCommerce and Yoast active | 10 | 20 | 12.9 | 1.53 s | 345 MB |
| WooCommerce shop page | 10 | 20 | 7.5 | 2.63 s | 357 MB |
| WooCommerce shop page | 20 | 40 | 7.0 | 5.62 s | 530 MB |
| Shop page, 1 GB memory limit | 20 | 40 | 7.1 | 5.37 s | 509 MB |
| Shop page, 1 GB memory limit | up to 80 (42 ran) | 100 | 4.3 | 13.99 s | 862 MB, then MariaDB was killed |
At rest, the plain site used 150 MB in total and the site with WooCommerce and Yoast 183 MB, most of it the MariaDB database server. The lab machine was shared with other tests, so read these as proportions; a heavier theme or more plugins will move them.
CPU sets the speed, not memory
With Debian's default of 5 PHP workers the server already hit its ceiling: 27.8 pages per second, which works out at about 72 ms of CPU per page on two vCPUs. Allowing 10 or 20 workers added no pages (23.2 and 25.6 a second), only longer waits and more memory, 342 MB with 20 workers. The shop page needed about 0.27 seconds of CPU each (41 CPU-seconds for 150 pages), so the same two vCPUs managed 7.5 a second.
Two plugins nearly halved the homepage
Turning on WooCommerce and Yoast SEO, with nothing else changed, cut the same uncached homepage from 23.2 to 12.9 pages per second. Every active plugin runs on every page that misses the cache, which is why a page cache matters more than any server setting. In our WordPress stack benchmark, Nginx served 2,811 cached pages per second on a server of this size, against about 25 without the cache.
ps says 100 MB per worker, but they share most of it
During the shop test, ps listed each PHP worker at about 100 MB, which suggests 2 GB for 20 workers. All 20 together used 436 MB, because they share OPcache (PHP's store of compiled code) and the same libraries. Size your server from the total in free -m, not the per-process figure, or you will pay for memory you never use.
Too many workers on 1 GB: MariaDB was killed
At a 1 GB limit, the size of VPS Nano, 20 workers peaked at 509 MB and the shop ran as before; even 50 workers fitted, at 781 MB. With the limit raised to 80 workers and 100 visitors at once, memory hit the ceiling, the kernel's out-of-memory killer stopped MariaDB, and a page requested while it restarted returned HTTP 500. systemd restarted MariaDB 6 seconds later. Set the worker limit to what the memory holds, not to the crowd you hope for.
Disk is rarely the limit: the whole test server, operating system included, used 1.5 GB, with a 171 MB database and 210 MB of site files. Uploaded images fill a disk far faster. The WordPress VPS hosting page lists every size with its city availability.
Which WordPress VPS plan fits your site
| Plan | What you get | What our numbers mean for it | Start PHP workers at | Good for |
|---|---|---|---|---|
| VPS Nano | 1 shared vCPU, 1 GB RAM, 20 GB NVMe, 1 Gb/s | 1 GB held 20 shop workers in our test; one vCPU means about 14 uncached blog pages a second (estimate, half our 2 vCPU result) | 5, Debian's default | One blog or company site with a page cache |
| VPS Micro | 2 shared vCPU, 2 GB RAM, 40 GB NVMe, 1 Gb/s | Measured: 23 to 28 uncached blog pages or 7.5 shop pages a second, at most 530 MB in use | 10 | A busy blog, a few small sites, a small shop with page caching |
| VPS Mini | 4 shared vCPU, 4 GB RAM, 80 GB NVMe, 1 Gb/s | About twice Micro (estimate), with room for a control panel, Redis and a staging copy | 20 | Several sites behind a panel, a growing shop |
| VDS Small | 4 dedicated vCPU, 8 GB RAM, 240 GB NVMe, 10 Gb/s | Mini's 4 vCPUs, but dedicated to you, so other customers' load does not slow your uncached pages | 20 to 30 | WooCommerce shops and membership sites |
| VDS Medium | 8 dedicated vCPU, 16 GB RAM, 480 GB NVMe, 10 Gb/s | About four times our measured Micro numbers (estimate) | 40 | Agencies, large shops, multisite networks |
Our rule of thumb is about 5 PHP workers per vCPU: more than our fast test pages needed, with spares for pages that wait on a payment gateway or another outside service. Watch free -m under real traffic and keep a few hundred MB free, since admin pages, imports and updates may use up to 256 MB each. VPS plans share their vCPUs with other customers; VDS plans have dedicated vCPUs, which counts most when much of your traffic misses the cache (see our VPS vs VDS comparison). VDS Large, with 16 dedicated vCPUs and 32 GB, covers the biggest sites. Every plan has NVMe, 1 to 100 TB of traffic a month and its own IPv4 and IPv6, and you can upgrade later from the client area with a short reboot. Choose your WordPress VPS plan here.
Which city for WordPress hosting: Amsterdam, Dublin or Prishtina
Put the server close to most of your visitors, because every uncached page and every new HTTPS connection pays for the round trip. These figures come from our own ping.pe test on 6 October 2026, the lowest of about 10 pings per probe city, as published on our city pages:
- Amsterdam: probes in Frankfurt and London reached our server in 6.6 and 6.7 ms, Paris in 9.3 ms and Berlin in 11.6 ms, a good centre for mainland Europe. Read WordPress hosting in Amsterdam, or see the plans on the Netherlands VPS page.
- Dublin: a probe in Dublin needed 21.0 ms to reach our Amsterdam server, so visitors in Ireland are better served from Dublin itself. Read WordPress hosting in Dublin, or see the Ireland VPS page.
- Prishtina: probes in Vienna and Frankfurt reached our Prishtina server in 18.6 and 27.8 ms, and Skopje is about 3 ms away on our own network, which suits visitors in Kosovo and the nearby Balkans. Read WordPress hosting in Prishtina, or see the Kosovo VPS page.
A CDN helps far-away visitors with images and cached pages, but carts, checkouts and logged-in pages always come from your server. The full comparison is in our WordPress server location test, and availability by city is on the plans page.
Set up WordPress on a Debian 13 VPS, tested step by step
These are the commands we ran in the lab, in order. Order a plan with Debian 13 and wait for the email with the server's IP address and root password. At your domain registrar, point an A record for example.com and www.example.com to the IPv4 address and an AAAA record to the IPv6 address. Log in with ssh root@YOUR_SERVER_IP, and replace example.com with your domain everywhere below.
Step 1: install Nginx, PHP and MariaDB
# as root
apt update && apt full-upgrade -y
apt install -y nginx mariadb-server php-fpm php-mysql php-curl php-gd php-intl php-mbstring php-xml php-zip php-imagick curl unzip sudo
systemctl is-active nginx php8.4-fpm mariadb
The install took 30 seconds in our lab, and the last command should print active three times. The PHP packages cover the extensions the WordPress hosting handbook marks as required and most of its highly recommended list.
Step 2: turn on the firewall
Allow SSH first, or you will lock yourself out:
# as root
apt install -y ufw
ufw allow OpenSSH
ufw allow "Nginx Full"
ufw --force enable
ufw status
You should see Status: active with OpenSSH and Nginx Full allowed, for IPv4 and IPv6. Our Debian 13 security guide adds SSH keys and uses nftables directly; pick one firewall tool, not both.
Step 3: create the database
Make a strong password and copy it somewhere safe; you need it twice:
# as root
openssl rand -hex 16
mariadb -e "CREATE DATABASE wordpress DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;"
mariadb -e "CREATE USER 'wpuser'@'localhost' IDENTIFIED BY 'PASTE-PASSWORD-HERE';"
mariadb -e "GRANT ALL PRIVILEGES ON wordpress.* TO 'wpuser'@'localhost';"
The three mariadb lines print nothing when they work.
Step 4: install WP-CLI
WP-CLI is WordPress's official command-line tool for installs, plugins and updates:
# as root
curl -O https://raw.githubusercontent.com/wp-cli/builds/gh-pages/phar/wp-cli.phar
php wp-cli.phar --info
chmod +x wp-cli.phar
mv wp-cli.phar /usr/local/bin/wp
The second command should end with WP-CLI version: 2.12.0 or newer.
Step 5: download and install WordPress
The site's files belong to www-data, the user Nginx and PHP run as, so WP-CLI runs as that user too:
# as root (WP-CLI itself runs as the www-data user)
mkdir -p /var/www/example.com
chown www-data:www-data /var/www/example.com
cd /var/www/example.com
sudo -u www-data wp core download
sudo -u www-data wp config create --dbname=wordpress --dbuser=wpuser --dbpass='PASTE-PASSWORD-HERE'
sudo -u www-data wp core install --url=http://example.com --title="My WordPress VPS" --admin_user=siteowner --admin_email=you@example.com
We saw Downloading WordPress 7.1.3 (en_US)... and, at the end, Admin password: with a generated password; copy it. Two warnings are harmless: WP-CLI cannot create its cache folder in /var/www/.wp-cli, and /usr/sbin/sendmail: not found appears because WordPress tries to email the new admin before mail is set up.
Step 6: tell Nginx about the site
# as root
cat > /etc/nginx/sites-available/example.com <<'EOF'
server {
listen 80;
listen [::]:80;
server_name example.com www.example.com;
root /var/www/example.com;
index index.php;
client_max_body_size 64m;
location / {
try_files $uri $uri/ /index.php?$args;
}
location ~ \.php$ {
include snippets/fastcgi-php.conf;
fastcgi_pass unix:/run/php/php8.4-fpm.sock;
}
location ~ /\.(?!well-known) {
deny all;
}
}
EOF
ln -s /etc/nginx/sites-available/example.com /etc/nginx/sites-enabled/
rm /etc/nginx/sites-enabled/default
nginx -t && systemctl reload nginx
nginx -t should report syntax is ok and test is successful; our homepage then answered with HTTP 200.
Step 7: set PHP limits and the number of workers
The hosting handbook suggests a 256 MB PHP memory limit; the sed line sets the worker limit from the plan table above:
# as root
cat > /etc/php/8.4/fpm/conf.d/99-wordpress.ini <<'EOF'
memory_limit = 256M
upload_max_filesize = 64M
post_max_size = 64M
EOF
sed -i 's/^pm.max_children = .*/pm.max_children = 10/' /etc/php/8.4/fpm/pool.d/www.conf
systemctl restart php8.4-fpm
grep ^pm.max_children /etc/php/8.4/fpm/pool.d/www.conf
The last line should print pm.max_children = 10.
Step 8: switch on HTTPS
Install Certbot and its Nginx plugin from Debian:
# as root
apt install -y certbot python3-certbot-nginx
certbot --version
We got certbot 4.0.0, and Debian enabled certbot.timer, which renews certificates on its own. Once DNS points at the server, run certbot --nginx and answer its questions about your email and domain names, as the Certbot user guide describes. We could not run that step in our lab, because it needs a real public domain. When https://example.com opens with a padlock, tell WordPress:
# as root
cd /var/www/example.com
sudo -u www-data wp option update home 'https://example.com'
sudo -u www-data wp option update siteurl 'https://example.com'
Each line answers Success: Updated 'home' option. or the same for siteurl. Prefer Caddy or Traefik for certificates? Our reverse proxy and SSL guide compares them.
Step 9: give WordPress a real cron
By default WordPress runs scheduled tasks only when someone visits. A system cron runs them every five minutes instead:
# as root
apt install -y cron
cd /var/www/example.com
sudo -u www-data wp config set DISABLE_WP_CRON true --raw
echo '*/5 * * * * cd /var/www/example.com && /usr/local/bin/wp cron event run --due-now --quiet' | crontab -u www-data -
crontab -u www-data -l
In our lab the system log showed the job running as www-data at the next five-minute mark.
Prefer a control panel?
Panels do steps 1 to 8 from a web form. In our free control panel test, CloudPanel used about 1.1 GB of RAM at idle and asks for 2 GB, so it starts at VPS Micro; HestiaCP, with web, mail and DNS, used about 590 MB. For agencies that add sites every week, a panel is the easier road. Coming from cPanel? Our cPanel price increase guide names the free panels that import its accounts.
Make your WordPress VPS fast
- Add a page cache first; our stack benchmark has tested setups for Nginx, Apache, Caddy and OpenLiteSpeed.
- Keep the plugin list short. Two plugins cost our homepage 44% of its uncached speed.
- Check that OPcache is on. Debian enables it, but hand-edited configs sometimes switch it off.
- Serve images as WebP or AVIF, and put a CDN in front for distant visitors.
- Add a Redis object cache when the database is the slow part, as on busy shops.
# as root
php-fpm8.4 -i | grep -E "opcache.enable =>|opcache.memory_consumption"
free -m
ps -C php-fpm8.4 -o rss=,args= | grep pool
You want opcache.enable => On => On; ours also showed 128 MB of OPcache memory. free -m gives the real total in use; the ps line shows each worker's own figure, which overstates the total. If you would rather hand this tuning to someone, speed optimisation is part of our managed WordPress care for €100 a month, described below. If a server still feels slow, see why a VPS is slow.
Moving an existing site
Build the new server, copy the files and database, and preview the site through your computer's hosts file before you change DNS; then freeze changes, make a final copy and switch. Keep every URL the same so your rankings carry over. Our WordPress migration guide walks through it with WP-CLI. Send WordPress mail through a mail provider on SMTP port 587; outbound port 25 is blocked on new servers and opened on request via Telegram.
Keep it secure
# as root
apt install -y unattended-upgrades
cat /etc/apt/apt.conf.d/20auto-upgrades
On Debian 13 the package switches itself on; the file should contain APT::Periodic::Update-Package-Lists "1"; and APT::Periodic::Unattended-Upgrade "1";. Security updates then install daily. For WordPress itself, use a long admin password with a two-factor plugin, update core, themes and plugins weekly, delete what you do not use, and log in to SSH with keys. Keep your own copies of the database and wp-content somewhere other than the server; our off-site backup guide shows one way.
Managed WordPress from RS Computers: €100 a month
Not everyone who needs a VPS wants to run one. RS Computers offers managed WordPress on demand for €100 a month on your RS server: speed optimisation, WordPress customisation, managed WordPress care, SEO and AI search optimisation, getting the site indexed by Google, Bing and other search engines, and advice on which articles to write for your company, for owners who want their own server without doing the WordPress work themselves. To order or to ask whether it fits your site, email info@rscomputers-ks.com or message us on Telegram.
Frequently asked questions
What is a WordPress VPS?
A WordPress VPS is a virtual private server that runs only your WordPress sites. You get a fixed number of vCPUs (shared on VPS plans, dedicated on VDS plans), your own memory and NVMe disk, your own IP address and root access, so you choose the PHP version, the PHP workers, the database and the cache. At RS Computers it is a KVM server in Amsterdam, Dublin or Prishtina.
How much RAM does a WordPress VPS need?
Less than many guides suggest. In our lab the whole server used 150 MB at rest; under load a plain blog peaked at 198 to 342 MB and a WooCommerce shop at 357 to 530 MB on 2 vCPUs. 1 GB runs one cached site, 2 GB a busy site or a small shop, and 4 GB or more suits several sites with a control panel.
Is a VPS faster than shared hosting for WordPress?
Usually, once a site has real traffic, because the PHP workers and database serve only your sites. Cached pages feel fast on any good host; the difference shows on carts, checkouts, search and the admin area, which PHP builds on every request. In our test an uncached page cost 72 to 270 ms of CPU.
Can I get managed WordPress on an RS Computers VPS?
Yes, on demand. RS Computers offers managed WordPress for €100 a month on your RS server: speed optimisation, WordPress customisation, managed WordPress care, SEO and AI search optimisation, search engine indexing and article advice for your company. Email info@rscomputers-ks.com or message us on Telegram to order or to ask whether it fits your site.
How many WordPress sites can one VPS run?
As many as the CPU and memory carry. Plugins weigh more than the count of sites: two plugins nearly halved our homepage speed, while extra cached sites cost little. A VPS Micro carries a handful of small sites; a VPS Mini or a VDS, an agency's portfolio.
Do I need Linux skills to run WordPress on a VPS?
Basic ones. The nine steps in this guide are copy and paste, and a free control panel such as CloudPanel or HestiaCP replaces most of them with a web form. After that the regular work is updates, and automatic security updates handle the operating system.
Start with the plan your numbers point to
Count vCPUs before RAM, add a page cache, and set the worker limit to what the memory holds. Unsure? Start with VPS Micro and move up from the client area when free -m or your response times say so. Compare every size and city on the WordPress VPS hosting page, or message us on Telegram with what your site runs and we will help you pick.