Which requirements Magento 2.4.9 places on hosting, which models exist, how to check providers and which costs to expect.
Magento needs hosting that is built for Magento. Magento Open Source and Adobe Commerce only run on a specific software stack: PHP, MySQL or MariaDB, OpenSearch for search, Valkey as a cache, RabbitMQ for queues and Varnish as a page cache. A standard web hosting package does not provide this.
For most merchants, managed hosting with a specialized provider is the sensible choice. The provider runs the stack, keeps it up to date and monitors it. Your own server only makes sense if you have a team with Linux experience that is also reachable at night.
Expect hosting costs in the three-figure range per month for a live Magento store. In our experience, small stores pay around €100 to €250 per month, mid-sized stores €250 to €600, and clusters for high traffic more than that. The larger costs often come on top of the server: updates, security patches and support.
This article is for managing directors, e-commerce managers and IT leads who run or take over a Magento store and want to rethink their hosting. You will learn which requirements Adobe officially sets, which hosting models exist, how to compare providers and what it costs.
Magento is not a small PHP script that runs on any server. It is a large application with many services that have to work together. A standard web hosting package for websites or blogs is not designed for this.
A WordPress site gets by with PHP and a database. Magento needs much more: a search engine (OpenSearch), a cache store (Valkey, formerly usually Redis), a message broker for background jobs (RabbitMQ) and a page cache in front of the application (Varnish). If one of these services is missing or runs in the wrong version, the store does not work or runs slowly.
Magento handles many tasks in the background. Indexers update prices and catalogs, queues send emails and process bulk changes. For this, cron jobs must run reliably every minute and queue consumers must stay active. Many low-cost hosting packages do not allow this or limit how long processes can run.
Updates, code compilation and static content deployment run on the command line in Magento. Without SSH access and Composer, a Magento store cannot be maintained properly. Adobe recommends a PHP memory limit of 1 GB for code compilation and deployment and 2 GB for debugging.
Adobe supports Magento exclusively on Linux systems with x86-64 architecture. According to the system requirements, Windows and macOS are not supported. Teams developing on a Mac therefore use containers, and a Linux server for production.
Adobe publishes a list of tested software combinations for each version. Other combinations may work but are not supported. For a live store you should stick to this list, because otherwise errors are hard to pin down.
| Component | Magento 2.4.9 | Magento 2.4.8 | Magento 2.4.7 |
|---|---|---|---|
| PHP | 8.5 | 8.4, 8.3 | 8.3, 8.2 |
| MySQL | 8.4 | 8.4 | no longer listed |
| MariaDB | 12.3 | 11.4, 11.8 | 10.11, 11.8 |
| OpenSearch | 3 | 3 | 2.19, 3 |
| Valkey | 9 | 8.1 | 8.1 |
| RabbitMQ | 4.3 | 4.3 | 4.3 |
| Varnish | 8 | 8 | 8 |
| Nginx | 1.30 | 1.30 | 1.30 |
| Composer | 2.10 | 2.10 | 2.10 |
Table status: Adobe system requirements for on-premises installations, retrieved in November 2026. The values refer to the latest patch releases. Different versions may apply to Adobe Commerce on Cloud.
A provider does not just install these versions once, but has to keep up with them for years. If you run 2.4.8 with PHP 8.3 today and want to upgrade to 2.4.9, you need PHP 8.5 and MariaDB 12.3 or MySQL 8.4. Ask every provider how quickly they make new PHP and database versions available and whether you can choose the version per environment yourself.
Varnish stores finished pages and delivers them without PHP having to do any work. Valkey keeps sessions and the internal cache in memory. OpenSearch handles search and filters in the catalog. These three services influence load time more than raw processor power. A provider should offer them preconfigured and be able to explain how the cache is cleared after a deployment.
Magento needs a mail server or an SMTP service for order confirmations. A valid certificate is mandatory for HTTPS; Adobe does not support self-signed certificates. PayPal and Adobe’s package repository require at least TLS 1.2.
How much computing power your store needs depends less on revenue than on catalog size, extensions and traffic peaks. The following points help with the assessment.
Adobe points out that updates of Magento and extensions can require up to 2 GB of RAM. That is the lower limit for a single process, not for the whole server. The database, OpenSearch, Valkey, RabbitMQ and Varnish also run on a server. OpenSearch alone takes up several gigabytes depending on the catalog. In our experience, 8 GB of RAM is tight for a small live store, and 16 to 32 GB is common for mid-sized stores.
Pages delivered by Varnish cost hardly any computing time. The expensive pages are those that cannot be cached: cart, checkout, customer account and search. For planning, the number of simultaneous buyers in checkout matters, not the number of visitors on category pages.
Product images, log files and database backups grow over time. Plan for headroom and clarify whether backups are stored on the same storage or separately. Fast SSD or NVMe storage is standard for Magento, because indexers and the database create many small read and write operations.
A merchant with 20,000 products, three store views and ten extensions expects three times the number of simultaneous orders during Black Week. In normal operation, a managed server with 8 cores and 32 GB of RAM is enough. For the sales week, the merchant books additional web servers for two weeks. With cluster offerings this is often possible on a daily basis, with a single server it is not. The figures are an example, not a recommendation for your store. Planning only becomes reliable with a load test on the staging environment.
Five models are relevant for Magento. They differ in who runs the server and who responds when something breaks.
| Model | Who runs the stack | Suitable for |
|---|---|---|
| Shared hosting | Provider, but without Magento services | not suitable for live stores |
| Own server (VPS or root) | Your team or your agency | teams with Linux experience and on-call coverage |
| Managed Magento hosting | specialized provider | most small and mid-sized stores |
| Managed cluster | specialized provider | high traffic, B2B with many integrations, strong seasonal peaks |
| Adobe Commerce on Cloud | Adobe, on AWS or Azure | companies with an Adobe Commerce license |
A root server is cheap to rent. But you carry full responsibility for the operating system, security updates, firewall, backups and monitoring. If the store goes down on a Saturday evening, someone from your team has to respond. This working time does not appear on any hosting invoice, but it is real.
The provider supplies a server with a preinstalled Magento stack, applies security updates, monitors the services and responds to outages. You or your agency remain responsible for the application itself, meaning Magento updates and extensions. This split should be clearly stated in the contract.
In a cluster, the load is spread across several servers: separate web servers, database and search service. If one part fails, the rest keeps running. Many providers let you add resources at short notice for traffic peaks.
Adobe Commerce on Cloud is Adobe’s platform-as-a-service offering. In the Pro plan, staging and production run on dedicated infrastructure on AWS or Azure, spread across three availability zones. Fastly as a CDN and New Relic for monitoring are included. This offering is only available together with an Adobe Commerce license. It is not an option for Magento Open Source.
Several hosting providers in Europe specialize in Magento. We name two examples here to show what to look for. This is not a ranking and not a complete market overview.
maxcluster states that it runs Magento hosting in a data center in Frankfurt am Main that is certified to ISO 27001, PCI DSS and ISAE 3402. According to its product page, Varnish, Redis, RabbitMQ and a search engine are included in all plans, and availability is stated as 99.99% on an annual average. Prices are listed in a price list and a configurator.
Hypernode from the Netherlands offers cloud and dedicated plans for Magento, Adobe Commerce and Shopware. Prices are shown excluding VAT.
There are also general managed hosting providers that set up Magento servers, and agencies that offer hosting through partners. For Adobe Commerce, there is also Adobe Commerce on Cloud.
Reputable providers offer a test environment. Load a copy of your store there, measure load times for category, product page and checkout, and run a short load test. Only then do you know whether the performance matches the price.
solution25 and the two providers named above are based in Europe; US merchants will also find Magento hosting providers in the US. Whichever you choose, check that the data center region is close to your customers. Sales tax in the US is not handled by the hosting but through a tax service integration in Magento, which calculates rates by state and locality. If you work with a European provider or agency, clarify their support hours: between Central Europe and the US East Coast there are usually only a few overlapping working hours, so agree on a clear process for urgent outages.
Costs depend on the model, the size of the store and the scope of support. The figures in the table are reference values from our projects, not list prices. For Magento they sit at the upper end of what we quote for store systems in general in our article on e-commerce hosting, because the stack is larger.
| Option | Monthly cost (experience value) | What is included |
|---|---|---|
| Own server, self-managed | about €50 to €150 rent | hardware only; operation, updates and on-call come on top |
| Managed hosting, small store | about €100 to €250 | preinstalled stack, backups, monitoring, server security updates |
| Managed hosting, mid-sized business | about €250 to €600 | stronger servers, staging, extended response times |
| Managed cluster | from about €600, often over €1,500 | several servers, redundancy, flexible scaling |
| Adobe Commerce on Cloud | on request | platform operation, Fastly, New Relic; only with an Adobe Commerce license |
Adobe does not publish prices for Adobe Commerce. On its pricing page, every option leads to a request for a custom quote.
For Magento, the server invoice is rarely the largest item. Recurring costs include:
A mid-sized Magento store pays €400 per month for managed hosting, so €4,800 per year. The agency applies four security patches and needs one and a half days each, including testing. At an assumed €800 per day, that is another €4,800. A version upgrade with a PHP change costs another five to ten days once. In this example, hosting makes up less than half of the running costs. The assumptions are chosen freely; your figures depend on extensions and code quality.
An online store processes names, addresses, orders and often payment data. The hosting provider stores this data on your behalf. For stores serving the EU, the GDPR rules on data processing therefore apply to hosting.
Under Article 28 GDPR, you need a data processing agreement with the provider. Reputable providers offer one as standard. Check which subprocessors are listed, for example an external data center, a CDN or a backup service.
A data center in the EU makes the assessment easier. With providers based in the US, such as cloud platforms, the data region and the contractual basis matter. Since July 2023, the adequacy decision on the EU-US Data Privacy Framework applies to certified companies. For larger projects, have your data protection officer assess this question.
Ask about encrypted connections, separate access for your team, logging of access and a documented process for security incidents. A provider that cannot answer these questions in writing is not suitable for an online store.
Give every person and every agency their own SSH and admin access. Shared logins are convenient but make it unclear who changed what. When a collaboration ends, revoke access on the same day.
Adobe supports each Magento version only for a limited time. After regular support ends, there are no more regular security patches. This also affects hosting, because newer versions need newer software on the server.
| Version | Released | End of regular support |
|---|---|---|
| 2.4.6 | March 14, 2023 | August 11, 2026 |
| 2.4.7 | April 9, 2024 | May 31, 2027 |
| 2.4.8 | April 8, 2025 | May 31, 2028 |
| 2.4.9 | May 12, 2026 | May 31, 2029 |
The dates come from Adobe’s lifecycle policy for Adobe Commerce, as of November 2026. For 2.4.6, Adobe offers extended support until August 31, 2027.
If you still run 2.4.6 today, you are out of regular support. An upgrade to 2.4.8 or 2.4.9 almost always means a change of PHP version and often of the database. Clarify with the provider in advance whether both versions can run in parallel on a staging environment. That way you can test the upgrade without putting the live store at risk.
Set a date each year for the next major upgrade, ideally outside your peak season. An upgrade in January or February is calmer for most merchants than one in October.
Many merchants also review the platform itself when changing hosting. That makes sense, because a hosting contract often runs for one to two years. A few questions help put things in perspective:
If you plan to switch in the medium term, a shorter hosting contract can make sense. You will find a fair comparison of the systems in our article Shopware vs. Magento vs. WooCommerce, and the migration process on our page about migrating from Magento to Shopware 6. If Magento fits your business well, solid hosting is a better investment than a switch.
Not for a live store. Such packages usually lack OpenSearch, Valkey, RabbitMQ, Varnish, persistent background processes and enough memory. For a quick test, a local development environment is enough.
Adobe states up to 2 GB for updates of individual processes. Since other services run on the server as well, in our experience we plan at least 16 GB for small live stores and more for larger catalogs.
No. Adobe Commerce on Cloud is only available together with an Adobe Commerce license. Magento Open Source runs with a provider of your choice or on your own server.
The actual move with database, files and DNS change takes a few hours with good preparation. Including testing on the new environment and coordination, plan for two to four weeks. Do not schedule the move during peak season.
At least the version you use today and the next supported version. In November 2026, that usually means 2.4.8 and 2.4.9.
solution25 is a Shopware agency based in Bremen, Germany. We do not host Magento stores ourselves. But we help you make the right decision: we review your store, the state of the version and the extensions, and tell you which hosting model fits. If a switch to Shopware makes more sense for you, we calculate both paths honestly.
A good starting point is our store analysis. For questions about moving from Magento, read our page on migrating from Magento to Shopware 6 or contact us directly.
Henrik Schäfer is a TÜV-certified data protection officer and handles privacy and compliance topics in ecommerce projects at solution25. He helps merchants put privacy requirements into practice without losing sight of conversion. Get in touch
Responsible for content and updates: Henrik Schäfer. Last updated: November 2026. Next content review: February 2027.
