Magento 2 Hosting Requirements: The Version Matrix That Decides Upgrades

Magento is the heaviest mainstream ecommerce platform you can self-host, and its requirements list is the reason. It is not one application: it is PHP, a database, a search engine, a cache, a message broker and a reverse proxy, all of which have their own supported-version matrices that move every release.

Here are the Magento 2 hosting requirements as Adobe publishes them, then the part the requirements page deliberately does not cover — what the store actually needs to stay up.

The version matrix, current as of September 2026

Read this by row. Each Commerce release supports a narrow band of everything, and mixing bands is where upgrades fail.

Two dates in that table are doing quiet damage right now. MySQL 8.0 reached end of support on 30 April 2026, and Elasticsearch 7.17 on 15 January 2026. A 2.4.6 store on MySQL 8.0 is running a supported Magento version on an unsupported database — which passes every check the application makes and fails the only one that matters when a CVE lands.

The rest of the supporting cast:

Adobe also requires Linux x86-64 — RHEL, CentOS, Ubuntu or Debian. Windows and macOS are not supported for production. And a valid HTTPS certificate is mandatory, with TLS 1.2 or higher required for PayPal and for repo.magento.com itself, so a stale TLS configuration breaks not only checkout but your ability to install anything.

The extension list, and the one requirement people miss

Adobe requires: bcmath, ctype, curl, dom, fileinfo, filter, ftp, gd, hash, iconv, intl, json, libxml, mbstring, openssl, pcre, pdo_mysql, reflection, simplexml, soap, sockets, sodium, spl, tokenizer, xmlwriter, xsl, zip, zlib.

Two beyond that list matter operationally. OPcache is recommended for every deployment and is not optional in practice — Magento's class hierarchy is enormous and recompiling it per request is the largest single waste available. And pcntl is required for the indexer to run in parallel; without it, reindexing is serial and slow in a way that is easy to misdiagnose as a hardware problem.

Then the requirement that catches everyone: a minimum of 2 GB RAM for Composer upgrades, with Adobe explicitly advising a swap file if the machine has less. Composer resolving Magento's dependency graph is memory-hungry, and the failure is an upgrade that dies partway through on a machine that runs the store perfectly well. Size for the upgrade, not just for the traffic.

What the requirements page cannot tell you

The matrix is an install gate. Four things decide capacity:

Catalogue and attribute depth. Magento's EAV model means attribute count multiplies against product count in a way a flat schema does not. A 5,000-product catalogue with 80 attributes is a bigger database than the product count suggests.

Concurrency on the uncached path. Varnish serves category and product pages beautifully. Cart, checkout, account and search bypass it entirely — and those are the requests that earn money. Size PHP-FPM and MySQL for the uncached fraction only.

Indexers. Reindexing is real work on real hardware, and on a large catalogue it competes with serving traffic. This is the workload that most often makes a store that "was fine" become intermittently slow.

Third-party modules. Same as every PHP platform, more so here. Each adds plugins and observers that execute per request.

Choosing a platform honestly

Be clear-eyed about the first row. NexonHost's Magento hosting plans run from a 10 GB Starter tier at €4.99/month to an 80 GB Agency tier at €34.99/month with unmetered bandwidth, and they are a good fit for development, staging, a modest catalogue and a store still finding its traffic. They are not where a store doing serious volume belongs, and no shared tier from any provider is — because a production Magento store wants OpenSearch, Varnish and Valkey configured against its catalogue, and that requires root.

When the store is real, the honest next step is a Linux VPS where you own the stack, and past that a dedicated server where MySQL gets memory nobody else is competing for and the indexers do not fight the web tier for I/O. If you would rather not run that stack yourself, managed infrastructure services cover the patching, monitoring and tuning without giving up root access.

The tuning that outperforms a hardware upgrade

1. OPcache sized so it is not evicting. Check opcache_get_status(); do not assume.
2. innodb_buffer_pool_size set against the actual working set. The default is far too small for an EAV schema.
3. Varnish in front, correctly. Full-page cache is the difference between Magento being fast and Magento being expensive.
4. Valkey or Redis for session and cache backends, not the filesystem.
5. RabbitMQ for asynchronous work — order processing, emails, exports — so a queue spike does not become a checkout latency spike.
6. Cron actually running. A surprising share of "Magento is broken" is cron not executing, and the symptoms are diffuse.

Failure modes worth recognising

• Upgrade dies during composer update. Memory. Add swap, or move to a machine with headroom.
• Search returns nothing. OpenSearch version outside the supported band for that release, or the service is down and the catalogue silently has no index.
• Checkout fails while browsing works. TLS version or outbound connectivity to the payment provider.
• Admin unusably slow, front end fine. Indexers, or a report table that has grown without bound.
• Fine until a campaign. PHP-FPM pm.max_children or MySQL max connections.

Before you commit

Check three things against the release you are running, not the newest one: the PHP version, the database version and its support status, and the search engine version. Most Magento upgrade failures are predicted by the matrix above before anyone touches a server. And confirm the target host will give you 2 GB of memory for Composer even if the store itself is small.

Related reading: PrestaShop hosting requirements, OpenCart hosting requirements, and DDoS-protected web hosting.

Sources

• System Requirements, Adobe Commerce documentation, retrieved 7 September 2026 — version matrix, extension list, 2 GB Composer memory requirement, Linux-only support and TLS requirement.
• Plan specifications and pricing as published on nexonhost.com on 7 September 2026; check the product page for current figures.