WooCommerce VPS Hosting

WooCommerce VPS hosting gives your store a server with its own RAM and vCPU, while shared hosting splits them among many sites. A store needs that more than a blog does. Cart, checkout and account pages show each shopper's own cart, so they can't come from a page cache. Every one of those requests runs PHP and queries the database. A self-managed GreenGeeks VPS also gives you full root access. With it, you can add what WooCommerce's baseline spec asks for, which is OPcache, a persistent object cache such as Redis, and a real cron job.

Yes, on most stores. WP-Cron only runs when someone loads a page. Action Scheduler sends WooCommerce's emails, applies scheduled sale prices and runs subscription renewals, and WP-Cron is what starts it. On a low-traffic store those jobs run late, and on a busy one WP-Cron adds work to every page view. Add define('DISABLE_WP_CRON', true); to wp-config.php, then add a system cron job that runs wp cron event run --due-now. GreenGeeks VPS allows cron as often as every minute, and every few minutes suits most stores.

Most growing stores fit the 8 GB plan at $19.99 a month, renewing at $39.99, and a new store can start on 4 GB at $9.99. The cost that grows with your sales is card processing. With WooPayments, US card sales cost 2.9% + $0.30 with no monthly fee, and Stripe, PayPal and Square work too. WooCommerce core adds no platform fee. Shopify, by comparison, adds 2% per sale on Basic when you use an outside payment provider, which is $200 on $10,000 of monthly sales. On a VPS, that money stays with the store.

On a self-managed VPS you move the store yourself, and you need a full copy. The WordPress XML export won't work, because it leaves out orders, products and WooCommerce settings. Move the database and the wp-content folder, update wp-config.php with the new database details, test the store, then point your domain at the VPS's dedicated IP. Older stores may still keep orders in wp_posts. You can switch to HPOS under WooCommerce > Settings > Advanced > Features, where compatibility mode keeps both sets of tables in sync.

GreenGeeks looks after the hardware and network. A self-managed VPS gives you full root access, so the OS, PHP, WooCommerce, your theme and your plugins, including their updates and conflicts, are up to you. That includes server tuning, such as PHP-FPM workers and innodb_buffer_pool_size. Two habits catch problems early. Check WooCommerce > Status > System Status after every PHP or plugin change, and place a test order after adding a plugin. LSCache only works on a LiteSpeed web server, which needs its own license, so on Apache plan page caching another way, with Redis taking load off the database.

Yes, with the stack you install on it. WooCommerce 10.8 and later recommends WordPress 6.9+, PHP 8.3+ and MySQL 8.0+ or MariaDB 10.6+, along with HTTPS and a 256 MB WordPress memory limit. PHP 8.4 is tested too. With root access, you install PHP 8.3 or 8.4, MariaDB 11.4 and a web server such as Apache 2.4 yourself. Optional pieces include cURL for PayPal and other integrations, SOAP for some extensions, and Multibyte String for non-English stores. After you install, WooCommerce > Status > System Status shows anything missing.

Hosting guides start live stores at 4 GB, even though WooCommerce's baseline is 1 vCPU and 2 GB. GreenGeeks' 4 GB plan fits a new store, and the 8 GB plan suits a store past 1,000 products or 1,000 orders a month. WooCommerce says it's time to move up when the admin area slows past 5,000 products or 10,000 orders, or 502 errors appear during a sale. Redis needs little memory, about 128 MB for a small store and 512 MB for a busy one. A catalog near 100,000 products with its own search engine needs more than 16 GB.

WP-CLI is the quickest route on a server you manage over SSH. Install it once, then run wp core download, wp config create and wp core install to set up WordPress. Then wp plugin install woocommerce --activate adds the store, and the setup wizard takes it from there. New stores use the faster HPOS order tables by default. Add Redis the same way with wp plugin install redis-cache --activate and wp redis enable, once the Redis server itself is running.

GreenGeeks leaves backups on a self-managed VPS to you, so set them up before the first order. Orders change all day, so dump the database several times a day with wp db export from a cron job, and copy the dumps and files off the server, for example to Google Drive or Amazon S3. The database stores your orders, products, customers and settings, plus the actionscheduler_ tables for scheduled emails and renewals. The files that matter are wp-content, including uploads for product images and downloads, and wp-config.php. The Redis cache rebuilds itself and doesn't need a backup.

WooCommerce runs without Redis, but a persistent object cache is part of its baseline hosting spec. WooCommerce's 2026 hosting guide calls object caching a must for growing stores. Redis keeps data such as prices, SKUs and stock levels in memory, so the database doesn't run the same query on every request. On GreenGeeks VPS you install it yourself with dnf, then add the free Redis Object Cache plugin. It isn't a page cache. Some store owners report extra CPU load on small servers, so watch the cache hit rate after you turn it on.