Cutter 4
- vCPU
- 2 × dedicated
- RAM
- 4 GB
- Storage
- 80 GB NVMe SSD
- Transfer
- 6 TB
- IPv4 / IPv6
- 1 / /64 routed
Solution
A WordPress site with moderate traffic runs comfortably on two dedicated cores and 4 GB of RAM with PHP 8.3, OPcache and Redis object caching. WooCommerce needs more, because cart and checkout pages cannot be page-cached: budget 4 cores and 8 GB. NVMe matters more than core count — most WordPress slowness is database IO wearing a CPU costume.
| Resource | What you actually need |
|---|---|
| CPU | 2 cores for a content site, 4 for WooCommerce |
| RAM | 4 GB with Redis; 8 GB for a shop with a large catalogue |
| Disk | NVMe, 80 GB and up depending on media |
| Stack | PHP 8.3 with OPcache, MariaDB, Redis, nginx |
Location is usually the decision that matters most for this workload — either because latency dominates, or because jurisdiction does.
Four cores and 8 GB leaves headroom for growth.
Or use a stack installer if you would rather not hand-configure.
These two changes account for most of the achievable speedup.
nginx FastCGI cache, or a plugin that writes static HTML.
Certbot for TLS, nightly encrypted backups for the database and uploads.
2 GB is workable for a small site, 4 GB is comfortable with Redis object caching, and WooCommerce with a real catalogue wants 8 GB. Database memory, not PHP, is usually what runs out first.
Materially, yes. You get guaranteed resources, root access, your own PHP version, and no arbitrary process limits. The trade is that you are responsible for updates and security.
Yes. We require only an email address you control, and checkout is crypto-only, so there is no payment-card trail linking you to the site.