Cutter 16
- vCPU
- 6 × dedicated
- RAM
- 16 GB
- Storage
- 320 GB NVMe SSD
- Transfer
- 15 TB
- IPv4 / IPv6
- 1 / /64 routed
Solution
Shops cannot cache the pages that matter. Cart, checkout and account pages are dynamic by definition, so e-commerce is genuinely CPU and database bound in a way that content sites are not. Budget four dedicated cores and 8 GB for WooCommerce with a real catalogue, and eight cores with 16 GB for Magento 2, which is heavier than its documentation suggests.
| Resource | What you actually need |
|---|---|
| CPU | 4 dedicated cores for WooCommerce, 8 for Magento 2 |
| RAM | 8–16 GB; Elasticsearch alone wants 4 GB |
| Disk | NVMe, 320 GB and up with product media |
| Uptime | 99.99% SLA — downtime is lost revenue, measurably |
Location is usually the decision that matters most for this workload — either because latency dominates, or because jurisdiction does.
Six to eight dedicated cores with 16 GB.
Magento requires Elasticsearch or OpenSearch; WooCommerce benefits from it.
Full-page cache everything else; never cache a session-bearing page.
Both affect real-world checkout latency.
An order lost to a failed backup is a customer lost permanently.
Eight dedicated cores and 16 GB of RAM is a realistic production floor, largely because Elasticsearch and the Magento cron stack are memory-hungry. The official minimums are optimistic.
Yes, measurably. Every additional 100 ms of latency has a documented negative effect on conversion; host near your customers.
Yes — that is independent of hosting. Most shop platforms have a crypto gateway plugin, including the one that powers our own checkout.