- Magento is the heaviest mainstream e-commerce platform, and it makes hosting demands WooCommerce never dreams of: Elasticsearch is mandatory, Varnish is expected, and RAM disappears fast.
- This guide specs a dedicated server for Magento properly, maps the full service stack, and sizes by catalog and order volume.
Nobody drifts casually into Magento — you choose it for multi-store setups, B2B price books, 100k-SKU catalogs, and customization depth no other platform matches. The price of that power is infrastructure: Magento 2 / Adobe Commerce is the hungriest mainstream commerce platform ever shipped, with a mandatory search engine dependency and an architecture that assumes serious hardware. A dedicated server for Magento is not an upgrade path; for production stores it is effectively the system requirement.
The Stack Magento Actually Requires
A production Magento 2.4.x box runs, simultaneously: PHP 8.2/8.3-FPM, MySQL/MariaDB, OpenSearch/Elasticsearch (mandatory — catalog search will not run without it), Redis (sessions + cache), Varnish (Adobe's officially recommended full-page cache), RabbitMQ for async operations on larger stores, and cron jobs that do real work (indexing, catalog rules, email queues). Each service wants its own RAM allocation — this is why "Magento minimum requirements" documents are a fantasy and 16 GB VPSes running Magento are a support-ticket generator.
Sizing by Store Profile
| Profile | Catalog / Volume | Recommended Spec | Est. Monthly |
|---|---|---|---|
| Small production store | Under 10k SKUs, modest traffic | 8 cores, 64 GB, 1 TB NVMe RAID 1 | $150–$220 |
| Established B2C | 10k–100k SKUs, multi-store views | 12–16 cores, 128 GB, NVMe RAID 10 | $250–$400 |
| B2B / enterprise commerce | Large catalogs, price books, ERP sync | Dual CPU or split DB/app servers, 256 GB | $450–$900+ |
Note the floor: Magento's realistic entry spec (64 GB) is WooCommerce's established-store spec — the platforms are a tier apart in appetite, which our WooCommerce guide makes a useful contrast to. RAM allocation on a 64 GB box, roughly: MySQL 16–24 GB, OpenSearch 8–12 GB (heap ≤ 50% of its allocation), Redis 4–8 GB, PHP-FPM pool 12–16 GB, OS and headroom the rest.
Performance Non-Negotiables
- Varnish in front: full-page cache via Varnish (not the file/Redis FPC fallback) is the difference between 50 ms and 800 ms category pages. Terminate TLS with Nginx in front of Varnish.
- NVMe everywhere: reindexing a 50k-SKU catalog is an I/O bloodbath — NVMe vs SATA shows up as minutes versus hours on index rebuilds.
- Production mode + preloaded OPcache — deploy compiled, never run developer mode in production, and give OPcache enough memory for Magento's enormous codebase (512 MB+).
- Cron hygiene: Magento's cron does heavy lifting — isolate it (separate FPM pool or CLI limits) so a long reindex never starves customer-facing PHP workers.
- High-clock cores still matter: admin operations, checkout, and API calls are single-threaded like all PHP — the Xeon vs Ryzen tradeoff tilts Xeon/EPYC here only because RAM ceilings force the platform choice first.
When to Split Servers
The classic Magento scale-out, in order: (1) everything on one strong box; (2) database to its own server on a private VLAN; (3) OpenSearch joins the DB server or gets a third; (4) multiple app/web nodes behind a load balancer with shared Redis and media. Most stores live happily at stages 1–2 for years — see our single server vs cluster guide before paying for stage 4 prematurely.
Frequently Asked Questions
Can Magento 2 really not run on a VPS?
It can run — badly. The service stack's combined RAM appetite plus reindexing I/O makes mid-size VPS hosting a false economy: you will spend the savings on developer hours chasing performance ghosts. See our dedicated vs VPS comparison.
Magento or WooCommerce for a new store?
If you are asking, WooCommerce — Magento earns its complexity only for multi-store, B2B, or 6-figure-SKU requirements. The hosting bill difference alone (roughly 2x at every tier) should factor in.
Does Magento need a managed dedicated server?
Unless you employ someone fluent in Varnish VCL, OpenSearch heap tuning, and MySQL optimization — yes. Magento operations is a genuine specialty.
Can WebsNP deploy the full Magento stack pre-configured?
Yes — Varnish, OpenSearch, Redis, and PHP tuned to your catalog size, with free migration of your existing store, staged and validated before cutover.
Magento rewards hardware done right: order a Magento-ready dedicated server from WebsNP — 64 GB+, NVMe RAID, full stack pre-configured. Send us your SKU count and order volume for an exact spec.