Deploy Ubuntu or Debian
Order the size below, then SSH in. Typical provision is under a minute.
WordPress
Your stack, your plugins, your VPS.
Skip restrictive shared WordPress hosts. Deploy Ubuntu or Debian, install Nginx and PHP, and size RAM for WooCommerce yourself.
Why a VPS
WordPress without a shared-hosting ceiling.
You choose the OS, the PHP version, the cache, and the database. WooCommerce sizing is a RAM conversation, not a locked SKU.
Enterprise SAS SSD
PHP-FPM, MySQL, and object caches stay on enterprise drives. Every plan includes the same storage class.
Full root
Install Redis, Nginx or Caddy, or a panel if you want one. Nothing is hidden behind a shared-hosting plugin list.
Copy the site off first
Take a snapshot before plugin day, and keep a database dump and a copy of wp-content off the server too: snapshots and backups stay on LayerOne's cluster, and a reinstall is permanent.
Public-site protection
Always-on L3/L4 mitigation sits in front of the storefront. You still own the host firewall and WordPress hardening.
How it works
A stack you can rebuild from notes.
Most brochure sites fit gc.micro. WooCommerce and concurrent checkout usually want gc.medium so MySQL has RAM to breathe.
Install the web stack
Nginx or Caddy, PHP-FPM, and MariaDB or MySQL. Redis if you are running object cache.
Point DNS at the IPv4
Every VPS includes a dedicated address. TLS is yours to terminate with Caddy or certbot.
Copy data off before plugin day
Dump the database and copy wp-content off the server, then update. The platform has nothing to restore from if a plugin takes the shop down.
Step 2 on Ubuntu 24.04: packages and the Nginx site
sudo apt install -y nginx mariadb-server php8.3-fpm php8.3-mysql \
php8.3-curl php8.3-gd php8.3-intl php8.3-mbstring php8.3-xml php8.3-zip# /etc/nginx/sites-available/example.com
server {
listen 80;
server_name example.com www.example.com;
root /var/www/example.com;
index index.php;
location / {
try_files $uri $uri/ /index.php?$args;
}
location ~ \.php$ {
include snippets/fastcgi-php.conf;
fastcgi_pass unix:/run/php/php8.3-fpm.sock;
}
}Link the site into sites-enabled, run sudo nginx -t, reload, then add the certificate with Certbot. Help center: A web server with HTTPS.
Plan fit
RAM for PHP and MySQL, not a WordPress SKU.
Brochure sites start on gc.micro. Catalogs and checkout traffic usually need gc.medium.
gc.micro
Brochure and light blogs
Cached WordPress, low concurrent editors, no heavy WooCommerce.
- 1 vCPU
- 2 GB RAM
- 40 GB SAS SSD
gc.medium
WooCommerce and busy sites
Catalog, checkout, and a real MySQL working set.
- 4 vCPU
- 8 GB RAM
- 160 GB SAS SSD
gc.xlarge
Heavier shops and staging plus prod
Larger catalogs, search indexes, or more than one WordPress on the same host.
- 8 vCPU
- 32 GB RAM
- 500 GB SAS SSD
Sized example: gc.medium
A WooCommerce shop with a Redis object cache
PHP-FPM workers, MariaDB, and Redis share one server, and cart and checkout pages skip the page cache, so every order reaches PHP and the database. 8 GB gives MariaDB room for its buffer pool beside the PHP workers. A cached brochure site or blog starts on gc.micro.
Deploy gc.medium- 4 vCPU
- 8 GB RAM
- 160 GB SAS SSD
- $15.00/mo ($0.0205/hr)
Need exact specs and order links?
Deploy a WordPress VPS
FAQ
Full FAQ
Frequently asked questions
Straight answers on billing, the platform, and what is included on every plan.
Can I run WooCommerce on a VPS?
Yes. Choose a plan with enough RAM for your catalog size and concurrent checkout traffic.
Do you include a control panel?
No managed panel is required. Install WordPress over SSH or bring your own stack.
Are backups available?
Yes. Buy backup storage from Images at $1.00 per 10 GB per month, billed hourly from account credit. Snapshots and backups share that pool. Restore a server or deploy a new one from a backup. Still copy WordPress files and the database off the server yourself.
Ready to deploy a VPS?
Tampa is live. Pick a plan, pick an OS, and the server is online in under a minute.