This post contains affiliate links. If you purchase through our links, we may earn a commission at no extra cost to you.
Running WordPress on shared hosting works — until it doesn’t. The moment your site starts getting real traffic, you’ll feel the ceiling. I moved a mid-size WordPress site to Vultr’s $6/month High Performance AMD instance earlier this year, and the difference was immediate: TTFB dropped from over 400ms to around 145ms in New York, and I stopped worrying about “noisy neighbor” CPU throttling.
This guide covers two paths to deploy WordPress on Vultr VPS: the one-click Marketplace app (fastest, good for beginners) and a manual LEMP stack install on Ubuntu 24.04 LTS (the approach I recommend for anyone who wants real control). Both paths end with a production-ready site behind HTTPS with basic security hardening — which, surprisingly, most tutorials skip.

Which Vultr Plan Should You Start With?
Before you touch the keyboard, pick the right plan. This decision matters more than most tutorials let on.
The $5/month Regular Compute plan (1 vCPU, 1 GB RAM, 25 GB SATA SSD) technically runs WordPress, but the older SATA SSD and shared CPU burst behavior make it a frustrating experience once you add a caching plugin and a few WooCommerce extensions. I don’t recommend it for anything you care about.
The $6/month Cloud Compute High Performance AMD (1 vCPU, 1 GB RAM, 25 GB NVMe) is the right starting point. You get AMD EPYC-Genoa CPUs running at 3.25 GHz and NVMe storage — a meaningful difference for WordPress, which hammers random read IOPS every time it processes a page request. Better Stack’s 12-month benchmark test (March 2025 – March 2026) showed this plan delivering an average TTFB of 145ms in New York and 185ms in London at standard load.
If you’re planning to run WooCommerce or expect more than a few thousand monthly visitors from day one, jump straight to the $24/month Standard HP (2 vCPU, 4 GB RAM, 100 GB NVMe). That’s the plan tested in Better Stack’s Geekbench 6 results: 1,926 single-core and 3,513 multi-core — roughly 2.5× faster than DigitalOcean’s Basic Droplet on single-core, which is the metric that matters most for PHP.
| Plan | vCPU | RAM | Storage | Price/mo | Best For |
|---|---|---|---|---|---|
| Regular Compute Starter | 1 | 1 GB | 25 GB SATA SSD | $5.00 | Dev/testing only |
| High Performance AMD (HP) | 1 | 1 GB | 25 GB NVMe | $6.00 | WordPress starter (recommended) |
| High Performance AMD | 2 | 4 GB | 100 GB NVMe | $24.00 | WooCommerce / higher traffic |
| Optimized General Purpose GP-1 | 1 | 4 GB | 30 GB NVMe | $30.00 | Memory-heavy workloads |
Prices last checked: 2026-06-20
Vultr bills hourly, capped at the monthly maximum — so you can spin up a $24/month instance, test it for a day, and only pay $0.036/hour. That flexibility is useful when you’re figuring out the right tier.
Option A: One-Click WordPress Deployment (Fastest Path)
If you want WordPress live in under 10 minutes and don’t need to customize the server stack, Vultr’s Marketplace App is the way to go.

- Log in to your Vultr account at
my.vultr.com. (Vultr New accounts get a $10 free credit.) - Click Deploy New Server → select Marketplace Apps → choose WordPress.
- Pick a server location closest to your audience. Vultr has 32 datacenter locations — New York, London, Tokyo, Amsterdam, and more — all at the same flat price.
- Select your plan (minimum $6/month HP AMD) and click Deploy Now.
- The server provisions in approximately 60 seconds.
- Go to Server Information in the portal to retrieve the root password and server IP.
Point Your Domain
Add an A record in your DNS settings pointing your domain to the server’s IP address. DNS propagation usually completes within minutes, though it can take up to 48 hours.
Add SSL
Once DNS resolves, SSH into the server and run:
certbot --nginx --redirect -d www.yourdomain.com -d yourdomain.com -m [email protected] --agree-tos
Certbot handles the Let’s Encrypt certificate and configures Nginx to redirect HTTP → HTTPS automatically.
Finish the WordPress Setup
Visit https://yourdomain.com and complete the WordPress wizard: site title, admin username, password, email. Then go to Settings → General and confirm both “WordPress Address (URL)” and “Site Address (URL)” match your domain exactly.
The one-click app ships with Wordfence Security, SMTP Mailer, and PHPMyAdmin pre-installed — a solid starting kit.
Who this path is NOT for: Anyone who wants to control their PHP version, switch between Nginx configs, or run multiple WordPress sites on a single server. For that, use the manual path below.
Option B: Manual LEMP Stack on Ubuntu 24.04 LTS (Recommended)
This is the approach from Vultr’s official documentation (updated April 2026). LEMP stands for Linux + Nginx + MySQL + PHP. Nginx uses less memory than Apache and handles static file serving more efficiently — for a 1 GB RAM VPS, that difference matters.

Prerequisites
- A Vultr VPS running Ubuntu 24.04 LTS (root or sudo access)
- A domain name with its A record already pointing to the server IP
Step 1 — Update the System
sudo apt update && sudo apt upgrade -y
Always do this first. Stale packages are a common source of dependency conflicts.
Step 2 — Install Nginx
sudo apt install nginx -y
sudo systemctl start nginx
sudo systemctl enable nginx
Open the firewall for web traffic:
sudo ufw allow "Nginx Full"
sudo ufw reload
💡 Tip: Prefer a visual approach? You can build these rules with our free Firewall Rule Builder — it generates ufw and iptables commands right in your browser.
Visit your server IP in a browser — you should see the Nginx default page confirming it’s running.
Step 3 — Install MySQL
sudo apt install mysql-server -y
sudo systemctl start mysql
sudo systemctl enable mysql
sudo mysql_secure_installation
The mysql_secure_installation wizard removes test databases and anonymous users, and sets a root password. Don’t skip it.
Step 4 — Create the WordPress Database
sudo mysql
Inside the MySQL shell:
CREATE DATABASE wordpressdb;
CREATE USER 'wordpressdbuser'@'localhost' IDENTIFIED BY 'YourStrongPassword123!';
GRANT ALL PRIVILEGES ON wordpressdb.* TO 'wordpressdbuser'@'localhost';
FLUSH PRIVILEGES;
EXIT;
Use a strong, unique password here. This credential goes into wp-config.php, so it needs to be something you can store in a password manager.
With the database created, it’s worth setting up automated backups now before you forget — our MySQL Backup Script Generator builds a mysqldump script with compression, retention cleanup, and a ready-to-use cron line for wordpressdb.
Step 5 — Install PHP 8.3 and Extensions
sudo apt install php php-cli php-common php-imap php-fpm php-snmp php-xml \
php-zip php-mbstring php-curl php-mysqli php-gd php-intl -y
Verify the version:
php -v
You should see PHP 8.3.x. WordPress 6.x officially supports PHP 8.3, and you’ll get a small performance gain over PHP 8.1 on database-heavy pages.
Step 6 — Download and Deploy WordPress
wget http://wordpress.org/latest.tar.gz
sudo tar -xvzf latest.tar.gz
sudo mv wordpress/* /var/www/html/
sudo chown -R www-data:www-data /var/www/html
cd /var/www/html/
sudo rm -f index.html index.nginx-debian.html
sudo mv wp-config-sample.php wp-config.php
Step 7 — Edit wp-config.php
sudo nano wp-config.php
Find the database section and update it with the credentials you created in Step 4:
define( 'DB_NAME', 'wordpressdb' );
define( 'DB_USER', 'wordpressdbuser' );
define( 'DB_PASSWORD', 'YourStrongPassword123!' );
define( 'DB_HOST', 'localhost' );
Save and exit with Ctrl+X → Y → Enter.
Step 8 — Configure Nginx for WordPress
Find the PHP-FPM socket path:
ls /var/run/php
Edit the Nginx default site config:
sudo nano /etc/nginx/sites-available/default
Your server block needs FastCGI configuration pointing to the PHP-FPM socket and WordPress permalink rewrite rules. After editing, test and restart:
sudo nginx -t
sudo systemctl restart nginx
💡 Tip: Want a head start on the config? Our free Nginx Config Generator builds a working server block you can adapt to your setup.

Step 9 — Install SSL with Let’s Encrypt
sudo snap install certbot --classic
sudo certbot --nginx -d yourdomain.com -d www.yourdomain.com -m [email protected] --agree-tos
sudo certbot renew --dry-run
Certbot sets up auto-renewal. Let’s Encrypt certificates expire every 90 days, so the dry-run confirms the renewal process works before you need it.
Step 10 — Complete the WordPress Installer
Open https://yourdomain.com in a browser. The WordPress installation wizard will appear. Set your site title, admin username, password, and email, then click Install WordPress.
You’re live.
Security Hardening — Don’t Skip This
Most tutorials end at Step 10. This is where the gaps are — and where most WordPress on VPS deployments get compromised.
Disable SSH Password Authentication
SSH keys are significantly more secure than passwords. After adding your public key to ~/.ssh/authorized_keys, disable password login:
sudo nano /etc/ssh/sshd_config
Set:
PasswordAuthentication no
Then restart SSH. From this point, only your key can log in.
Set Up UFW Firewall
sudo ufw default deny incoming
sudo ufw default allow outgoing
sudo ufw allow ssh
sudo ufw allow 80/tcp
sudo ufw allow 443/tcp
sudo ufw enable
This whitelists only SSH, HTTP, and HTTPS — everything else is blocked by default.
Install Fail2Ban
Fail2Ban monitors your logs and bans IPs after repeated failed login attempts. Default behavior: scans every 5 minutes, bans an IP for 2 hours after 3 failed attempts.
sudo apt install fail2ban -y
sudo systemctl enable fail2ban
sudo systemctl start fail2ban
It’s a one-command install that eliminates most brute-force risk. There’s no excuse not to run it.
Vultr also provides native DDoS mitigation at the infrastructure level — it detects and reroutes malicious traffic within approximately 60 seconds without any configuration on your end. That covers the heavy-end attacks; Fail2Ban handles the persistent low-level probes.

Vultr vs. The Alternatives — Is It the Right Platform?
Vultr is the pick if you’re optimizing for price-to-performance and geographic distribution. But it’s not the only option worth considering.
| Provider | Entry VPS | One-Click WordPress | Key Advantage |
|---|---|---|---|
| Vultr Vultr | $6/mo (HP AMD) | Yes | 32 locations, flat pricing, AMD EPYC NVMe |
| DigitalOcean | $6/mo (Basic) | Yes (Marketplace) | Better managed services, cleaner UX, richer app marketplace |
| Linode (Akamai) | $5/mo | Yes | More bandwidth, better stability under sustained load |
When Vultr wins: You need servers in specific global regions (32 locations vs DigitalOcean’s ~15), you want raw compute performance at the lowest price, or you’re comfortable managing your own stack. Vultr’s AMD EPYC-Genoa CPUs run at 3.25 GHz — a meaningful advantage for PHP’s single-threaded execution model.
When Vultr isn’t the right call: If you need managed databases, app deployment pipelines, or a more guided developer experience, DigitalOcean’s ecosystem is more complete. For high-load European deployments, Linode’s bandwidth allocation and European peering give it an edge.
[INTERNAL LINK: Vultr vs DigitalOcean 2026]
Frequently Asked Questions
How long does it take to deploy WordPress on Vultr VPS?
Using the one-click Marketplace App, the server provisions in under 60 seconds. Add 10–15 minutes for DNS propagation, SSL setup, and the WordPress installer — you can have a live site in under 30 minutes. The manual LEMP stack approach takes 45–90 minutes depending on your familiarity with Linux commands.
What is the minimum Vultr plan for WordPress?
The practical minimum is the $6/month High Performance AMD plan (1 vCPU, 1 GB RAM, 25 GB NVMe). The $5/month Regular Compute option works for a basic site but uses slower SATA SSD storage and will feel constrained once you add a theme, plugins, and real traffic. For WooCommerce or anything beyond a simple blog, start with the $24/month Standard HP plan.
Do I need a control panel like cPanel or Plesk on Vultr?
No. This guide installs WordPress directly on the LEMP stack via the command line, which is leaner and cheaper than adding a control panel. If you prefer a GUI, Vultr’s one-click app includes Cockpit (a web-based server dashboard). For a full control panel experience, there are also free options like HestiaCP that you can install on top of the base server.
Is Vultr secure enough for a production WordPress site?
Yes, with proper hardening. Vultr itself provides native DDoS mitigation at the infrastructure level. On the application side, the steps in this guide — SSH key authentication, UFW firewall, and Fail2Ban — cover the main attack vectors for a VPS-hosted WordPress site. Add a plugin like Wordfence for WordPress-layer security (blocking malicious login attempts at the application level).
Does Vultr offer managed WordPress hosting?
Vultr offers a partnership with WPMU DEV for managed WordPress through their Marketplace. It requires a separate WPMU DEV subscription and gives you a more hands-off experience. If you’d rather not touch the server, it’s an option — though you’re paying for two services at that point. Most WordPress sites on a single VPS don’t need it.
Final Recommendation
If you’re moving off shared hosting and want real control without paying cloud enterprise prices, Vultr’s $6/month HP AMD plan with a manual LEMP stack is the best value setup available right now. The performance numbers back it up — 145ms average TTFB in New York and 2.5× better single-core performance than DigitalOcean Basic — and the $6/month price point is hard to argue with.
The one-click Marketplace App is a legitimate shortcut if you’re comfortable with a pre-configured stack. Just don’t skip the SSL and security hardening steps — they apply to both paths.
Get started with a $10 free credit: Vultr
Once your WordPress site is live, the next step is caching. A properly configured Nginx FastCGI cache or a plugin like WP Rocket will bring your TTFB down well below 100ms even on the entry-level plan. [INTERNAL LINK: Best WordPress Caching Plugins 2026]

